On Mon, 15 Aug 2016 07:12:02 -0400
Hendrik Boom <[email protected]> wrote:

> On Mon, Aug 15, 2016 at 03:25:01AM -0700, Rick Moen wrote:
> > 
> > There shouldn't IMO be broken DNS any more on modern networked *ix 
> > hosts.  Run a local recursive resolver and list 127.0.0.1 as the
> > first resolv.conf entry.  It's 2016, guys.  
> 
> Why isn't a local resolver the default?  Why do we rely on the ISP to 
> do provide one with DHCP?

Because, even to this day, djbdns tricky to compile-install and
calibrate, and don't EVEN get me started on what distro packages do to
djbdns.

I suppose someone could suggest I go to Bind, but that someone would be
greatly overestimating my IQ: I'd need about 40 additional IQ points to
understand how to work with Bind.

But you bring up an excellent point. Life would be sweeter with an
always-working, local, caching DNS. I *could* create a package made out
of djb's source code (which almost certainly won't change anymore) and
my shellscripts to easily lay down a djbdns, fully configured. I think
there's a patch to make djbdns work with ipv6, so my version2 could do
that.

SteveT

Steve Litt
August 2016 featured book: Manager's Guide to Technical Troubleshooting
  Brand new, second edition
http://www.troubleshooters.com/mgr
_______________________________________________
Dng mailing list
[email protected]
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to