I'm experiencing an issue where a couple of teachers can't access skillsusa-register.org after the site switched to a new IP address. The previous IP was 104.156.59.9, but it's now 46.21.148.42. I've set up my local DNS server to use 8.8.8.8 and 1.1.1.1 as forwarders and have cleared the cache multiple times, yet the site still resolves to the old IP. Even when I use nslookup or dig from a client machine, I'm still getting the old address. Interestingly, Google shows the updated IP address. What's going on?
5 Answers
It sounds like your local DNS isn't flushing correctly or there's still an old DNS record causing issues. Usually, older records should clear out within 12-24 hours based on their default TTL settings.
I checked and Quad9 is still showing the old IP, but both 1.1.1.1 and 8.8.8.8 are showing the new address. It's a bit odd, but it might take some time for certain DNS servers to propagate completely.
Some tools can also help with troubleshooting if you've cleared your DNS cache locally, such as checking if your server’s configurations are correct. Just be patient; it usually resolves itself after a while.
You might also want to try a DNS propagation checker like whatsmydns.net. It gives you a global view of the address resolution. Remember, DNS changes can take up to 24 hours to propagate fully.
It looks like the old DNS information is likely still cached by servers that have previously looked up the address. If your query goes to a server that hasn't cached it yet, then you'll see the new IP. You can check the Time To Live (TTL) for the record with a dig command to see when it should update. For example: dig @ns1.hivelocity.net skillsusa-register.org. The number you see in the response indicates how long it will take for it to update.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures