DNS server

Submitted ⁨⁨13⁩ ⁨hours⁩ ago⁩ by ⁨iturnedintoanewt@lemmy.world⁩ to ⁨selfhosted@lemmy.world⁩

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!

source

Comments

Sort:hotnew top

tux0r@feddit.org ⁨8⁩ ⁨hours⁩ 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).

source
- philpo@feddit.org ⁨6⁩ ⁨hours⁩ 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.
  
  source
  - tux0r@feddit.org ⁨4⁩ ⁨hours⁩ 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.
    
    source
    -> View More Comments
Shimitar@downonthestreet.eu ⁨13⁩ ⁨hours⁩ ago
My 2c.

Changing “DNS” won’t fix it. There are two DNS: dnsmasq and inbound (and bind, ok). What else you use doesn’t matter (pihole, adguard, opnSense) at the end of the day it’s always them inside.

In my experience ISPs will block your direct DNS queries overtime, so it might be that. I set up my unbound as caching and forwarding, not as a pure resolver. This fixed all my issues with DNS self hosted. You can forward to 9.9.9.9 if you like it.

Another issue might be with your blocklists of course, your azure might have been temporary listed maybe.

Over time I ended up choosing a very lax blocklist setup due to this reason

source
- non_burglar@lemmy.world ⁨7⁩ ⁨hours⁩ ago
  
  In my experience ISPs will block your direct DNS queries overtime,
  
  I have no idea what ISP you’re using, but that’s probably not true. Lots of devices have hard-coded DNS servers and nothing would work if ISPs stated blocking dns upstream queries.
  
  source
  - Shimitar@downonthestreet.eu ⁨6⁩ ⁨hours⁩ ago
    Above some threshold, the one you will cross when filtering port 53 in your network and setup a custom full resolver, it can happen.
    
    I experienced it, it seems they filter excess dns traffic from inside. Probably more a malware/anti spam measure than an actually DNS blocking.
    
    source
Onomatopoeia@lemmy.cafe ⁨7⁩ ⁨hours⁩ ago
What’s the use-case for pihole and unbound together?

Aren’t they both DNS servers?

source
- InnerScientist@lemmy.world ⁨5⁩ ⁨hours⁩ ago
  Pi-hole forwards the requests to another DNS server. Unbound can ask the root servers and go down the DNS chain.
  
  source
Eideen@lemmy.world ⁨9⁩ ⁨hours⁩ 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?

source
nesc@lemmy.cafe ⁨13⁩ ⁨hours⁩ ago
Just normal dnsmasq without fancy web-ui.

source