Cannot complete nameserver setup


Hi there,

We’re trying to set up Cloudflare for the domain for our town museum, we’ve followed the instructions for repointing the NS records, and those changes have been applied, however the rest of the process seems stuck.

Looking at the DNS, it seems the SOA record is pointing to the domain registrar value, should this have been changed to Cloudflare as well? The DNS FAQ implies it gets switched over automatically when the NS records are changed? 3599 IN SOA 1447254827 28800 7200 604800 3600 3599 IN TXT “v=spf1 mx a ptr ~all” 3599 IN MX 30 3599 IN MX 10 3599 IN NS 3599 IN NS

I got this information from Google Apps dig, where the NS record changes have propagated. However when I lookup the domain on the NS records are shown as:

If I do a lookup locally I get the right answer:

set type=SOA
Non-authoritative answer:
primary name server =
responsible mail addr =
serial = 2030176827
refresh = 10000 (2 hours 46 mins 40 secs)
retry = 2400 (40 mins)
expire = 604800 (7 days)
default TTL = 3600 (1 hour)

This change was made at the end of last week and showed up at Google immediately, so we are slightly confused.



You need to change the nameservers at your registrar, not your host (where you seem to have made the change).


Thanks for the reply - the changes were at the registrar, sorry for any confusion. Cloudflare requested ns1 and ns2 be changed to fred and kate, and we have done that.

The local lookup I show at the end I’ve just done from my PC.


Thats the point. You changed the nameserver only at your host (Inter DNS presumably) but not at the registrar (might be Nominet for .uk). Your nameservers still point to Inter DNS.


But why is that when I query the NS records for the domain using Google Apps Dig, Google sees fred and kate? Those records can only be propagated if the change is made at the domain registrar?


These records come straight from your host.



Okay, I think I understand - I have set up Cloudflare previously for clients and not had this problem, but it was a different domain registrar, I might be (incorrectly!) expecting everything to work the same way with this one.

We will investigate further and get back to you - thanks for your help.


Confirmed that there was another screen on the domain company’s web site which had to be used to do this (different to my own previous experience), once we’d done that everything went as expected.

closed #10

This topic was automatically closed after 31 days. New replies are no longer allowed.