0

High latency to Google domains

Hi!

For at least a couple of days (but quite possibly longer) I've noticed that Google-related domains (google.com, youtube.com etc.) resolve to IP addresses that are, judging by the latency, quite far away from Sweden where I am.

Here are the response times of a regular ping against google.com (with NextDNS as my resolver):

ping google.com
PING google.com (142.250.181.174) 56(84) bytes of data.
64 bytes from mct01s20-in-f14.1e100.net (142.250.181.174): icmp_seq=1 ttl=112 time=140 ms
64 bytes from mct01s20-in-f14.1e100.net (142.250.181.174): icmp_seq=2 ttl=112 time=140 ms
64 bytes from mct01s20-in-f14.1e100.net (142.250.181.174): icmp_seq=3 ttl=112 time=140 ms
64 bytes from mct01s20-in-f14.1e100.net (142.250.181.174): icmp_seq=4 ttl=112 time=140 ms
64 bytes from mct01s20-in-f14.1e100.net (142.250.181.174): icmp_seq=5 ttl=112 time=140 ms
64 bytes from mct01s20-in-f14.1e100.net (142.250.181.174): icmp_seq=6 ttl=112 time=140 ms

Using Google Public DNS to resolve google.com and pinging that IP address specifically, I get the following response times instead:

ping 142.250.74.142
PING 142.250.74.142 (142.250.74.142) 56(84) bytes of data.
64 bytes from 142.250.74.142: icmp_seq=1 ttl=117 time=4.58 ms
64 bytes from 142.250.74.142: icmp_seq=2 ttl=117 time=4.64 ms
64 bytes from 142.250.74.142: icmp_seq=3 ttl=117 time=4.67 ms
64 bytes from 142.250.74.142: icmp_seq=4 ttl=117 time=4.66 ms
64 bytes from 142.250.74.142: icmp_seq=5 ttl=117 time=4.65 ms
64 bytes from 142.250.74.142: icmp_seq=6 ttl=117 time=4.57 ms

I've tried disabling all the performance settings in the NextDNS web UI (Anonymized EDNS Client Subnet etc.) without any real improvements as far as I can tell.

Network Diagnostics: https://nextdns.io/diag/4fab9700-6dce-11ee-b257-1300416f0b1b

Happy to provide any other data that could be useful to pinpoint the issue.

Thanks!

5 replies

null
    • jyggen
    • 1 yr ago
    • Reported - view

    Bump.

    • jyggen
    • 1 yr ago
    • Reported - view

    Still an issue most of the time, though some odd days it resolves to a server close to me for a while. Google and Cloudflare's public DNS servers continue to resolve to low latency servers for Google domains all the time.

    As of writing, NextDNS resolves google.com to 142.251.167.101 (102ms on `ping`) whereas Google Public DNS resolves it to 142.250.74.142 (4ms on `ping`).

    • BigDargon
    • 1 yr ago
    • Reported - view

    Because ECS sent a query, the server IP returned was too far away. Try turning off the EDNS feature in the Settings tab and try again.

    I have reported this bug https://help.nextdns.io/t/g9yqzgr

      • jyggen
      • 1 yr ago
      • Reported - view

      BigDargonI've already given that a try with no difference. I've now again had it off for 24h+ and I still get 100ms+ towards Google domains - so seems like EDNS is unrelated.

    • jyggen
    • 11 mths ago
    • Reported - view

    Ended up cancelling my subscription and moving back to a self-hosted DNS solution instead.

Content aside

  • 11 mths agoLast active
  • 5Replies
  • 236Views
  • 2 Following