DNS resolf problem

164 views
Skip to first unread message

dian raikov

unread,
Jun 25, 2021, 9:35:34 AM6/25/21
to public-dns-discuss
only google dns did not resolf our domain which is burgasnet.com

I can open dns.google.com and post some test hier

root@web:/ # dig +dnssec +bufsize=1400 +timeout=1 @8.8.8.8 burgasnet.com A

; <<>> DiG 9.8.4-P2 <<>> +dnssec +bufsize=1400 +timeout=1 @8.8.8.8 burgasnet.com A
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached


root@web:/ # dig +dnssec +bufsize=1400 +timeout=1 @1.1.1.1 burgasnet.com A

; <<>> DiG 9.8.4-P2 <<>> +dnssec +bufsize=1400 +timeout=1 @1.1.1.1 burgasnet.com A
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15620
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 1232
;; QUESTION SECTION:
;burgasnet.com.                 IN      A

;; ANSWER SECTION:
burgasnet.com.          86400   IN      A       45.84.187.163

;; Query time: 26 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Jun 25 11:15:13 2021
;; MSG SIZE  rcvd: 58


The problem is only with dns 8.8.8.8 and 8.8.4.4 . 
I have test with many other dns servers , nad all work fine

according to google Troubleshooting I did the suggested tests and they are positive

root@web:/ # dig -t TXT test.dns.google.com. '@dns.google.'

; <<>> DiG 9.8.4-P2 <<>> -t TXT test.dns.google.com. @dns.google.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56083
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;test.dns.google.com.           IN      TXT

;; ANSWER SECTION:
test.dns.google.com.    5       IN      TXT     "Thanks for using Google Public DNS."

;; Query time: 8 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Fri Jun 25 11:21:16 2021
;; MSG SIZE  rcvd: 85


root@web:/ # dig -t TXT +tcp locations.dns.google.com. '@dns.google.'

; <<>> DiG 9.8.4-P2 <<>> -t TXT +tcp locations.dns.google.com. @dns.google.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12752
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;locations.dns.google.com.      IN      TXT

;; ANSWER SECTION:
locations.dns.google.com. 3600  IN      CNAME   locations.publicdns.goog.

;; Query time: 8 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Jun 25 11:21:36 2021
;; MSG SIZE  rcvd: 80


Please help

Anthony Lieuallen

unread,
Jun 25, 2021, 1:50:46 PM6/25/21
to dian raikov, public-dns-discuss
https://dns.google/query?name=burgasnet.com

Our web app shows an error message "Name servers did not respond [45.84.187.166, 45.84.187.168]."

If I open a Google Cloud Shell and try from there:


; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> @45.84.187.166 burgasnet.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

It appears your authoritative servers (or some network in the path) are blocking packets to or from Google.  We are observing this behavior from all locations in the world.  You might want to check our list of egress IPs in each region ( https://developers.devsite.corp.google.com/speed/public-dns/faq#locations_of_ip_address_ranges_google_public_dns_uses_to_send_queries ) and cross reference it against firewall rules or similar settings.

--
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/public-dns-discuss/ba7233a5-1232-4c32-af93-8d9e27666510n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages