0

IOS Profile wrong DNS location

Hi.

Last 4 months I'm getting wrong location with IOS profile and Nextdns app on iPhone.

I'm based in Sweden but are getting Lithuania DNS server on IP 62.77.154.193  and hostname 1fc8.l.hostens.cloud.
While on the app, I'm getting randomly assigned to Oslo and Copenhagen.
This has been happening more and more.

I have private relay off. I have tried every possible solution, but nothing is working.
Furthermore,  I tried disabling "Anonymized EDNS Client Subnet", same thing again, a random country.

I want to enlighten that this been happening since the summer. Nothing new when I'm reading other threads here and on reddit.

 

Can you guys create a server based in Gothenburg? Or what are the options here? 

9 replies

null
    • DJKatastrof
    • 1 mth ago
    • Reported - view

    With "Ultra-low latency"

    Second same and thirs without ultra-low.

    • BigDargon
    • 1 mth ago
    • Reported - view

    If you are using 4G, native dns will depend on your carrier's DNS server. The carrier's DNS server will resolve the domain name *.dns.nextdns.io to find the NextDNS ultralow server IP address.

    If you are using wifi at home and you have access to the modem/router, change the DNS server in DHCP to the DNS servers with ECS (such as OpenDNS 208.67.222.222, Quad9 ECS 9.9.9.11 and Google DNS 8.8.8.8). Then the device's native dns will choose the correct ultralow server closest to you.

      • DJKatastrof
      • 1 mth ago
      • Reported - view

       At home, it's already working as intended.

      Someone from NextDNS crew that can guide me into the right direction here?

      • BigDargon
      • 1 mth ago
      • Reported - view

      There is no solution here, when using 4G, native dns queries the domain name dns.nextdns.io to the DNS server set by the carrier, to find the NextDNS ultralow server IP address. So it depends on which carrier you are using which DNS server.

      • DJKatastrof
      • 1 mth ago
      • Reported - view

       as I pointed out, having the same carrier for 5 years and using NextDNS for 2-3 years. These issues started happening recently. 
       

      can’t be a coincidence when some other people from other countries have the same symptoms?

      • R_P_M
      • 1 mth ago
      • Reported - view

      It can and is a coincidence, they may seem the same to you but most of the time there are clear differences.

      For your case in question, this could simply be down to changes by your carrier (sometimes its new IP blocks being reused from other locations around the world & location services not catching up with the change).

      • DJKatastrof
      • 1 mth ago
      • Reported - view

       I then have no other option than to move on to another service. Been a good ride with NextDNS. 

      • R_P_M
      • 1 mth ago
      • Reported - view

      No other option? You haven’t even tried running the diag yet or at least run some simple tests like visiting https://ping.nextdns.io

      The images you provided don’t say much about any routing issues, only the perceived endpoint. 

    • Gourab
    • 1 mth ago
    • Reported - view

    I would better check the ecs with dnscheck.tools instead of the server location

     

    cause if the ecs location is same as yours then you contents will be server quickly

Login to reply

Content aside

  • 1 mth agoLast active
  • 9Replies
  • 135Views
  • 4 Following