• 1 Post
  • 7 Comments
Joined 1 year ago
cake
Cake day: August 10th, 2023

help-circle

  • 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!]
    ~ $
    



  • My host records consist of a single AAAA record that points to the IP address of my server, which I verified beforehand. I’ve tried dig, but I’m not sure how to interpret it’s output, which looks as follows:

    ;; Warning: Client COOKIE mismatch
    
    ; <<>> DiG 9.18.24 <<>> [domain]
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35067
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 1232
    ; COOKIE: 485ffdde4d749cd80100000066019ef6aba1fc1942596e31 (bad)
    ;; QUESTION SECTION:
    ;[domain].              IN      A
    
    ;; AUTHORITY SECTION:
    [domain].       3113    IN      SOA     dns1.registrar-servers.com. hostmaster.registrar-servers.com. 1711343555 43200 3600 604800 3601
    
    ;; Query time: 0 msec
    ;; SERVER: 192.168.178.1#53(192.168.178.1) (UDP)
    ;; WHEN: Mon Mar 25 17:05:52 CET 2024
    ;; MSG SIZE  rcvd: 146