Nameserver changes, but Cloudflare not recognizing them

Website, Application, Performance DNS & Network
1

I changed the name servers for astlepark.co.uk over a week ago, but Cloudflare isn’t recognising the change.

I’ve looked it up, and they look fine on DNS checker:

image
image1209×275 15.1 KB

Am I missing something?

2

You have not changed your nameservers. What you have done is add NS records with your current nameservers, which is not enough.

astlepark.co.uk.        172800  IN      NS      ns1.he.net.
astlepark.co.uk.        172800  IN      NS      ns2.he.net.
astlepark.co.uk.        172800  IN      NS      ns3.he.net.
astlepark.co.uk.        172800  IN      NS      ns4.he.net.
astlepark.co.uk.        172800  IN      NS      ns5.he.net.
;; Received 140 bytes from 2a01:618:404::1#53(dns3.nic.uk) in 28 ms

astlepark.co.uk.        86400   IN      NS      eleanor.ns.cloudflare.com.
astlepark.co.uk.        86400   IN      NS      wesley.ns.cloudflare.com.
;; Received 104 bytes from 2001:470:400::2#53(ns4.he.net) in 32 ms

You need to replace the nsX.he.net nameservers with the Cloudflare nameservers.

1 Like
3

What did you use to get that list? All the DNS lookup tools I’m using just show the Cloudflare ones.

4

NS entries form a chain from the root zone (.) to your zone:

dig +trace +nodnssec astlepark.co.uk. ns

; <<>> DiG 9.18.24-0ubuntu0.22.04.1-Ubuntu <<>> +trace +nodnssec astlepark.co.uk. ns
;; global options: +cmd
.                       7193    IN      NS      e.root-servers.net.
.                       7193    IN      NS      j.root-servers.net.
.                       7193    IN      NS      l.root-servers.net.
.                       7193    IN      NS      g.root-servers.net.
.                       7193    IN      NS      c.root-servers.net.
.                       7193    IN      NS      b.root-servers.net.
.                       7193    IN      NS      a.root-servers.net.
.                       7193    IN      NS      m.root-servers.net.
.                       7193    IN      NS      k.root-servers.net.
.                       7193    IN      NS      i.root-servers.net.
.                       7193    IN      NS      d.root-servers.net.
.                       7193    IN      NS      h.root-servers.net.
.                       7193    IN      NS      f.root-servers.net.
;; Received 239 bytes from 127.0.0.53#53(127.0.0.53) in 0 ms

uk.                     172800  IN      NS      nsd.nic.uk.
uk.                     172800  IN      NS      dns4.nic.uk.
uk.                     172800  IN      NS      dns2.nic.uk.
uk.                     172800  IN      NS      nsc.nic.uk.
uk.                     172800  IN      NS      nsb.nic.uk.
uk.                     172800  IN      NS      nsa.nic.uk.
uk.                     172800  IN      NS      dns1.nic.uk.
uk.                     172800  IN      NS      dns3.nic.uk.
;; Received 580 bytes from 192.112.36.4#53(g.root-servers.net) in 100 ms

astlepark.co.uk.        172800  IN      NS      ns1.he.net.
astlepark.co.uk.        172800  IN      NS      ns2.he.net.
astlepark.co.uk.        172800  IN      NS      ns3.he.net.
astlepark.co.uk.        172800  IN      NS      ns4.he.net.
astlepark.co.uk.        172800  IN      NS      ns5.he.net.
;; Received 140 bytes from 43.230.48.1#53(dns4.nic.uk) in 40 ms

astlepark.co.uk.        86400   IN      NS      eleanor.ns.cloudflare.com.
astlepark.co.uk.        86400   IN      NS      wesley.ns.cloudflare.com.
;; Received 104 bytes from 2001:470:300::2#53(ns3.he.net) in 32 ms

The tools you use for DNS lookups only show the last entry, not the whole chain, so you only see the Cloudflare servers.

1 Like
5

Awesome, every day’s a school day! Cheers bud, I’ll get on to the domain owner!

1 Like
6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.