Problem with resolving from DNS Google [203450136]

Customer Issue

Status Update

No update yet.

Description

do...@gmail.com

created issue #1

Oct 19, 2021 08:04AM

Hi Team,

We had troubles with resolving:

targovishte.bg for A, MX and NS
We received "Comment": "Name servers did not respond [83.228.89.235]."

I check the network connectivity everything seems that is OK from other public DNSs work correctly

Can you check with me what could be the provlem?

Best Regards,
Momchil Momchilov
Network Security Engineer

Comments

al...@google.com <al...@google.com> #2Oct 19, 2021 01:38PM

https://dnschecker.org/#A/targovishte.bg shows that most but not all resolvers succeed.

In our case, we do indeed frequently see issues communicating with authoritative DNS servers which do not respond within the 1 second timeout that we set.

It's also the case that DNSViz (

https://dnsviz.net/d/targovishte.bg/dnssec/ ) shows several errors. I don't believe that's the root cause of any timeouts, but it can't help overall behavior.

The best thing you can do is make sure that you have geographically redundant name servers, so name serving is generally more reliable. In some locations we can resolve just fine while in others we always fail to receive responses in time.

fd...@gmail.com <fd...@gmail.com> #3Nov 9, 2021 11:20AM

You were looking at an old analysis by DNSViz done on July 2020, I've updated it for you and it seems to be valid now: https://dnsviz.net/d/targovishte.bg/dnssec/ This does not seem to be the problem.

From these locations it resolves 100% of the time fine for me: Amsterdam, Noord-Holland (NL) Lisbon, Lisboa (PT) Kiev, Kyiv (UA) Perth, Western Australia (AU) Tel Aviv, Tel Aviv (IL)

I'm seeing some occasional SERVFAILs from the locations: Atlanta, Georgia (US) Chicago, Illinois (US) Dallas, Texas (US) Los Angeles, California (US) San Jose, California (US) Osaka, Osaka (JP)

I see almost constant SERFAILs from locations: New York City, New York (US).

And never got past a SERVFAIL from these locations: Dubai, Dubayy (AE)

Looking at the distances of the locations to Bulgaria I suppose they're too far to roundtrip within the set timeout.

From Atlanta, Georgia (US):

~ % dig targovishte.bg a @8.8.8.8

; <<>> DiG 9.10.6 <<>> targovishte.bg a @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45017
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
targovishte.bg.		21599	IN	A	83.228.89.3

;; Query time: 1432 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 09 11:40:21 CET 2021
;; MSG SIZE  rcvd: 59

~ % dig targovishte.bg a @8.8.8.8

; <<>> DiG 9.10.6 <<>> targovishte.bg a @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 57449
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

;; Query time: 2300 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 09 11:41:11 CET 2021
;; MSG SIZE  rcvd: 43

~ % dig targovishte.bg a @8.8.8.8

; <<>> DiG 9.10.6 <<>> targovishte.bg a @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47318
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
targovishte.bg.		21600	IN	A	83.228.89.3

;; Query time: 299 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 09 11:41:23 CET 2021
;; MSG SIZE  rcvd: 59

~ % dig targovishte.bg a @8.8.8.8

; <<>> DiG 9.10.6 <<>> targovishte.bg a @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 30543
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

;; Query time: 1283 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 09 11:41:29 CET 2021
;; MSG SIZE  rcvd: 43

~ % dig targovishte.bg ns @8.8.8.8

; <<>> DiG 9.10.6 <<>> targovishte.bg ns @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 60229
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;targovishte.bg.			IN	NS

;; Query time: 3249 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 09 11:46:26 CET 2021
;; MSG SIZE  rcvd: 43

~ % dig targovishte.bg ns @8.8.8.8

; <<>> DiG 9.10.6 <<>> targovishte.bg ns @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 25565
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;targovishte.bg.			IN	NS

;; Query time: 1124 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 09 11:46:29 CET 2021
;; MSG SIZE  rcvd: 43

~ % dig targovishte.bg ns @8.8.8.8

; <<>> DiG 9.10.6 <<>> targovishte.bg ns @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30326
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;targovishte.bg.			IN	NS

;; ANSWER SECTION:
targovishte.bg.		21600	IN	NS	ns1.egov.bg.
targovishte.bg.		21600	IN	NS	ns2.egov.bg.

;; Query time: 353 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 09 11:46:30 CET 2021
;; MSG SIZE  rcvd: 84

do...@gmail.com <do...@gmail.com> #4Nov 25, 2021 03:43PM

Hi,

Today I made some changes for routing optimization, but Is till sometimes
receive ServeFail or timed out may be from specific places around the
world. I did;nt know when I asked 8.8.8.8 it tries on a round robin for DNS
query am I right ?

Best Regards,
Momchil

На вт, 9.11.2021 г. в 13:20 ч. <buganizer-system@google.com> написа:

- Show quoted text -

do...@gmail.com <do...@gmail.com> #5Dec 21, 2021 12:20PM

Hi Team,

As I mentioned I already tried rerouting for the traffic through alternate ISPs.
We had problems only with Google DNS services.
I attached the Logs from all over the world from uptrends,
Can you check it again?

Best regards,
Momchil Momchilov
Network Security Engineer - CNsys PLC

Monitor_log-376098-20211221.xlsx

77 KB

Download

Monitor_log-376098-20211221.pdf

290 KB

View

Download

do...@gmail.com <do...@gmail.com> #6Jan 27, 2022 12:40PM

Hi Team,

Do you see my last post, unfortunately the issue persist. Can you check it again?

Best Regards,
Momchil Momchilov

pr...@gmail.com <pr...@gmail.com> #7Sep 1, 2024 09:23AM

On Sun, Sep 1, 2024, 13:52 princeqarsh0703 <buganizer-system@google.com>
wrote: