cloudflare IPv6 DNS pings quite high.

Forums › One New Zealand (including Vodafone, WxC, Farmside) › cloudflare IPv6 DNS pings quite high.

jlittle

147 posts

Master Geek

Subscriber

#269741 5-Apr-2020 18:44

I get pings averaging about 8 ms on 1.1.1.1; that's the same as the Vodafone DNS (which the Ultrahub tells me is 203.109.191.1), which suggests they're the same server, or if not, at the same location. That's not much more than the Ultrahub just across the house at 4 ms.

But with IPv6 it's a different story. Cloudflare's 2606:4700:4700::1111 gives an average of 131 ms, suggesting a trip to the US west coast. But to Vodafone's 2407:7000:2100:5300::1 it's 8 ms.

I wonder why? Is my ignorance showing? Any explanation appreciated.

Linux

10294 posts

Uber Geek

Trusted

Lifetime subscriber

#2455279 5-Apr-2020 18:49

What does a trace route show / pathping show?

Pluralsight

Learn cloud, mobile, security, data and web technologies with Pluralsight (affiliate link).

gaddman

224 posts

Master Geek

Trusted

#2455283 5-Apr-2020 18:51

Yeah, that doesn't look right - it should be, and used to be, the same latency on both v4 and v6. I'll get someone to take a look.

hio77

'That VDSL Cat'
12982 posts

Uber Geek

ID Verified

Trusted

Voyager

Subscriber

#2455290 5-Apr-2020 19:06

you shouldn't be testing dns purely based on latency, that's got a ton of pitfalls if your trying to find the 'fastest' GRC put out a pretty decent tool to get a better idea.

Remember to consider feature sets too when looking at switching, the likes of EDNS0 shouldn't be overlooked.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

timmmay

19626 posts

Uber Geek

Trusted

Lifetime subscriber

#2455350 5-Apr-2020 19:56

Poor routing was one reason I left Vodafone.

2degrees fiber, ip4 is a touch faster - it has fewer hops. Bit odd that ip6 goes through metaport and Vocus.

Pinging 2606:4700:4700::1111 with 32 bytes of data:
Reply from 2606:4700:4700::1111: time=15ms
Reply from 2606:4700:4700::1111: time=15ms
Reply from 2606:4700:4700::1111: time=15ms
Reply from 2606:4700:4700::1111: time=15ms

Ping statistics for 2606:4700:4700::1111:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 15ms, Average = 15ms

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=13ms TTL=60
Reply from 1.1.1.1: bytes=32 time=13ms TTL=60
Reply from 1.1.1.1: bytes=32 time=12ms TTL=60
Reply from 1.1.1.1: bytes=32 time=12ms TTL=60

Ping statistics for 1.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 13ms, Average = 12ms

Tracing route to one.one.one.one [2606:4700:4700::1111]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms fritz.box [2406:e006:2dd8:3001:2e3a:fdff:fed6:429c]
2 6 ms 5 ms 4 ms 2406:e000:2801:c::1
3 12 ms 13 ms 13 ms as23655.auckland.megaport.com [2001:dea:0:40::4d]
4 38 ms 37 ms 37 ms as4826.auckland.megaport.com [2001:dea:0:40::12]
5 38 ms 37 ms 37 ms bundle-11.cor01.alb01.akl.vocus.net.nz [2402:7800:110:1::35]
6 40 ms 37 ms 37 ms BE-101.bdr03.akl05.akl.VOCUS.net.nz [2402:7800:110:1::7a]
7 13 ms 13 ms 14 ms asn13335.cust.bdr01.akl05.akl.VOCUS.net.nz.0.1.1.0.0.0.8.7.2.0.4.2.ip6.arpa [2402:7800:110:511::13e]
8 12 ms 13 ms 13 ms one.one.one.one [2606:4700:4700::1111]

tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms fritz.box [192.168.1.1]
2 3 ms 5 ms 2 ms 69.7.69.111.static.snap.net.nz [111.69.7.69]
3 15 ms 12 ms 14 ms snap1.ape.nzix.net [192.203.154.120]
4 17 ms 24 ms 14 ms cloudflare.ape.nzix.net [192.203.154.51]
5 15 ms 13 ms 14 ms one.one.one.one [1.1.1.1]

jlittle

147 posts

Master Geek

Subscriber

#2455364 5-Apr-2020 20:47

Linux:

What does a trace route show / pathping show?

traceroute to 1.1.1.1 (1.1.1.1), 64 hops max
1 192.168.1.1 3.879ms 3.682ms 3.690ms
2 118.92.3.254 30.691ms 7.117ms 8.022ms
3 203.97.78.54 7.493ms 12.257ms 7.833ms
4 203.97.78.53 8.088ms 8.161ms 7.641ms
5 198.41.236.253 8.362ms 8.699ms 7.480ms
6 1.1.1.1 7.025ms 7.874ms 7.906ms

traceroute to 2606:4700:4700::1111 (2606:4700:4700::1111) from 2407:7000:818c:bf00:54e8:eac3:c453:bece, 30 hops max, 24 byte packets
1 2407:7000:818c:bf00:1213:31ff:fea8:73a0 (2407:7000:818c:bf00:1213:31ff:fea8:73a0) 4.0836 ms 3.8485 ms 3.8801 ms
2 lo20.bng1-mdr-akl.vf.net.nz (2407:7000::1407) 10.3874 ms 8.3603 ms 7.8598 ms
3 2407:7000:2100:5381::1 (2407:7000:2100:5381::1) 8.7262 ms 8.3873 ms 7.5962 ms
4 * * *
5 2001:5014:300:d::2 (2001:5014:300:d::2) 131.8177 ms 132.0434 ms 132.1777 ms
6 e0-6.switch1.lax2.he.net (2001:470:1:7f4::1) 131.2190 ms 134.9171 ms 133.2136 ms
7 2001:504:13::211:63 (2001:504:13::211:63) 132.5859 ms 137.2604 ms 132.9511 ms
8 2400:cb00:12:1024::ac45:2073 (2400:cb00:12:1024::ac45:2073) 131.5840 ms 132.4897 ms 131.8691 ms

jlittle

147 posts

Master Geek

Subscriber

#2455369 5-Apr-2020 20:57

hio77:

you shouldn't be testing dns purely based on latency, that's got a ton of pitfalls...

I was just idly checking out the new 1.1.1.2 and 1.1.1.3 services (loosely considering censorship a service), and ran pings to see if they were any different from the 1.1.1.1. The reports of the new DNS didn't mention the IPv6 versions, so I checked out the obvious counterparts.

To use the GRC DNSBench.exe I'll have to install Wine... I'll make a note if I'm into serious DNS testing.

Bugzptr

43 posts

Geek

ID Verified

Lifetime subscriber

#2455455 6-Apr-2020 08:00

I'd like to echo this, I'm seeing ipv6 traffic for Cloudflare seeming travelling the scenic route.

Tracing route to www.geekzone.co.nz [2606:4700:20::681a:9fb]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 2407:7000:9d36:8e00::1
2 33 ms 9 ms 9 ms 2407:7000::7207
3 8 ms 10 ms 10 ms 2407:7000:f402::1
4 145 ms 145 ms 146 ms 2001:550:2:18::46:2
5 146 ms 147 ms 147 ms te0-1-0-1.ccr41.lax04.atlas.cogentco.com [2001:550:2:18::46:1]
6 * 148 ms 146 ms be3271.ccr41.lax01.atlas.cogentco.com [2001:550:0:1000::9a36:2a65]
7 146 ms 146 ms 148 ms be3243.ccr41.lax05.atlas.cogentco.com [2001:550:0:1000::9a36:1b76]
8 147 ms 153 ms 147 ms 2001:550:2:67::1a:2
9 146 ms 145 ms 146 ms 2606:4700:20::681a:9fb

Trace complete.

Tracing route to www.geekzone.co.nz [104.26.9.251]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.101.254
2 9 ms 8 ms 9 ms 203-118-151-254.ihug.net [203.118.151.254]
3 10 ms 10 ms 10 ms 203.167.224.158
4 8 ms 9 ms 9 ms 203.167.224.157
5 21 ms 21 ms 22 ms 198.41.236.254
6 24 ms 25 ms 23 ms 198.41.236.253
7 21 ms 21 ms 21 ms 104.26.9.251

Trace complete.

jlittle

147 posts

Master Geek

Subscriber

#2460533 13-Apr-2020 14:03

A week later, and IPv6 traffic to geekzone.co.nz is still going via what appears to be California:

traceroute6 geekzone.co.nz
traceroute to geekzone.co.nz (2606:4700:20::681a:9fb) from 2407:7000:818c:bf00:5549:dca6:a925:e709, 30 hops max, 24 byte packets
1 2407:7000:818c:bf00:1213:31ff:fea8:73a0 (2407:7000:818c:bf00:1213:31ff:fea8:73a0) 4.3548 ms 5.1578 ms 3.9937 ms
2 lo20.bng1-mdr-akl.vf.net.nz (2407:7000::1407) 12.4627 ms 6.8375 ms 7.5568ms
3 2407:7000:2100:5381::1 (2407:7000:2100:5381::1) 9.8129 ms 10.8108 ms 6.6656 ms
4 * * *
5 2001:5014:300:d::2 (2001:5014:300:d::2) 133.3071 ms 133.7614 ms 131.7625 ms
6 te0-1-0-1.ccr41.lax04.atlas.cogentco.com (2001:550:2:18::46:1) 132.4330 ms 132.2821 ms 132.0513 ms
7 * * *
8 be3359.ccr41.lax05.atlas.cogentco.com (2001:550:0:1000::9a36:346) 133.6653 ms 134.8073 ms 132.0034 ms
9 2001:550:2:67::1a:2 (2001:550:2:67::1a:2) 131.7161 ms 132.6574 ms 132.7204 ms
10 2400:cb00:12:1024::ac45:207c (2400:cb00:12:1024::ac45:207c) 131.1065 ms 133.6668 ms 132.2799 ms

IPv4 is very quick to geekzone.co.nz.

Does vodafone not care? Or is there some Spark-like attitude problem?

Linux

10294 posts

Uber Geek

Trusted

Lifetime subscriber

#2460538 13-Apr-2020 14:08

jlittle:

A week later, and IPv6 traffic to geekzone.co.nz is still going via what appears to be California:

traceroute6 geekzone.co.nz
traceroute to geekzone.co.nz (2606:4700:20::681a:9fb) from 2407:7000:818c:bf00:5549:dca6:a925:e709, 30 hops max, 24 byte packets
1 2407:7000:818c:bf00:1213:31ff:fea8:73a0 (2407:7000:818c:bf00:1213:31ff:fea8:73a0) 4.3548 ms 5.1578 ms 3.9937 ms
2 lo20.bng1-mdr-akl.vf.net.nz (2407:7000::1407) 12.4627 ms 6.8375 ms 7.5568ms
3 2407:7000:2100:5381::1 (2407:7000:2100:5381::1) 9.8129 ms 10.8108 ms 6.6656 ms
4 * * *
5 2001:5014:300:d::2 (2001:5014:300:d::2) 133.3071 ms 133.7614 ms 131.7625 ms
6 te0-1-0-1.ccr41.lax04.atlas.cogentco.com (2001:550:2:18::46:1) 132.4330 ms 132.2821 ms 132.0513 ms
7 * * *
8 be3359.ccr41.lax05.atlas.cogentco.com (2001:550:0:1000::9a36:346) 133.6653 ms 134.8073 ms 132.0034 ms
9 2001:550:2:67::1a:2 (2001:550:2:67::1a:2) 131.7161 ms 132.6574 ms 132.7204 ms
10 2400:cb00:12:1024::ac45:207c (2400:cb00:12:1024::ac45:207c) 131.1065 ms 133.6668 ms 132.2799 ms

IPv4 is very quick to geekzone.co.nz.

Does vodafone not care? Or is there some Spark-like attitude problem?

@jlittle I am sure the carriers have better things to worry about right now than this!

michaelmurfy

cat
12219 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#2460543 13-Apr-2020 14:15

Because of COVID, providers will be focusing on more important things.

Voda will get around to it. Just not straight away.

Michael Murphy | https://murfy.nz
Referral Links: Tessie | Tesla | Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

gaddman

224 posts

Master Geek

Trusted

#2460549 13-Apr-2020 14:36

Looks like we're still waiting on a response from Cloudflare's NOC, I've asked the team to give it a chase.

jlittle

147 posts

Master Geek

Subscriber

#2460821 13-Apr-2020 22:24

michaelmurfy:

Because of COVID, providers will be focusing on more important things.

Doh. 🤦