Hi guys! So…I have a self-hosted DNS server. Initially I’d use pihole, with unbound, and the more or less basic blocklists. But from time to time things would start acting wonky. Sometimes a reboot would fix it. Sometimes…not really and I was really not sure what was going wrong, but it was clearly DNS. Changing the clients settings from my own server to something like 9.9.9.9 would immediately get it sorted out.

So I went with an adguard server. In the last few days I’ve started to notice weird behaviors. Today I’ve lost the Azure desktop I was connected, and it was very clearly looking like DNS. So I checked…and yup, 9.9.9.9 again would sort it all out. So…I’m not sure what’s going wrong. I’m selfhosting these on an LXC container in proxmox. Nothing else seems to have issues connecting, and I see almost no resources being used. Any ideas? Any other DNS server I might be able to try?

Thanks!

  • Eideen@lemmy.worldEnglish
    2·
    1 month ago

    I use pihole with DNS over https (my ISP intercepts my non encrypted DNS queries) works great for me. Both in LXC and Raspberry pi.

    What issue are you trying to solve?

  • rhabarba@feddit.orgEnglish
    31·
    1 month ago

    Any other DNS server I might be able to try?

    I use and warmly recommend Technitium DNS. Unlike most other solutions, it uses the root servers by default while still providing an ad blocker, DoH, DoQ etc. - and it does not even require any command-line kung-fu for that (except for the installation, which is one command).

    • philpo@feddit.orgEnglish
      2·
      1 month ago

      I absolutely second Technitium as well. That thing is rock solid, can be used for basically everything, has blocking with a multitude of options and does provide a nice graphical GUI.

      I have it running in a dual DNS setup (main server+a Zimablade nowadays) and that shit just works - it’s the container that has caused the least amount of problems in the last 3 years.

      The API is fairly handy and quite easy - I have it integrated into HomeAssistant so I have a “Disable DNS Blocking” button in my “Network control” tab in the app.

      The only downside is the fact that initially it can be quite overwhelming, especially if you are not an DNS guru and just did the step from AdGuard/PiHole - but soon you realise that you actually only need a few fields for basic operations.

      • rhabarba@feddit.orgEnglish
        31·
        1 month ago

        The only downside is the fact that initially it can be quite overwhelming

        On the other hand, Technitium comes with a fairly useful configuration straight out of the box. If you only want to use it on your home LAN (and therefore don’t necessarily need SSL), the only thing you really need to change is the block list field.

        • philpo@feddit.orgEnglish
          2·
          1 month ago

          Yeah, absolutely - nevertheless it can inspire that reaction - which is a shame, because it’s indeed fairly easy.

          • Jakeroxs@sh.itjust.worksEnglish
            2·
            1 month ago

            I definitely bounced off of it as it had so much configuration I had no idea where to start. Adguard home was so much easier to set up, particularly because I also had to use it via DHCP as my router doesn’t have a dns option.

  • justme@lemmy.dbzer0.comEnglish
    2·
    1 month ago

    When I set up opnsense with unbound I switched on detailed logs, just for checking what’s going on and if course I forgot to turn it off, which resulted in horrible overall performance, in particular when the drive filled up and everything broke.

  • MehBlah@lemmy.worldEnglish
    1·
    1 month ago

    I use pfsense as my router os and run pfblockerng for my filter. Anytime I have some problem I can log in to the router and look at what is being blocked and if necessary whitelist the entry that is being blocked.

    I also redirect all dns to my router at the firewall and block dns over https. This means that all dns no matter the settings on the client machine are redirected to the router. Its not fool proof but so far so good.

  • Australis13@fedia.io
    1·
    1 month ago

    I use Pi-hole, except that I originally retrofitted after setting up DNScrypt years ago to connect to Cisco OpenDNS. That’s not the only DNS server you can use with it, though, and it’s added more features since.

    To use DNScrypt with Pi-hole on the same device, set DNScrypt to listen on 127.0.0.1:54 and point Pi-hole to that as the DNS server.

    The only time I have ever had any trouble with this setup and DNS resolution is when the network is recovering from a power outage; there’s a race condition somewhere between the Pi and my modem/router that I’ve never found the time to pin down (given outages are so infrequent I just haven’t gotten around to it) and it’s easily resolved by rebooting the Pi.