Closed adueppen closed 5 years ago
Hello, the screenshot shows that your server is 192.168.1.1
. What happens when you run dig moa.party @1.1.1.1
? For me it resolves as expected.
Touchy/james ~ > dig moa.party @1.1.1.1
; <<>> DiG 9.10.6 <<>> moa.party @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64775
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;moa.party. IN A
;; ANSWER SECTION:
moa.party. 1799 IN CNAME jmoore.me.
jmoore.me. 1799 IN A 38.103.165.44
;; Query time: 25 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Aug 09 10:23:09 PDT 2019
;; MSG SIZE rcvd: 77
Hmm when I do that it resolves normally. The server appears as 192.168.1.1
because I have 1.1.1.1
configured through my router. Oddly, disabling DNSSEC in my router configuration causes the site to resolve normally as well. I'm not quite sure where the issue lies though.
I messed around with the settings a bit more, and it turns out that DNSSEC and DoT can cause conflicts, which seems to have been the cause. I'm still not sure why some sites resolve and others don't, but it appears to be fixed now.
The website fails to load when I use 1.1.1.1 as my DNS server. Attempting to ping it fails, and dig reports a server error. I have DoT enabled on my router (as well as the Cloudflare DNS) but switching to Google's Public DNS results in no issues.