Oddly enough, my email which uses the same service isn’t having any problems.
There were no DNS changes on my end before the site went down. I’ve since tried deleting and re-adding all records, nameservers, etc. on both my registrar and in the netlify settings but no luck. It’s been about 48 hours with no improvement.
Unless I’ve missed something obvious, could you take a look behind the scenes and see what’s put a spanner in the works, please?
@codemacabre I’m seeing the same thing here in Southern California that @hrishikesh posted. Your DNS looks fine, so if you’re seeing something different, it may be regional, or maybe something to do with your local setup.
Yes, it could be your ISP. The way DNS works implements caching at every layer, including your ISP’s DNS servers and your local DNS cache. If you switched off to cellular (a good tactic for debugging, nice call!) and it worked, it would show that your ISP’s DNS cache was holding onto that value.
The funny part is now that your mobile device got the right IP, it probably logged it to its local DNS cache and once you connect back to the wi-fi / ISP, it’ll still resolve fine because your mobile device won’t reach out to the ISP’s DNS again (it’s already cached!)
This is a good exercise in understanding DNS TTL’s though; this guide that Luke wrote is a great explainer of how to wield the powers of TTL
Dang. I know that some ISP’s will automatically intercept non-resolving DNS requests and forward you to their own search engine instead of letting your browser totally fail (which I always disable for these reasons) but I’ve never heard of an ISP (cellular or land) just straight up blocking DNS for particular domains. That’s not cool
Hi, @codemacabre. The only other thing I can think of that it possibly could have been that fix this was enabling IPv6 for the DNS zone. Some mobile/wireless ISPs provide IPv6 connectivity only so it could be enabling that which resolved the DNS issues.
This is just a thought. I don’t know for sure what it was because DNS doesn’t have a history for me to check.