Intermittent google.com DNS resolving issues

[rbrb...@gmail.com]

For last week or so I have had intermittent issues with what I think is resolving google.com addresses.  This includes basic google.com searches, using maps - maps.google.com, Gmail - mail.gmail.com, etc...  No issues with non-google.com addresses.  Youtube is fine.  Can get to say google.co.uk.

My understanding is limited of these configurations.  I think the problem is with ipv6.  For example, from this article:

https://developers.google.com/speed/public-dns/docs/troubleshooting

On step 2 doing tracert -d 2001:4860:4860::8888

I get:

Tracing route to 2001:4860:4860::8888 over a maximum of 30 hops

  1  Transmit error: code 1231.

Trace complete.

I have reset my router, tried to change DNS servers to multiple options (google, opendns, etc...)

The issues are intermittent but at times quite frustrating.  I am not a fan of bing and that is what I am heading to.

When I go to: https://dnsviz.net/d/google.com/dnssec/

I get errors:

• google.com zone: The server(s) were not responsive to queries over UDP. (2001:4860:4802:32::a, 2001:4860:4802:34::a, 2001:4860:4802:36::a, 2001:4860:4802:38::a)
• google.com/A: No response was received from the server over UDP (tried 12 times). (2001:4860:4802:32::a, 2001:4860:4802:34::a, 2001:4860:4802:36::a, 2001:4860:4802:38::a, UDP_-_NOEDNS_)
• google.com/NS: No response was received from the server over UDP (tried 12 times). (2001:4860:4802:32::a, 2001:4860:4802:34::a, 2001:4860:4802:36::a, 2001:4860:4802:38::a, UDP_-_NOEDNS_)

https://intodns.com/google.com

I get following warnings/errors:

SOA REFRESH

WARNING: Your SOA REFRESH interval is: 900. That is not so ok

SOA EXPIRE

Your SOA EXPIRE number is: 1800. That is NOT OK

Different MX records at nameservers

The MX records that are not the same at all your nameservers: aspmx.l.google.com with ip(s): 74.125.140.26  reported only by: 216.239.36.10 216.239.38.10 aspmx.l.google.com with ip(s): 74.125.133.26  reported only by: 216.239.34.10 aspmx.l.google.com with ip(s): 66.102.1.26  reported only by: 216.239.32.10 It is better to have the same MX records at all your nameservers!

Reverse MX A records (PTR)

ERROR: No reverse DNS (PTR) entries. The problem MX records are: 26.4.250.142.in-addr.arpa -> no reverse (PTR) detected You should contact your ISP and ask him to add a PTR record for your ips

This is kind of the limit of my knowledge.  Done the virus scans.  Threw pixie dust at the screen.  Prayed to the alter of the IBM x86.

Any help is appreciated.

[Michael Batchelder]

> On step 2 doing tracert -d 2001:4860:4860::8888

Ensure that your command syntax is correct for an IPv6 traceroute:

https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/tracert

Then run traces and pings (ping -6 <address>) to google DNS and some other IPv6 targets. You can use other public DNS resolvers, like Cloudflare (2606:4700:4700::1111). That'll tell you if you have an IPv6 routing issue.

Michael

--
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/bd83626d-35e7-481b-827c-02c3a1e6a118o%40googlegroups.com.

[David T Smith]

1-3 nights ago (started around 11pm and was still an issue at 2am) Google dns (and other Google services) in the Atlanta were not responding to ipv4 requests, had to add 1.1.1.1 to my router DNS server list to get other websites.

Nothing listed on https://www.google.com/appsstatus#hl=en&v=status

But others were reporting problems on isitdown.com