Anyone got a suggestion for this? Why would Cloudflare DNS be unable to resolve the SOA record of a given domain if Google DNS can? 18.104.22.168 can also resolve this without trouble. Its not a one-of either, it repeatedly refuses to answer, but does for other domains. Hmmm. Is this a disconnect between Cloudflare and .ca root? A caching issue in Cloudflare? Hmm. If we “$ dig @d.root-servers.net -t SOA 100years.ca” and then check each of the roots (c.ca-servers.ca etc), they all work from my house… Hmm.
$ dig @22.214.171.124 -t soa 100years.ca ... ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 63615 ... $ dig @126.96.36.199 -t soa 100years.ca ... ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 196 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;100years.ca. IN SOA ;; ANSWER SECTION: 100years.ca. 10799 IN SOA ns1.fastpark.net. hostmaster.100years.ca. 1545692000 28800 7200 604800 86400