Using DNS Server in Australia while located in Canada

Nakfel_Hagen
10 mths ago
5replies

Hello:

My location is Calgary, Canada but my DNS server points to Melbourne, Australia.

DNS test result: 103.137.14.21 - GSL Networks Pty, Melbourne, Australia

I am using the yearly plan as of November 30, 2023; home user.

Additional information:

- I check https://dnsleaktest.com/ daily as part of my network maintenance checks.

- I login to https://my.nextdns.io daily to check logs.

- The previous location was a server in the United States, and had been like that since I started using the service.

- There has been a noticeable lag increase on the network when browsing the web since yesterday; but it "feels" slower. I am doing more testing right now to confirm this.

Any ideas or suggestions would be appreciated. Thank you.

Here is the diag report:

Client
ASN: AS6327 SHAW
Country: CA
Has IPv6: false
Created: 2023-06-27T15:00:37.000Z
Status
SrcIP:
Client:
DestIP:
Server: gsl-mel-1
Status: ok
Protocol: UDP
Top
anexia-yvr 20 ms (ultralow1)
cacloud-yvr 25 ms (ultralow2)
zepto-sea 31 ms (anycast2)
vultr-sea 31 ms
directspace-pdx 36 ms
tier-pdx 41 ms
vultr-yto 52 ms
xmission-slc 62 ms
bronto-slc 73 ms
anexia-yto 83 ms
Steering
Ultra Low Latency
Primary: anexia-yvr (26 ms)
1 192.168.2.1 2 ms 1 ms 2 ms
2 68.146.0.1 13 ms 12 ms 11 ms AS6327 SHAW
3 rc3so-be159-1.cg.shawcable.net (64.59.132.209) 12 ms 12 ms 13 ms AS6327 SHAW
4 24.244.57.209 12 ms 12 ms 12 ms AS6327 SHAW
5 24.244.60.117 12 ms 11 ms 12 ms AS6327 SHAW
6 rc3so-be214.cg.shawcable.net (24.244.57.21) 12 ms 11 ms 12 ms AS6327 SHAW
7 rc1bb-be6-1.vc.shawcable.net (66.163.78.38) 23 ms 24 ms 23 ms AS6327 SHAW
8 * * * *
9 * * * *
10 208.98.192.198 28 ms 28 ms 23 ms AS6327 SHAW
11 37.252.226.32 26 ms 26 ms 24 ms AS42473 ANEXIA Internetdienstleistungs GmbH
12 dns.nextdns.io (188.172.213.149) 23 ms 25 ms 25 ms AS42473 ANEXIA Internetdienstleistungs GmbH
Secondary: cacloud-yvr (26 ms)
1 192.168.2.1 2 ms 2 ms 1 ms
2 68.146.0.1 12 ms 12 ms 13 ms AS6327 SHAW
3 rc3so-be159-1.cg.shawcable.net (64.59.132.209) 13 ms 11 ms 11 ms AS6327 SHAW
4 24.244.57.209 12 ms 12 ms 12 ms AS6327 SHAW
5 24.244.60.117 12 ms 12 ms 11 ms AS6327 SHAW
6 rc3so-be214.cg.shawcable.net (24.244.57.21) 13 ms 12 ms 11 ms AS6327 SHAW
7 rc3no-be23.cg.shawcable.net (66.163.71.117) 13 ms 13 ms 14 ms AS6327 SHAW
8 rc1st-be11-1.vc.shawcable.net (66.163.72.70) 24 ms 24 ms 24 ms AS6327 SHAW
9 as13768.vanix.ca (206.41.104.1) 23 ms 24 ms 23 ms
10 xe-7-0-0.van-hc16e-dis-1.peer1.net (216.187.88.217) 25 ms 30 ms 23 ms
11 64.34.109.172 24 ms 24 ms 24 ms AS13768 COGECO-PEER1
12 dns.nextdns.io (104.36.148.181) 28 ms 26 ms 28 ms AS54643 IDIGITAL
Anycast
Primary: gsl-mel (206 ms)
1 192.168.2.1 2 ms 1 ms 2 ms
2 68.146.0.1 12 ms 11 ms 12 ms AS6327 SHAW
3 rc3so-be159-1.cg.shawcable.net (64.59.132.209) 11 ms 12 ms 12 ms AS6327 SHAW
4 24.244.57.209 17 ms 13 ms 12 ms AS6327 SHAW
5 24.244.60.117 12 ms 12 ms 11 ms AS6327 SHAW
6 rc3so-be214.cg.shawcable.net (24.244.57.21) 11 ms 11 ms 13 ms AS6327 SHAW
7 rc1wt-be82.wa.shawcable.net (66.163.76.9) 34 ms 35 ms 33 ms AS6327 SHAW
8 peering.sea-drtsea10.globalsecurelayer.com (206.148.27.242) 33 ms 32 ms 33 ms AS174 COGENT-174
9 po2.sea-drtsea10-bb1.globalsecurelayer.com (206.148.25.8) 35 ms 36 ms 33 ms AS174 COGENT-174
10 e49.lax-csla2-bb1.globalsecurelayer.com (206.148.25.6) 63 ms 64 ms 64 ms AS174 COGENT-174
11 206.148.27.251 63 ms 63 ms 64 ms AS174 COGENT-174
12 206.148.27.250 63 ms 63 ms 63 ms AS174 COGENT-174
13 e31.syd.sy5-cr2.gslnetworks.com (103.137.13.96) 195 ms 194 ms 196 ms AS7578 Global Secure Layer
14 p201.syd.sy5-cr1.gslnetworks.com (223.165.7.15) 195 ms 200 ms 195 ms AS7578 Global Secure Layer
15 e72.mel.me1-cr1.gslnetworks.com (103.137.13.89) 205 ms 205 ms 206 ms AS7578 Global Secure Layer
16 mel.gslnetworks.com (103.137.13.209) 205 ms 206 ms 205 ms AS7578 Global Secure Layer
17 dns1.nextdns.io (45.90.28.0) 206 ms 206 ms 207 ms AS34939 nextdns, Inc.
Secondary: zepto-sea (30 ms)
1 192.168.2.1 33 ms 2 ms 2 ms
2 68.146.0.1 11 ms 11 ms 11 ms AS6327 SHAW
3 rc3so-be159-1.cg.shawcable.net (64.59.132.209) 11 ms 11 ms 15 ms AS6327 SHAW
4 24.244.57.209 11 ms 11 ms 14 ms AS6327 SHAW
5 24.244.60.117 11 ms 12 ms 12 ms AS6327 SHAW
6 rc3so-be214.cg.shawcable.net (24.244.57.21) 11 ms 10 ms 12 ms AS6327 SHAW
7 rc1wt-be82.wa.shawcable.net (66.163.76.9) 34 ms 35 ms 36 ms AS6327 SHAW
8 sea-b1-link.ip.twelve99.net (213.248.67.224) 33 ms 33 ms 38 ms AS1299 Telia Company AB
9 datacamp-ic-356844.ip.twelve99-cust.net (80.239.193.194) 33 ms 34 ms 34 ms AS1299 Telia Company AB
10 po77-3528.cr01.sea02.us.misaka.io (84.17.33.9) 34 ms 34 ms 35 ms AS60068 Datacamp Limited
11 po-29.lag.sea02.us.misaka.io (170.39.227.9) 35 ms 34 ms 34 ms AS917 MISAKA
12 dns2.nextdns.io (45.90.30.0) 35 ms 35 ms 35 ms AS34939 nextdns, Inc.

- Nakfel_Hagen
- 10 mths ago
- Reported - view
After some testing I can confirm as a current issue.

It is affecting websites and services, pointing to location change.

I will disconnect from NextDNS.IO in the meantime and monitor the issue.

Thank you.
- losnad
- 10 mths ago
- Reported - view
If you stop using IPv4 or IPv6 and you would start using encrypted DNS your device will be routed on the ultralow network.

https://help.nextdns.io/t/p8hw3vp/adding-multiple-routers-to-paid-home-user?r=h7hwxq5#h7hwxq5
- Nakfel_Hagen
  
  10 mths ago
  
  Reported - view
  losnad
  
  Thanks for the reply.
  
  I am using the dnsmasq config in the firewall/router which is Untangle. At https://my.nextdns.io/ I could see traffic logged.
  
  With the above configuration a test at https://dnssec-tools.org/test/ would pass, and https://dnsleaktest.com/ would resolve to a DNS Server in the United States. Now it still resolves to Australia.
  
  So I thought I was using encrypted DNS, but your comment states otherwise. I appreciate you taking the time to point that out. Thank you.
  
  I've read your reply, followed the link and did some digging around; but truly I don't have the knowledge to understand how to implement what you mentioned.
  
  I need to learn more about this topic.
  
  Regardless, thanks for your help.
- Nakfel_Hagen
  
  10 mths ago
  
  Reported - view
  Nakfel Hagen The devices I have support linked IP or dnsmasq.
  
  Using this configuration, from Calgary the DNS leak tests that I ran pointed to servers in the United States until yesterday.
  
  Now they still resolve to Melbourne, Australia.
  
  I created a test profile to check on another device, an old Asus RT-AC68U.
  
  I will keep checking, but the problem does persist with general lag and apps having location issues.
  
  Thank you.
- Nakfel_Hagen
- 10 mths ago
- Reported - view
Resolved as of July 2nd, 2023.

Now when using NextDNS from Canada it resolves the Seattle instead of Australia, lag greatly reduced.

Thank you!

149.248.36.234 dns.nextdns.io. Choopa, LLC Seattle, United States

Content aside

10 mths agoLast active
5Replies
209Views
1 Following

Using DNS Server in Australia while located in Canada

5 replies

Content aside

Home

Tags