dice@molly:~ % drill opentracker.i2p.rocks AAAA
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 50351
;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;; opentracker.i2p.rocks. IN AAAA
;; ANSWER SECTION:
;; AUTHORITY SECTION:
i2p.rocks. 396 IN SOA ns1.i2p.rocks. ns2.i2p.rocks. 2024012401 3600 600 600 600
;; ADDITIONAL SECTION:
;; Query time: 0 msec
;; SERVER: 192.168.10.1
;; WHEN: Tue Mar 26 21:46:51 2024
;; MSG SIZE rcvd: 83
dice@molly:~ % drill opentracker.i2p.rocks
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 36745
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; opentracker.i2p.rocks. IN A
;; ANSWER SECTION:
opentracker.i2p.rocks. 3353 IN A 23.137.251.46
;; AUTHORITY SECTION:
;; ADDITIONAL SECTION:
;; Query time: 0 msec
;; SERVER: 2a02:a46e:550b:10::1
;; WHEN: Tue Mar 26 21:47:30 2024
;; MSG SIZE rcvd: 55
If you look closely at your drill(1) example, the ANSWER section is empty (as it should be when there's no record of the requested type). Getting a SOA record in the AUTHORITY section is expected. So I'd say something else is going wrong here, maybe some code just doesn't distinguish the sections in the response correctly...In this case it means the i2p.rocks domain exists (that's what the SOA record shows) but it doesn't have an AAAA (IPv6) address