Assigned Authoritative Nameservers changed by Cloudflare

DNS & Network
#1

Our company has been using these Cloudflare assigned nameservers for over 3 years (cody and lucy). Now, when we create a new site, it is telling us to use a different set of nameservers:
lady.ns.cloudflare.com
rudy.ns.cloudflare.com

This seems to work, as our sites are still resolving, but we are getting a ‘Glue vs A record’ conflict now. My question is why would our authoritative nameservers change? And how can we revert the change so our nameservers remain cody and lucy. We have not changed accounts or account types. Thanks in advance!

#2

Name servers are assigned on a per-domain basis and while they’re often the same from one domain to another within an account, there is no guarantee that they will be consistent.

When a domain is delegated to name servers outside of the domain itself, glue records don’t really apply, so my guess is that the tool you are using might be seeing something cached if you just recently changed nameservers.

#3

Thanks Dave, yes the NS’ were recently changed and the error is still showing here http://leafdns.com/index.cgi?testid=AC05018E

We will keep an eye on it, but you are saying we shouldn’t worry about resolution failures?

#4

I don’t see any issues, the information from the gTLD servers appears to match with what Cloudflare is providing.

#5

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