I manage several websites, servers and domains and we recently migrated our DNS server after an emergency. Now some domains have their NS servers pointing to the wrong IP according to some (Internet) DNS servers. I thought the situation would resolve itself when propagation was complete but it has been more than 72 hours and the problem is still affecting these domains.
The domain name ismartdesign.com, for example, should resolve to IP 220.127.116.11 and has NS servers
ns1.wizgousa.com correctly resolves to
18.104.22.168. However, if you use a website such as DNSWatch, which only does live DNS requests, you’ll notice that the IP address for
22.214.171.124. This is the old server’s IP and it has been offline since Monday June 30, 2014.
Some networks will resolve the problematic domains properly, some are still trying to reach the old server’s IP. Is there any way I can speed up the transition? Will this even sort itself out by itself?
Note: I know our current DNS configuration does not conform to best practices (both servers in same class, etc.) and we have plans to fix all this once all domains work properly.
You seem to have mismatched glue records for the domain wizgousa.com. Those nameservers themselves are returning the correct information, if you know where to find them, but the root nameservers still seem to have old addresses for them.
To resolve this, the owner of wizgousa.com must update the glue records with the domain regsitrar.
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.