2 ms·

> BTW, if you run your own local DNS resolver Can you share some more information on this? I've been thinking of doing so with my OpenBSD server, but my DNS kn

> BTW, if you run your own local DNS resolver Can you share some more information on this? I've been thinking of doing so with my OpenBSD server, but my DNS knowledge is limited to the client side.

formerly_proven 2y ago
knot-resolver
- 77pt77 2y ago
  Can vouch. It just works and has low resource utilization.
quesera 2y ago
Running a local resolver is very simple. If you know the steps -- install software, download root hints file, glance at default config (probably no changes needed), set packet filter rules, start daemon, update DHCP config -- you can be up and running in less than 10 minutes. If it's your first time, but all of those steps are conceptually clear, I'd allot an hour or so. I'd recommend Unbound[0] or Knot Resolver[1]. Either will give you fast local caching and private DNS history, with zero maintenance requirements. I literally have not touched my (Unbound) config in ten years. Though, now that I think about it, there have probably been root hints[2] updates that I should download. (30 sec later: Done!) 0: https://www.nlnetlabs.nl/projects/unbound/about/ https://www.nlnetlabs.nl/projects/unbound/about/ 1: https://www.knot-resolver.cz/ https://www.knot-resolver.cz/ 2: https://www.internic.net/domain/named.root https://www.internic.net/domain/named.root
- moscoe 2y ago
  I’ve also been running unbound for a few years now without issue.
nubinetwork 2y ago
Install bind, make your zone files, start it, and change your dhcp to give your computers the new DNS server address... shouldn't take longer than a half hour to set it all up. An additional bit of setup can also integrate the equivalent of pihole using rpz.
plagiat0r 2y ago
The best document to properly run a private root zone dns server is this: https://datatracker.ietf.org/doc/html/rfc8806 https://datatracker.ietf.org/doc/html/rfc8806 Just read it quickly and you're good to go.
3np 2y ago
I've tried most of the popular ones on Linux, these are the ones Ive got working all right with little enough hassle to recommend checking out: unbound knot-resolver Technitium Yadifa (I find BIND tiresome and would only recommend core-dns if you know why you want it) unbound would be my go-to. --- General advice: Keep your resolver(s) for public DNS dedicated and as isolated as reasonable. Don't point your clients directly to it or configure any custom zones on it. Instead have your existing (I assume, otherwise spin up dnsmasq) DNS servers forward and cache all your actual lookups.

> BTW, if you run your own local DNS resolver Can you share some more information on this? I've been thinking of doing so with my OpenBSD server, but my DNS knowledge is limited to the client side.

formerly_proven 2y ago

knot-resolver

77pt77 2y ago
Can vouch. It just works and has low resource utilization.

quesera 2y ago

Running a local resolver is very simple. If you know the steps -- install software, download root hints file, glance at default config (probably no changes needed), set packet filter rules, start daemon, update DHCP config -- you can be up and running in less than 10 minutes. If it's your first time, but all of those steps are conceptually clear, I'd allot an hour or so. I'd recommend Unbound[0] or Knot Resolver[1]. Either will give you fast local caching and private DNS history, with zero maintenance requirements. I literally have not touched my (Unbound) config in ten years. Though, now that I think about it, there have probably been root hints[2] updates that I should download. (30 sec later: Done!) 0: https://www.nlnetlabs.nl/projects/unbound/about/ https://www.nlnetlabs.nl/projects/unbound/about/ 1: https://www.knot-resolver.cz/ https://www.knot-resolver.cz/ 2: https://www.internic.net/domain/named.root https://www.internic.net/domain/named.root

moscoe 2y ago
I’ve also been running unbound for a few years now without issue.

nubinetwork 2y ago

Install bind, make your zone files, start it, and change your dhcp to give your computers the new DNS server address... shouldn't take longer than a half hour to set it all up. An additional bit of setup can also integrate the equivalent of pihole using rpz.

plagiat0r 2y ago

The best document to properly run a private root zone dns server is this: https://datatracker.ietf.org/doc/html/rfc8806 https://datatracker.ietf.org/doc/html/rfc8806 Just read it quickly and you're good to go.

3np 2y ago

I've tried most of the popular ones on Linux, these are the ones Ive got working all right with little enough hassle to recommend checking out: unbound knot-resolver Technitium Yadifa (I find BIND tiresome and would only recommend core-dns if you know why you want it) unbound would be my go-to. --- General advice: Keep your resolver(s) for public DNS dedicated and as isolated as reasonable. Don't point your clients directly to it or configure any custom zones on it. Instead have your existing (I assume, otherwise spin up dnsmasq) DNS servers forward and cache all your actual lookups.