Saturday, May 16, 2015

networking - DNS issues after NS changes



We were experimenting with moving to a new Name Server Provider yesterday, so we switched our NS records a few times (about 3-4 times) during the course of the day. We have it set now on the original settings, but the website does not load anymore. It works on some computers, not others.



If we run




dig ourdomain.com





it hangs, but with




dig ourdomain.com +trace




it shows the correct information. Also, when logging in to one of our remote servers (in Germany) it works fine.




Could this be a problem with the DNS servers globally still needing to update? Or should I worry that something has gone completely wrong?



Thanks


Answer



Use pingdom dns to help diagnose the problem



From the information you have provided it sounds like there isn't a problem and the incorrect nameservers are cached somewhere. Try clearing all your DNS caches. If this doesn't help it might be cached by your ISP.


No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...