SoA not returned when pointing to hostname w/ no A record

#1

Hello,
1.1.1.1 is returning a timeout when looking up a SOA record for ‘office.de’. It appears to be doing this because the A record that the SoA points to doesn’t exist. My expectation would be for 1.1.1.1 to return the information about the SoA similar to what 8.8.8.8 does.

Using Cloudflare

 dig @1.1.1.1 SOA office.de

 ; <<>> DiG 9.10.6 <<>> @1.1.1.1 SOA office.de
 ; (1 server found)
 ;; global options: +cmd
 ;; connection timed out; no servers could be reached

Using Google

dig @8.8.8.8 SOA office.de

; &lt;&lt;&gt;&gt; DiG 9.10.6 &lt;&lt;&gt;&gt; @8.8.8.8 SOA office.de

; (1 server found)

;; global options: +cmd

;; Got answer:

;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 9746

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:

;office.de. IN SOA

;; ANSWER SECTION:

office.de. 299 IN SOA lexpr01dc0008.deuprd01.prod.outlook.de. msnhst.microsoft.com. 2017296360 1800 60 2419200 300

;; Query time: 163 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Wed Apr 03 10:34:12 CDT 2019

;; MSG SIZE rcvd: 130

Using Google to lookup the A record for the SoA above

dig @8.8.8.8 lexpr01dc0008.deuprd01.prod.outlook.de

; &lt;&lt;&gt;&gt; DiG 9.10.6 &lt;&lt;&gt;&gt; @8.8.8.8 lexpr01dc0008.deuprd01.prod.outlook.de

; (1 server found)

;; global options: +cmd

;; Got answer:

;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: SERVFAIL, id: 61531

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:

;lexpr01dc0008.deuprd01.prod.outlook.de. IN A

;; Query time: 67 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Wed Apr 03 10:35:04 CDT 2019

;; MSG SIZE rcvd: 67

Thank you.

0 Likes

#2

Hi @TomS, I am seeing what you expected to see:

$ dig @1.1.1.1 SOA office.de

; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> @1.1.1.1 SOA office.de
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51063
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;office.de.			IN	SOA

;; ANSWER SECTION:
office.de.		300	IN	SOA	lexpr01dc0008.deuprd01.prod.outlook.de. msnhst.microsoft.com. 2017296372 1800 60 2419200 300

;; Query time: 172 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Wed Apr 03 10:06:28 PDT 2019
;; MSG SIZE  rcvd: 130
0 Likes

#3

Same here

[email protected]:~$ dig +short soa office.de @1.1.1.1 lexpr01dc0008.deuprd01.prod.outlook.de. msnhst.microsoft.com. 2017296377 1800 60 2419200 300

[email protected]:~$ dig +short CHAOS TXT id.server @1.1.1.1 "FRA"

Fomatting on mobile is horrible, sorry :roll_eyes:

1 Like

#4

@MarkMeyer @cloonan

Thanks for replying folks. It turns out that there error was related to a VPN and confusion about the results between two different machines. Apologies for your wasted time and thanks again for providing the sanity check.

2 Likes