1

Very high latencty with Free Mobile + roaming (wrong edge server used)

Hello,

I'm a Free Mobile customer and currently in the US. My Android phone is configured to use NextDNS with built-in DoT (but behavior is the same with the NextDNS App).

I believe the issue is that even though I'm roaming, Free gives me an IP address announced by their AS51207 (37.170.144.102 for instance ATM) and also configures the connection with their DNS (212.27.40.240 / 212.27.40.241).

It leads NextDNS to believe I'm obviously in France and thus selects the wrong edge server:

{
"status": "ok",
"protocol": "DOT",
"profile": "fpa9f570c5deeb6bfb",
"client": "37.170.144.102",
"srcIP": "37.170.144.102",
"destIP": "193.168.204.73",
"anycast": false,
"server": "netbarista-par-1",
"clientName": "unknown-dot"
}

Same with the ping output, which only selects edges close to France:

virtua-par 165 ms (anycast2)
anexia-mrs 190 ms
anexia-par 204 ms (ultralow1)
fusa-bru 204 ms
anexia-lon 206 ms
anexia-lux 214 ms
zepto-mrs 218 ms
vultr-lon 220 ms
■ netbarista-par 224 ms (anycast1, ultralow2)
zepto-bru 273 ms

If I do the same from my Hotel Wifi, it works as expected:

  anexia-ewr        7 ms  (anycast2, ultralow1)
  vultr-ewr         9 ms  (anycast1, ultralow2)
  smarthost-bos    13 ms
  anexia-mnz       13 ms
  zepto-iad        14 ms
  axcelx-bos       15 ms
  zepto-xrs        15 ms
  hetzner-iad      16 ms
  teraswitch-pit   27 ms
  router-pit       68 ms

Is there a way to fix this or to force NextDNS to use a specific while retaining my configuration id, because having 200ms on each DNS query makes everything really slow.

Reply

null

Content aside

  • 1 Likes
  • 2 yrs agoLast active
  • 68Views
  • 2 Following