4 ms·

I use tinydns or nsd You can use unbound I do not use a cache For HTTP I use a localhost-bound TLS forward proxy that has the DNS data in memory; I gather th

I use tinydns or nsd You can use unbound I do not use a cache For HTTP I use a localhost-bound TLS forward proxy that has the DNS data in memory; I gather the DNS data in bulk from various sources using various methods; there are no remote DNS queries when I make HTTP requests Unbound is overkill for how I use DNS on the local network

throw0101c 1y ago
Unbound is a recursive-only resolver. NSD is an authoritative-only resolver. Those are different use cases.
- JdeBP 1y ago
  Psst! NSD isn't a "resolver" at all. Traditional DNS terminology is tricky to use (given that what is covered by "resolver" in the RFCs does not match how most people see the system as divided up) but something that does not do the resolving part at all is definitely not a resolver. * https://jdebp.uk/FGA/dns-server-roles.html https://jdebp.uk/FGA/dns-server-roles.html
- 1vuio0pswjnm7 1y ago
  "Unbound is a recursive-only resolver" https://raw.githubusercontent.com/NLnetLabs/unbound/master/doc/FEATURES https://raw.githubusercontent.com/NLnetLabs/unbound/master/d... https://raw.githubusercontent.com/NLnetLabs/unbound/master/doc/example.conf.in https://raw.githubusercontent.com/NLnetLabs/unbound/master/d... Unbound can also answer queries from data in a text file read into memory at startup, like an authoritative nameserver would; no recursion