1

Fetch error: Get "https://test.nextdns.io" / "https://dns.nextdns.io/info" / lookup ipv4.dns1.nextdns.io / lookup ipv4.dns1.nextdns.io

I have NextDNS setup using stubby and DOT on an OpenWRT router. Since I can't pick what servers I get assigned, I am always stuck on the same two, Chicago and Atlanta (vultr-chi and anexia-atl). I am constantly having to switch from NextDNS to Cloudflare to get stability as when I have my system running NextDNS,  either after some minutes, hours, or a day or two, DNS resolution stops working.

What I notice is normally when an issue occurs my system switches from Chicago to Atlanta and starts working again (since I use round robin set to 0).

 

I have been using Cloudflare for the past few months with 0 issues, really 0 issues. Now, within the past 2 days, same setup, same config, only changing the named servers in stubby.yaml and restarting stubby, NextDNS has failed me 3 x times over the past 2 days. I REALLY REALLY want to use NextDNS for the adblocking and access to my personal dashboard, but it's just not stable. I wish I could try different servers OTHER than the Chicago server. Is there anything I can do?

15 replies

null
    • NextDNs
    • 3 yrs ago
    • Reported - view

    Please try: 

    round_robin_upstreams: 1

    .

      • Hans_Geiblinger
      • 3 yrs ago
      • Reported - view

      NextDNS thanks for the suggestion, however I have been playing with either having round robin 1 (as suggested) or 0 to see if it makes any difference. This would be a red herring as the issue happens in either scenario.

    • NextDNs
    • 3 yrs ago
    • Reported - view

    Can you please try https://nextdns.io/cli to see if you reproduce the issue?

      • Hans_Geiblinger
      • 3 yrs ago
      • Reported - view

      NextDNS Are you asking basically that I convert from DoT to DoH? Doing this would be a rather large change on my side as I use dnsmasq + stubby setup locally. This would require a complete reimplementation of my DNS setup. As well, at least in the past I have found the installer (NextDNS script) to not really do the full setup/config and needed a lot of hand holding after install.

      Do you have any Docu on converting to this install script for users who are already in a customized env?

      • NextDNs
      • 3 yrs ago
      • Reported - view

      Hans Geiblinger the cli is a very simple service that does the job of both dnsmasq and stubby. The install script will only detect the platform and chose the best way to install the single static binary. You can check the repository wiki for your platform to find how to do it manually if you prefer. The install script will then execute `nextdns install` which installs an init script to start the daemon by detecting the init system of the platform. If you do not use the `setup-router=yes` directive (off by default), it will do nothing else, so it is on you to make sure no other daemon is listening on the port 53. Make sure you use `listen=:53` in the config to listen publicly.

      • Hans_Geiblinger
      • 3 yrs ago
      • Reported - view

      NextDNS If I compile my own OpenWRT images, is this the equivalent of including the GO binary "NextDNS" within my build?

       

      https://github.com/openwrt/luci/tree/openwrt-21.02/applications/luci-app-nextdns

      • NextDNs
      • 3 yrs ago
      • Reported - view

      Hans Geiblinger yes

      • Hans_Geiblinger
      • 3 yrs ago
      • Reported - view

      NextDNS DNSMASQ by default uses 53, how do we run nextdns on a port different than one that is already in use?

      • NextDNs
      • 3 yrs ago
      • Reported - view

      Hans Geiblinger on openwrt, the package will do it for you.

      • Hans_Geiblinger
      • 3 yrs ago
      • Reported - view

      NextDNS As I mentioned before, and have seen in the past, hence staying away from the installer, it is NOT doing it for me :-) What would you like to see?

      • NextDNs
      • 3 yrs ago
      • Reported - view

      Hans Geiblinger the installer will just detect the platform and install the openwrt package. Feel free to use the package directly, it will be the same. On openwrt, setup-router is on by default, which will take care of disabling dnsmasq. If you want to do it manually, you can set setup-router to false in the nextdns configuration and change the listing port of dnsmasq.

      • Hans_Geiblinger
      • 3 yrs ago
      • Reported - view

      NextDNS why are we disabling dnsmasq, what is the substitute for DNS/DHCP then? I feel we are venturing more and more away from just figuring out the issue with DoT, rather than reimplementing my setup with DoH using this installer. What do you think? We are taking 1 problem and now making it 3 or 4.

      • NextDNs
      • 3 yrs ago
      • Reported - view

      Hans Geiblinger it does not disable dnsmasq, it just disable the DNS part and keep DHCP as DNS is handled by CLI.

      • Hans_Geiblinger
      • 3 yrs ago
      • Reported - view

      NextDNS Well, I am not sure what to tell you other than it doesn't work, so I am no further along than when we first started. Installing through GUI doesn't end it a working config, uninstalling and reinstalling through CLI method also doesn't work.

    • Hans_Geiblinger
    • 3 yrs ago
    • Reported - view

    Switching back to pihole, thanks.

Login to reply

Content aside

  • 1 Likes
  • 3 yrs agoLast active
  • 15Replies
  • 246Views
  • 2 Following