Some further tests make it look like dig
is influenced by some caching stuff going on on my PC. I figured that out while playing around with a TXT record for testing purposes, and noticing that host
and dig
return different results for the same input.
Running the commands again on my phone using Termux reveals that the AAAA record is in place and functioning, but I still can’t reach the website from my browser by using the domain name.
~ $ dig [domain]
; <<>> DiG 9.16.41 <<>> [domain]
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39355
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;[domain]. IN A
;; AUTHORITY SECTION:
[domain]. 1800 IN SOA dns1.registrar-servers.com. hostmaster.registrar-servers.com. 1711402015 43200 3600 604800 3601
;; Query time: 30 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Mar 25 22:35:59 CET 2024
;; MSG SIZE rcvd: 118
~ $ dig [domain] AAAA
; <<>> DiG 9.16.41 <<>> [domain] AAAA
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45166
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;[domain]. IN AAAA
;; ANSWER SECTION:
[domain]. 1799 IN AAAA [correct IP!]
;; Query time: 36 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Mar 25 22:36:11 CET 2024
;; MSG SIZE rcvd: 73
~ $ host -t AAAA [domain]
[domain] has IPv6 address [correct IP!]
~ $
Correct on all counts. I’ll try some other DNS servers later. Right now I’m using the Mullvad DNS servers, any suggestions for ones that support DNS over TLS?