"James K. Lowden" <jklowden@schemamania.org> writes:

> http://www.mclink.it/personal/MG2508/nbsdeng/chap-dns.html#SECT-DNSCACHE
> 
> Federico's Guide explains setting up a caching name server in 263 words. 
> What could be easier?  You just have add the ability to turn recursion on
> and off, which looks from here like a little script to mv the right file
> into place and send a HUP.  

Does "recursion" mean e.g. that resolving ftp.de.netbsd.org implies
asking the root name server and the name servers for .org, ,
.netbsd.org and .de.netbsd.org in that order? Indeed I'd rather let
forward to my ISP's DNS server(s) when I'm online, because they may
have cached the DNS entry already.

Seems that I need different versions of named.conf. One for beeing
offline, and the other ones (one per ISP) with the suitable forwarder
option for beeing online.

> That sure *seems* simpler than the other options you listed, but maybe I'm
> missing something?  

Ack, it's quite simple. It's just that if there were ready to use
NetBSD packages for dnrd or pdnsd, it could be *more* simple. And the
latter ones have a much smaller footprint than bind (I think named is
bind, isn't it?). I always try to get a smaller thing for my old,
single PC at home, e.g. rather leafnode than inn.

In addition ipppd from isdn4linux offers an option ms-get-dns which
implements the client side of RFC1877, i.e. let accept my ISP's
suggestion of dns address.
  Is there something comparable in i4b?
Then I could dynamically generate my forwarder option for named.conf.

Thanks
  Thomas

-- 
+-----+ Thomas Hafner +-----+
| hafn@      / hafner@      |
|   gmx.net /    sdf-eu.org |
+ http://hafner.sdf-eu.org/ +