Australia's biggest ISP is routing to US servers instead of Sydney

[jupester]

Hi, I am a customer of Australia's largest ISP (so a large amount of users will be affected by this) and since recently Adguard DNS always uses LA or Chicago DNS servers instead of the preferable Sydney one, it seems a common issue that the nearest server isn't used in many countries going by the open/closed issues, and you mentioned in one of those topics that sometimes it is any easy fix and sometimes it is not, hopefully you can look into this issue and see if it is possible to fix easily since it is a long way overseas to a US server in this case.

I will provide a screenshot of the traceroute from my ISP since I live in Victoria (not NSW where Sydney is) but below that is also a text excerpt from the looking glass tool (also link to that provided below) which shows even my ISP's main Sydney POP routes overseas instead of to AdGuards Sydney DNS server which is in the same city.

I don't have ipv6 so haven't included those traceroute results.

https://lg.telstraglobal.com/

1 i-91.sydp-core04.telstraglobal.net (202.84.222.85) 2 msec 1 msec 2 msec 2 i-91.sydp-core04.telstraglobal.net (202.84.222.85) [MPLS: Label 25165 Exp 0] 137 msec 136 msec 137 msec 3 i-20802.eqnx-core02.telstraglobal.net (202.84.141.25) 137 msec 137 msec 136 msec 4 i-92.eqnx03.telstraglobal.net (202.84.247.17) 135 msec 135 msec 135 msec 5 134.159.61.78 135 msec 135 msec 135 msec 6 Hu0-0-0-0.br06.chc01.pccwbtn.net (63.218.4.186) 182 msec 183 msec 182 msec 7 Hu0-0-0-0.br06.chc01.pccwbtn.net (63.218.4.186) 182 msec 182 msec 182 msec 8 209.8.108.66 186 msec 186 msec 186 msec 9 dns.adguard.com (94.140.14.14) 186 msec 186 msec 187 msec

1 i-91.sydp-core04.telstraglobal.net (202.84.222.85) 2 msec 1 msec 0 msec 2 i-91.sydp-core04.telstraglobal.net (202.84.222.85) [MPLS: Label 25165 Exp 0] 135 msec 136 msec 136 msec 3 i-20802.eqnx-core02.telstraglobal.net (202.84.141.25) 136 msec 135 msec 136 msec 4 i-92.eqnx03.telstraglobal.net (202.84.247.17) 135 msec 136 msec 135 msec 5 134.159.61.78 135 msec 135 msec 135 msec 6 Hu0-0-0-0.br06.chc01.pccwbtn.net (63.218.4.186) 182 msec 182 msec 182 msec 7 Hu0-0-0-0.br06.chc01.pccwbtn.net (63.218.4.186) 182 msec 182 msec 182 msec 8 209.8.108.66 186 msec 186 msec 186 msec 9 dns.adguard.com (94.140.15.15) 187 msec 186 msec 186 msec

Anyway up until recently thanks for supplying a great service, hopefully this issue is able to be rectified, thanks in advance.

[ameshkov]

Yeah, approximately half of the Australian users are routed to Chi/La servers. We'll need time to adjust BGP and reroute them to the proper location.

[jupester]

Is there an rough ETA on this getting resolved?, I noticed another user just reported the same issue,

https://github.com/AdguardTeam/AdGuardDNS/issues/335

[ameshkov]

Sorry that it takes so long, resolving this kind of issues requires communicating to ISPs and this takes time (but only the first time).

[D13410N3]

Can you please check your routing now?

[jupester]

Yes, thanks, I noticed it had changed 2 days ago, I was just waiting a couple days to make sure it was stable, before replying, I will included an updated traceroute just for your info. It is a massive change for me, less hops, and faster, I have also included the results from my ISP looking glass tool, which is also slightly faster and a couple less hops, but the change isn't as prominent as mine.

Thanks very much.