We recently bought the domain: *****.com

7 days after accepting the transfer the domain finally transferred to our registrar and we immediately changed the name servers from ns*.netregistry.net to amy.ns.cloudflare.com and cody.ns.cloudflare.com

20 days after changing the name servers, the majority of tests show that both old and new nameservers are still being reported:



We are now ready to launch the new site but this issue is plagueing us as a high proportion of the traffic is still receiving the old nameserves and so hitting the old server.

You can tell if you have hit the old or new server as the old server has the value "A" for the meta tag "Location" and the new server has "U". (The old server just has an iframe too!)

I have never had this problem before - who is causing this and how should we go about reaching a resolution?



Our registrar, 123-reg, accepted this was their fault and someone on their end was able to fix it.

To reiterate what was said in responses the issue was solely due to them.

  • Who is the new registrar? – David Schwartz Nov 26 '12 at 3:21
  • Please accept an Answer (green checkmark next to the Answer) if it helped you! – Chris S Dec 12 '12 at 20:41

Whois lists your name servers as amy.ns.cloudflare.com and cody.ns.cloudflare.com, but the parent servers (the gTLD servers) list ns1.netregistry.net, ns2.netregistry.net and ns3.netregistry.net as well as amy.ns.cloudflare.com and cody.ns.cloudflare.com as the name servers for your domain.

You need to fix this at your domain registrar as they're the party that is responsible for updating the parent servers. Show them this trace:

Tracing DNS delegation for "****.com"

Loading root server list

a.root-servers.net (

b.root-servers.net (

c.root-servers.net (

d.root-servers.net (

e.root-servers.net (

f.root-servers.net (

g.root-servers.net (

h.root-servers.net (

i.root-servers.net (

j.root-servers.net (

k.root-servers.net (

l.root-servers.net (

m.root-servers.net (

Sending request to "e.root-servers.net" (

Received referral response - DNS servers for "com"

a.gtld-servers.net (

b.gtld-servers.net (

c.gtld-servers.net (

d.gtld-servers.net (

e.gtld-servers.net (

f.gtld-servers.net (

g.gtld-servers.net (

h.gtld-servers.net (

i.gtld-servers.net (

j.gtld-servers.net (

k.gtld-servers.net (

l.gtld-servers.net (

m.gtld-servers.net (

Sending request to "a.gtld-servers.net" (

Received referral response - DNS servers for "****.com"

ns3.netregistry.net (

ns1.netregistry.net (

ns2.netregistry.net (

amy.ns.cloudflare.com (

cody.ns.cloudflare.com (

  • +1 The registrar is still giving invalid information to the TLD name servers. – David Schwartz Nov 26 '12 at 5:30

Your whois record shows only the two (correct) nameservers:

Nameserver:             amy.ns.cloudflare.com
Nameserver:             cody.ns.cloudflare.com

So I speculate that something went wrong with the domain transfer, and you need to contact your registrar to have it fixed.

  • I have spoke to them a few times over the last couple of weeks - they attribute it to the name servers being cached in some locations. Do you think there is something they could/should do? – Thom Seddon Nov 25 '12 at 14:15
  • 2
    Besides hire someone competent? They do look kind of dodgy... – Michael Hampton Nov 25 '12 at 19:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.