0

Connection timeouts when using NextDNS

I have been using NextDNS for close to a year now on all my devices. Last night I left my laptop in sleep mode and when I woke up to day to work, I could not connect to Clockify. Brave search too was not connecting with both timing out. On the bottom right, it was just showing 'connecting to clockify...'  I updated my Arch install and rebooted it. Same thing. I use network manager to set my dns settings and these are the contents of /etc/resolve.conf:

# Generated by NetworkManager
nameserver 10.0.0.10
nameserver 45.90.28.16
nameserver 45.90.30.16

 

 

10.0.0.10 is a LAN server that resolves a domain used in my homelab. It uses Bind9 with NextDNS as upstream. Removing 10.0.0.10 only makes my domain unreachable and does not solve the problem. I tried having my domain resolve in NextDNS, but it only works on mobile and not on desktop for some reason. 

I have tested in Librewolf, Floorp, Firefox and Brave. Any configuration that points to nextdns does not work. So far it is only those two domains that seem to have an issue. I have tried DoH and that doesn't work either. Switching to other DNS providers solves my problem instantly. 

EDIT: I am seeing even more domains that are failing to connect as I keep using the system. It is becoming unusable.

3 replies

null
    • TechStud
    • yesterday
    • Reported - view

    Ahh good old network troubleshooting... For what it's worth, I'm not having any issues resolving or reaching clockify.me.

     

    Have you checked the NextDNS Logs to see if;

    • if your requests for clockify.me are being received?
      • if not received, your requests could be directed to a different resolver.
    • if clockify.me is being resolved or blocked?
      • if blocked add to your Allowlist

    Have you performed a traceroute/tracepath or any dig / nslookup commands to see if you see anything odd? 

    eg:

      • Ted.3
      • 15 hrs ago
      • Reported - view

       For some reason, it just fixed itself without any more intervention from me. I switch to a quad9 in my bind9 forwarders and called it a day. When I saw your message today I went in to do the tests you suggested, but it was working just fine. All the websites that were giving me trouble work fine. 

      • TechStud
      • 10 hrs ago
      • Reported - view

       Great to hear! Hopefully all remains well, especially through the holidays (and beyond of course). 

Content aside

  • 10 hrs agoLast active
  • 3Replies
  • 33Views
  • 2 Following