I’m a bit perplexed.
I initially got a call from a client in Calgary complaining that she could not reach one of our web sites - rebekahcourt.com - unless she disconnected from her WiFi and tethered to her cellphone.
Turns out the servers she’s using at Shaw Cable in Alberta - 220.127.116.11 and 18.104.22.168 - won’t resolve that site or a new sister site, hannambnb.com. But while I was waiting for her to get me that info, I was fiddling with dig via digwebinterface dot com ('cause I’m a Windows guy, sorry, LOL)…
First thing I found was that Google, AT&T, Comodo, HiNet, OpenDNS, Securolytics, UUNET, Verisign and Yandex report back the A records correctly but CloudFlare and Quad9 do not, seeming to time-out.
After a little more fiddling what I began to notice was that my domains with DNS hosted at DirectNIC or CarrierZone (Fusion/Megapath, yech) were fine but that domains with their DNS records hosted on old Windows boxes under my desk (yes, static IPs, thanks) were a problem.
Maybe a coincidence, but I doubt it.
Frankly there’s no reason for me not to move all my DNS to DirectNIC at this point but just so this doesn’t bite me in the tush with other clients in the future, I’d really like to know why CloudFlare (and Quad9) don’t like my old Windows DNS servers, and maybe what the heck is going on with Shaw and whether or not there’s a connection. Any thoughts?