TPG Community

Get online support

Bad pings to Quad9 DNS on TPG ip

Highlighted
Level 1a

Quad9 is like OpenDNS with build in malware block
I have some problems with TPG speeds in regards to using Quad9 dns server.

Quad9 is like OpenDNS with build in malware blocking and is faster than TPG dns for downloading from international sites

It has a local sydney server.

It appears there is some routing issues with TPG that the Quad9 dns does not recognise a local DNS pop.

Here is pings without VPN on normal TPG ip address

C:\Users\Me>ping 9.9.9.9 -t

Pinging 9.9.9.9 with 32 bytes of data:
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=168ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=168ms TTL=59
Reply from 9.9.9.9: bytes=32 time=168ms TTL=59
Reply from 9.9.9.9: bytes=32 time=168ms TTL=59
Reply from 9.9.9.9: bytes=32 time=168ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=169ms TTL=59
Reply from 9.9.9.9: bytes=32 time=168ms TTL=59
Reply from 9.9.9.9: bytes=32 time=168ms TTL=59

Ping statistics for 9.9.9.9:
Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 169ms, Average = 168ms
Control-C
^C

Here is tracert without VPN

C:\Users\Me>tracert 9.9.9.9

Tracing route to dns9.quad9.net [9.9.9.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 14 ms 14 ms 10.20.22.125
3 16 ms 21 ms 21 ms syd-apt-ros-int1-eth8-3.tpgi.com.au [203.29.134.67]
4 203 ms 199 ms 186 ms 100ge13-1.core1.sjc1.he.net [216.218.139.233]
5 171 ms 170 ms 170 ms 206.41.106.52
6 169 ms 168 ms 168 ms dns9.quad9.net [9.9.9.9]

Trace complete.

Now here is speeds and tracert with a VPN, notice how much quicker the ping speeds are.

C:\Users\Me>ping 9.9.9.9 -t

Pinging 9.9.9.9 with 32 bytes of data:
Reply from 9.9.9.9: bytes=32 time=16ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=16ms TTL=58
Reply from 9.9.9.9: bytes=32 time=18ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=22ms TTL=58
Reply from 9.9.9.9: bytes=32 time=19ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=16ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58
Reply from 9.9.9.9: bytes=32 time=17ms TTL=58

Ping statistics for 9.9.9.9:
Packets: Sent = 26, Received = 26, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 22ms, Average = 17ms
Control-C
^C

C:\Users\Me>tracert 9.9.9.9

Tracing route to dns9.quad9.net [9.9.9.9]
over a maximum of 30 hops:

1 * * * Request timed out.
2 17 ms 17 ms 17 ms rtif-221.121.132.1-25.cs-16.as45671.net.au [221.121.132.1]
3 17 ms 17 ms 18 ms rtif-118.127.7.70-31.cs-6.as45671.net.au [118.127.7.70]
4 17 ms 17 ms 17 ms ten2-2.br-6-1.as45671.net.au [203.26.198.39]
5 18 ms 17 ms 18 ms as42.nsw.ix.asn.au [218.100.52.27]
6 17 ms 17 ms 16 ms dns9.quad9.net [9.9.9.9]

Trace complete.

 

Who can i speak to to have this looked at? Ta

3 REPLIES 3
Highlighted
Moderator

Hi @Pinkyoshi,

 

Welcome to TPG Community!

 

We were able to locate your account using your community details and understand that you've contacted our Tech team.

 

We are using the best route possible that will be given by our routing partners. It appears that the router wasn't able to detect the local routing host.

 

Also, using a VPN connection is quite different to the connection from any local internet service provider, you may expect different routing result. Who is your VPN provider?

 

How VPN works?

- A VPN works by routing your device's internet connection through your chosen VPN's private server rather than your internet service provider (ISP) so that when your data is transmitted to the internet, it comes from the VPN rather than your computer.

 

If you are able to test the Quad9 DNS using other local Australian ISP (Telstra, Optus, etc.), then we may use the result to compare and raise it to our routing partners if possible.

 

BasilDV

Highlighted
Level 1a

i used looking glass from a few ISPs. 

 

Telstra seems to have same issues as TPG

 

HOWEVER

 

iinet and more importantly aussiebb (tpg main competitor of late) both able to access quad9 local POPs

 

Here is example

 

iinet is peering with equinix so it gets 4ms ping

 

 

iNet (AS4739) Looking Glass
Router: AS4739 – Sydney, AU
Command: traceroute ip 9.9.9.9

Tracing the route to dns9.quad9.net (9.9.9.9)

1 gi1-2-950.cor1.syd6.on.ii.net (150.101.199.50) 0 msec 0 msec 0 msec
2 te-0-9-1-3.cr2.syd7.on.ii.net (150.101.40.164) 0 msec 0 msec 0 msec
3 ae6.cr2.syd4.on.ii.net (150.101.41.124) 4 msec 4 msec 4 msec
4 42.syd.equinix.com (45.127.172.68) 0 msec 4 msec 0 msec

 

 

Aussie broadband picks up quad9 easily as well

1 be10-546.bng1.vdc01.syd.aussiebb.net (119.18.32.152) 1.121 ms 0.790 ms 0.770 ms
2 HundredGigE0-0-0-8.core2.vdc01.syd.aussiebb.net (180.150.1.186) 1.214 ms 1.245 ms 0.965 ms
3 HundredGigE0-0-0-8.core2.vdc01.syd.aussiebb.net (180.150.1.186) 0.584 ms 0.795 ms 0.624 ms
4 as42.sydney.megaport.com (103.26.68.95) 12.303 ms 12.390 ms 12.503 ms
5 dns9.quad9.net (9.9.9.9) 0.711 ms !Z 0.728 ms !Z 0.755 ms 

 

 

As you can see iinet peers via equinix

 

and aussiebroadband peers with megaport

Moderator

Thank you, @Pinkyoshi.

 

We'll raise this to our Network Engineers for further investigation.

 

Please send me a PM with your preferred number to be contacted once an update becomes available.

 

BasilDV