Thom Seddon asked:
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
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.
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.
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.