0

Timeout and Server failed resolving one domain name with some of NextDNS servers

Domain name inform.pucp.edu.pe

Mikrotik generally resolves this name, sometimes after several attempts.

Windows and Android NextDNS clients don't resolve.
I tested Windows client with nslookup, it either fails with timeout or gives "Server failed". Increasing timeout to 10 seconds doesn't help.

Maybe because the clients use different addresses for dns.nextdns.io?
Mikrotik is configured according to my setup page and so has static DNS records for dns.nextdns.io with addresses 45.90.*.
I don't know which addresses Windows and Android clients use. But Google's DNS (and NextDNS itself) resolve dns.nextdns.io to different addresses: 32.252.*.

So, looks like the problem exists on one NextDNS server but not on the other.

16replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • The domain works fine on me. The only problem is that it only has http not https and some browsers give warnings and some might not working depending on settings.

    Like
    • losnad What client do you use for NextDNS? And what NextDNS server does this client use?

      Like
  • I use DoH, DoT and DoQ with AdGuard on Android and secure DNS (DoH) in Brave and Opera. But it doesn't matter, I tried with Tor and with VPN on Opera. Works all the time.

    Like
    • losnad As I pointed out in my report, the issue happens using one NextDNS server but not the other. So, it really does matter. Unless you say specifically what NextDNS servers your clients use, or, at least, which address dns.nextdns.io is resolved to, your comments don't add anything new to my issue report.
      Tor doesn't use NextDNS, and I don't have a problem in Tor too.

      Actually, I hoped for an answer from NextDNS's support. But looks that it's the wrong place to ask for support..

      Like
      • R P M
      • R_P_M
      • 2 wk ago
      • Reported - view

      Basil Peace What is the full IP address of the failing NextDNS server? Without knowing this no one can check, as different locations will have two different dns servers and it will be “pot luck” to find the problematic one. 

      Like
    • R P M failing: 37.252.255.23 and .39
      working: 45.90.28.224 and .30.224

      BTW, is there a specific reason why the setup page says to use one address on a router while NextDNS client uses another one?
      Are IP addresses tied to specific configurations? Or I can use whatever I can/want?
      I suspect that 37.252.255.0/24 is split DNS for my location, so I'd better use it for my router too (if it'd worked).
      Or should I add 45.90.28.224 dns.nextdns.io to my hosts file since this is the address mentioned in setup? Documentation doesn't say this is necessary.

      Like
      • R P M
      • R_P_M
      • 2 wk ago
      • Reported - view

      Basil Peace 45.90.* IPs are as @Dmytro said Anycast addresses.

      37.252.255.23 & .39 appear to be offline and not accepting any dns requests. IPs are owned by Anexia who are a peering partner of NextDNS. 

      Can you try ping.nextdns.io on the problem devices and post back the results here.

      Like
      • Emanuel
      • Emanuel
      • 2 wk ago
      • Reported - view

      R P M Hey, as an aside, how do you know that those IPs are Anexia and more importantly how can I find which IPs those hosts from ping.nextdns.io have because edis-bud is lowest latency and maybe I would want to try it?

       

        edis-bud        8 ms  (ultralow2)

       anexia-vie     15 ms  (anycast2)

        exoscale-vie   16 ms

        enahost-bts    16 ms

        anexia-beg     21 ms

        anexia-bts     22 ms

        zepto-prg      23 ms  (anycast1)

        edis-zag       24 ms

        edis-beg       27 ms

        anexia-buh     30 ms

        anexia-bud     30 ms  (ultralow1)

       

      EDIT: on second thought, maybe I'm misinterpreting the results, it seems to be a traceroute instead! So my question doesn't make sense now, whoops :)

      Also

      https://dns.nextdns.io/info

      shows:

      locationName "🇭🇺 Budapest, Hungary"
      pop "edis-bud"
      rtt 7619

      PoP=? point of P... ?

      Like
      • R P M
      • R_P_M
      • 2 wk ago
      • 1
      • Reported - view

      Emanuel A simple WHOIS lookup of the IP addresses shows up as anexia. 

      ping.nextdns.io is not a traceroute, the ping times are just ordered lowest to highest.

      To switch to edis-bud, how have you setup to use NextDNS?

      PoP? Point of Presence would be my guess. 

      Like 1
      • Emanuel
      • Emanuel
      • 2 wk ago
      • Reported - view

      R P M I've set it up using the info provided on my.nextdns.io/$MYID/setup :

      Linked IP

      If you are unable to set up NextDNS using our apps, DNS-over-TLS, DNS-over-HTTPS or IPv6, then use the DNS servers below and link your IP. This is mostly for use on home networks and not recommended on mobile.

       

      DNS Servers

      45.90.28.230

      45.90.30.230

       

      I use Automate app to make the linked ip update via https request when wifi turns on.

       

      That "edis-bud" from the pop above confused me, it makes sense the ping result is not a traceroute and they're sorted, thanks!

      Maybe these are the hostnames for the ping info ? via uMatrix addon:

      yup I'm getting 9ms ping on edis-bud:

      194.71.130.182 ipv4-edis-bud-1.edge.nextdns.io

      Like
      • Emanuel
      • Emanuel
      • 2 wk ago
      • Reported - view

      can't edit post anymore, but wanted to add this has the same IP as edis-bud (edge) above:

      194.71.130.182 ipv4.dns2.nextdns.io
       

      So maybe it makes sense to use it, instead of the ones they give in setup?:

      45.90.28.230

      45.90.30.230

       

      217.146.4.63 ipv4.dns1.nextdns.io
       

      Like
    • R P M Problem device, Windows client:
       

      ■ anexia-led     16 ms  (ultralow1)

        hetzner-hel    19 ms

        zepto-mow      25 ms

        anexia-mow     26 ms  (ultralow2)

        anexia-sto     29 ms  (anycast2)

        wavecom-tll    34 ms

        tavu-hel       35 ms

        zepto-fra      44 ms  (anycast1)

        melbicom-rix   49 ms

        edis-rix       50 ms

        edis-vno       74 ms

        melbicom-vno   83 ms



      Android works now, with ■ zepto-fra. Previously either Android used a different server, or I was too impatient.
      PC behind router works. Ping either prints ■ before zepto-mow, or doesn't print ■ at all.

      P.S. Version of Windows client is the latest 2.2.1.

      Like
      • R P M
      • R_P_M
      • 2 wk ago
      • 1
      • Reported - view

      Emanuel Using the IP address setup you are limited to the Anycast servers. It’s not a good idea to set it to the IP address of dns2.nextdns.io because if the server has maintenance or offline for whatever reason, you could end up with no connection to the internet.

      If you can use the NextDNS apps on your devices or other DoH/DoT clients then you would be able to use that edis-bud automatically. 

      Like 1
      • R P M
      • R_P_M
      • 2 wk ago
      • Reported - view

      Basil Peace When you get no box for any on ping.nextdns.io are there any marked in bold?

      Like
    • R P M zepto-mow and vultr-ams are bold. My router is multi-WAN, and I have two ISPs, so I don't think missing box is a problem. I have some simple balancing+reserving algorithm in there, but it could be incompatible with ping.nextdns.io.

      Anyway, this setup (generally) doesn't have the problem resolving inform.pucp.edu.pe. Which this issue is about.

      The problematic device is the one using anexia-led.

       

      > 37.252.255.23 & .39 appear to be offline and not accepting any dns requests. IPs are owned by Anexia who are a peering partner of NextDNS

      Maybe it's behind a firewall and doesn't accept requests from your location? Considering current situation.

       

      > If you can use the NextDNS apps on your devices or other DoH/DoT clients then you would be able to use that edis-bud automatically

      I already use the NextDNS app, but either it chooses the wrong server, or there is a problem with that specific server.

      Like
  • 45.90.28.225

    45.90.30.225 is not working nor the ipv6 ip on the router, it's not working since July 23, 3pm.

    Like
Like Follow
  • 11 days agoLast active
  • 16Replies
  • 108Views
  • 5 Following