Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

EDNS requests intermittently timing out

Most are timing out. 8.8.8.8 works every time. Any ideas?

C:\Program Files\ISC BIND 9\bin>dig +search +bufsize=512 msn.com @64.6.64.6

; <<>> DiG 9.14.1 <<>> +search +bufsize msn.com @64.6.64.6
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19711
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;msn.com. IN A

;; ANSWER SECTION:
msn.com. 132 IN A 13.82.28.61

;; Query time: 93 msec
;; SERVER: 64.6.64.6#53(64.6.64.6)
;; WHEN: Fri May 03 13:31:24 Pacific Daylight Time 2019
;; MSG SIZE rcvd: 52


C:\Program Files\ISC BIND 9\bin>dig +search +bufsize=512 msn.com @64.6.64.6

; <<>> DiG 9.14.1 <<>> +search +bufsize msn.com @64.6.64.6
;; global options: +cmd
;; connection timed out; no servers could be reached

C:\Program Files\ISC BIND 9\bin>dig +search +bufsize=512 msn.com @64.6.64.6

; <<>> DiG 9.14.1 <<>> +search +bufsize msn.com @64.6.64.6
;; global options: +cmd
;; connection timed out; no servers could be reached

C:\Program Files\ISC BIND 9\bin>dig +search +bufsize=512 msn.com @64.6.64.6

; <<>> DiG 9.14.1 <<>> +search +bufsize msn.com @64.6.64.6
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61541
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;msn.com. IN A

;; ANSWER SECTION:
msn.com. 93 IN A 13.82.28.61

;; Query time: 62 msec
;; SERVER: 64.6.64.6#53(64.6.64.6)
;; WHEN: Fri May 03 13:32:03 Pacific Daylight Time 2019
;; MSG SIZE rcvd: 52


C:\Program Files\ISC BIND 9\bin>dig +search +bufsize=512 msn.com @64.6.64.6

; <<>> DiG 9.14.1 <<>> +search +bufsize msn.com @64.6.64.6
;; global options: +cmd
;; connection timed out; no servers could be reached

C:\Program Files\ISC BIND 9\bin>dig +search +bufsize=512 msn.com @64.6.64.6

; <<>> DiG 9.14.1 <<>> +search +bufsize msn.com @64.6.64.6
;; global options: +cmd
;; connection timed out; no servers could be reached

C:\Program Files\ISC BIND 9\bin>dig +search +bufsize=512 msn.com @64.6.64.6

; <<>> DiG 9.14.1 <<>> +search +bufsize msn.com @64.6.64.6
;; global options: +cmd
;; connection timed out; no servers could be reached

C:\Program Files\ISC BIND 9\bin>dig +search +bufsize=512 msn.com @64.6.64.6

; <<>> DiG 9.14.1 <<>> +search +bufsize msn.com @64.6.64.6
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26231
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;msn.com. IN A

;; ANSWER SECTION:
msn.com. 871 IN A 13.82.28.61

;; Query time: 47 msec
;; SERVER: 64.6.64.6#53(64.6.64.6)
;; WHEN: Fri May 03 13:34:08 Pacific Daylight Time 2019
;; MSG SIZE rcvd: 52


C:\Program Files\ISC BIND 9\bin>

Comments

  • Atcually, same resultseven if i remove the +bufsize

    Can this be related to yesterday's Azure DNS issue?
  • I am unable to replicate the results you are seeing. I will have our recursive team review in further detail.
  • Could you please provide a traceroute to both of our recursive IPs, 64.6.64.6 and 64.6.65.6, and also confirm if you are seeing similar results from both?
  • Yes, can I send it privately?
  • My traces do not go all the way through and ping does not reply. Is that normal?
  • Last usable hop on my traceroute is

    11 46 ms 46 ms 46 ms VERISIGN-IN.ear2.Seattle1.Level3.net [4.14.246.106]
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 * * * Request timed out.
    21 * * * Request timed out.
    22 * * * Request timed out.
    23
  • Same results with 64.6.65.6 except the trace is minutely different:
    (last hop)
    12 19 ms 20 ms 19 ms 4.7.26.10
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.

  • Thank you for the traceroutes. We appreciate your patience while we review and hope to have an update for you soon.
  • We have reached out directly so you may provide the full traceroute in confidence. I did speak with our networking team and we have had no reported issues or alerts at this time.
Sign In or Register to comment.