Goodle DNS - IPv4 vs IPv6 in Sydney, Australia

251 views
Skip to first unread message

ekimd...@gmail.com

unread,
Oct 1, 2015, 10:09:41 AM10/1/15
to public-dns-discuss
Hello all,

I suspect I know the answer, but here goes;

My nearest Google IPv4 anycast addresses 8.8.8.8 & 8.8.4.4 are about 40mSec away from where I am (I'm in New Zealand, and the 'nearest' Google DNS is in Sydney) - Hosted by Vocus, as far as I can tell.

However, Google IPv6 DNS addressing is 180 - 200mSec away from me, which means it's probably in the USA.

I thought that Google Sydney was IPv6 enabled, but my tests show otherwise.

Any ideas team?

Regards,
Mike Taylor

mitchcrt03#  ping 8.8.8.8
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/41/44 ms

mitchcrt03#traceroute 8.8.8.8
Type escape sequence to abort.
Tracing the route to google-public-dns-a.google.com (8.8.8.8)
VRF info: (vrf in name/id, vrf out name/id)
  1 ppp-chc-loopback.3t.nz (175.111.100.37) 0 msec 4 msec 4 msec
  2 TenGigE0-0-2-1-684.chrev-rt1.fx.net.nz (131.203.245.77) 4 msec 4 msec 0 msec
  3 TenGigabitEthernet0-1-0-310.wnmur-rt1.fx.net.nz (202.53.187.201) 12 msec 8 msec 12 msec
  4 TenGigE0-0-2-0-310.aktnz-art1.fx.net.nz (202.53.187.202) 16 msec 20 msec 16 msec
  5 ten-0-3-0-1002.bdr01.akl05.akl.vocus.net.nz (175.45.102.57) 16 msec 20 msec 16 msec
  6 ten-0-1-0-3.cor01.alb01.akl.VOCUS.net.nz (114.31.202.42) [MPLS: Label 16024 Exp 0] 40 msec 40 msec 40 msec
  7 ten-0-0-0-2.cor03.syd03.nsw.VOCUS.net.au (114.31.199.116) [MPLS: Label 16002 Exp 0] 44 msec
    ten-0-3-0-2.cor03.syd03.nsw.VOCUS.net.au (114.31.202.85) [MPLS: Label 16002 Exp 0] 40 msec
    ten-0-2-1-0.cor03.syd03.nsw.VOCUS.net.au (114.31.202.36) [MPLS: Label 16002 Exp 0] 44 msec
  8 ten-2-1-0.bdr03.syd03.nsw.VOCUS.net.au (114.31.192.43) 40 msec
    ten-1-1-0.bdr03.syd03.nsw.VOCUS.net.au (175.45.72.116) 40 msec 44 msec
  9 as15169.cust.bdr01.syd03.nsw.VOCUS.net.au (114.31.201.18) 40 msec 40 msec 40 msec
 10 216.239.41.77 40 msec 44 msec
    74.125.37.167 40 msec
 11 216.239.41.79 40 msec
    216.239.41.1 44 msec
    209.85.142.219 40 msec
 12 google-public-dns-a.google.com (8.8.8.8) 44 msec 40 msec 44 msec

mitchcrt03#ping 2001:4860:4860::8888
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:4860:4860::8888, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 184/186/188 ms

mitchcrt03#traceroute 2001:4860:4860::8888
Type escape sequence to abort.
Tracing the route to google-public-dns-a.google.com (2001:4860:4860::8888)

  1 2400:6900:1::1:1 4 msec 4 msec 4 msec
  2 TenGigE0-0-2-1-684.chrev-rt1.fx.net.nz (2402:6000:0:200::F3:1) 4 msec 4 msec 4 msec
  3 TenGigabitEthernet1-3-0-308.aktnz-rt1.fx.net.nz (2402:6000:0:5::9:1) 16 msec 16 msec 16 msec
  4 TenGigE0-0-2-0-308.aktnz-art1.fx.net.nz (2402:6000:0:5::9:2) 20 msec *  *
  5 2402:7800:110:511::F9 16 msec 16 msec 20 msec
  6  *  *
    2402:7800:110:1::4C 16 msec
  7 2402:7800:110:1::9E 40 msec *
    2402:7800:110:1::7E 40 msec
  8 ten-1-2-0.bdr03.syd03.nsw.VOCUS.net.au (2402:7800:0:1::56) 40 msec
    ten-2-1-0.bdr03.syd03.nsw.VOCUS.net.au (2402:7800:0:1::46) 44 msec
    2402:7800:0:1::7E 40 msec
  9 google.syd03.nsw.VOCUS.net.au (2402:7800:0:2::2E) 40 msec 40 msec 40 msec
 10 2001:4860::1:0:8604 40 msec 40 msec 40 msec
 11 2001:4860::8:0:79A0 [MPLS: Labels 554724/2 Exp 4] 172 msec
    2001:4860::8:0:81AC 172 msec
    2001:4860::8:0:79A0 172 msec
 12 2001:4860::8:0:8C6F [MPLS: Labels 28446/2 Exp 4] 184 msec 184 msec 184 msec
 13 2001:4860::8:0:73AE [MPLS: Labels 420938/2 Exp 4] 180 msec 176 msec 180 msec
 14 2001:4860::2:0:C6 184 msec
    2001:4860::2:0:B7 184 msec 184 msec
 15  *  *  *
 16 google-public-dns-a.google.com (2001:4860:4860::8888) 180 msec 184 msec 184 msec

mitchcrt03#traceroute google.com
Translating "google.com"...domain server (8.8.8.8) [OK]

Type escape sequence to abort.
Tracing the route to google.com (2404:6800:4003:C00::8B)

  1 2400:6900:1::1:1 4 msec 4 msec 0 msec
  2 TenGigE0-0-2-1-684.chrev-rt1.fx.net.nz (2402:6000:0:200::F3:1) 4 msec 4 msec 4 msec
  3 TenGigabitEthernet1-3-0-308.aktnz-rt1.fx.net.nz (2402:6000:0:5::9:1) 20 msec 16 msec 16 msec
  4 TenGigE0-0-2-0-308.aktnz-art1.fx.net.nz (2402:6000:0:5::9:2) 16 msec 20 msec 16 msec
  5 2402:7800:110:511::F9 20 msec 16 msec 16 msec
  6 2402:7800:110:1::71 20 msec 20 msec 16 msec
  7 2402:7800:110:1::7E 44 msec
    2402:7800:110:1::5E 40 msec
    2402:7800:110:1::7E 40 msec
  8 ten-2-1-0.bdr03.syd03.nsw.VOCUS.net.au (2402:7800:0:1::46) 60 msec
    2402:7800:0:1::7E 40 msec
    ten-1-2-0.bdr03.syd03.nsw.VOCUS.net.au (2402:7800:0:1::56) 40 msec
  9 google.syd03.nsw.VOCUS.net.au (2402:7800:0:2::2E) 40 msec 44 msec 40 msec
 10 2001:4860::1:0:8604 44 msec 56 msec 40 msec
 11 2001:4860::8:0:81AC [MPLS: Labels 600941/2 Exp 4] 168 msec
    2001:4860::8:0:79A0 172 msec 192 msec
 12 2001:4860::8:0:96E9 [MPLS: Labels 25014/2 Exp 4] 200 msec 200 msec
    2001:4860::8:0:8877 204 msec
 13 2001:4860::2:0:AB28 204 msec 204 msec
    2001:4860::2:0:AB29 200 msec
 14  *  *  *
 15 google.com (2404:6800:4003:C00::8B) 204 msec 204 msec 200 msec

Shen Wan

unread,
Oct 1, 2015, 10:22:38 AM10/1/15
to public-dns-discuss
We do not have as many IPv6 locations as IPv4. Please see Wilmer's reply in https://groups.google.com/forum/#!topic/public-dns-discuss/KDoGmEwgJwQ.

Alex Dupuy

unread,
Oct 5, 2016, 10:57:21 AM10/5/16
to public-dns-discuss, ekimd...@gmail.com
Hi Mike,

It has taken a while, but Google Public DNS IPv6 geographical coverage should now be comparable to coverage for IPv4.

Note that although the latency for DNS responses to cached data (frequently accessed domains like www.google.com and many other non-Google ones) should now be comparable for IPv6 and IPv4, you may find that the answers (whether to AAAA (IPv6) or A (IPv4) queries) are different when you look up certain GeoIP-enabled domains via IPv6, e.g.:

$ dig -6 +short www.mi.com @publicdns.goog
204.237.142.160
204.237.142.155
$ dig -4 +short www.mi.com @publicdns.goog
54.192.19.202
54.192.19.81
54.192.19.93
54.192.19.13
54.192.19.67
54.192.19.41
54.192.19.130
54.192.19.6

This is a known issue in the ECS GeoIP configuration in the DNSPod (dnsv5.com) name servers used by mi.com (Xiaomi), which don't handle ECS with IPv6 client addresses correctly.  Most larger (non-Chinese) CDNs will do the right thing, though:


If you re-enable IPv6 addresses for Google Public DNS, you may want to keep an eye out for problems like that, and if you (or other users of any resolvers that you point at Google Public DNS) use Chinese web sites extensively, you might want to stick to IPv4.

@alex

Reply all
Reply to author
Forward
0 new messages