After a while, I found this on Nameserver Record Report feature of WHM. I logged in to WHM of the virtual private server and looked for all DNS options. But it was perfectly fine on GoDaddy and that is fact is the parent nameserver. The hosting folks told me to set the IP correctly on your registrar. Note the highlighted areas, the child name servers or local name servers are still fetching old values somehow. The following nameservers are stealth nameservers:
The results of this are undefined in the DNS specifications, and it indicates configuration problems. I looked at the nameserver records first.Įrror : Your local nameservers contain NS records with IP’s not listed by the parent nameservers. SSL errors started coming in too and idiots at GoDaddy customer care promptly blamed it on the SSL.īut, I knew it well, it was not an SSL issue. As a result the client was in a fix and sales were down. While some internet service providers showed fetched our website from the new servers other ISPs still continued to pull content from the old server. We were moving from a shared hosting environment to a VPS environment when this problem occurred. This happened when we migrated the server from old host HostGator to new host Supreme Servers. Redundant nameservers issues when migrating servers In my case, the hosting company (Supreme Server), Domain registrar (GoDaddy) and ISP (Verizon) kept blaming each other and no one even tried to find a solution to this problem. I am providing the exact solution to fix this issue.
Basically, a single website resolves to multiple servers because of faulty nameserver configurations.Įspecially, if you are using custom nameservers via a Virtual Private Server and have created nameservers like and this problem arises many times. There have been situations where a particular website shows one version in Verizon ISP in the USA and a different version in Airtel ISP in India.