Tom Horsley wrote:
> Bind has 47,589,322 pages of documentation you can't search
> unless you already know all the proper jargon. The actual docs
> are the last place I ever want to look for anything :-).
Todd Zullinger:
Heh. If you're not sure of the terminology, bind is the
last thing you should be running¹. ;)
Though, to be fair, most of the time when you're researching a problem
with BIND, you'll be looking up snippets from your config files, or
error messages, so you do have codewords to search for.
I'd argue that the overwhemling majority of folks on this
list are better served by a name server other than bind.
Use dnsmasq or something else for most home-based DNS
services (and even for plenty of production-grade DNS
services).
I'd agree with that. Most people just need name resolution, they're
not actually being a public DNS server.
I use it because it and DHCPD were what I had to play with when I got
started, long ago. I figured out what I needed to do for that, which
wasn't too much of a complex requirement, and manage to work out how to
handle any changes across different releases.
I do come a cropper with a few modern gadgets that do a half-arsed job
of using DHCP and normal DNS, and seem to just want to use some bodge
of avahi/zeroconf/auto self configuration expecting it to be there,
somewhat like the UPnP nightmare of many years ago of NAT unfriendly
things. And avahi, et al, are useless to various older devices that
only handled DHCP or completely manual configuration.
--
uname -rsvp
Linux 5.11.21-100.fc32.x86_64 #1 SMP Fri May 14 18:03:50 UTC 2021 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.