On Sat, 5 Dec 1998, Michael Wirz wrote:
> It seems to me that setting up a local nameserver shouldn�t be as
> difficult as it appeared to me???
It's not too bad, but even the HOWTO had a lot of complexity for dealing
with situations well beyond what is needed for a simple local, private net
with a diald/masqueraded connection. And of course the details are
annoyingly detail-ish.
> How do you instruct named to respond to other than local name request
> by forcing diald to connect and look up my ISPs Nameserver?
You want two lines in the config file (often /var/named/named.boot):
options forward-only
forwarders xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy
With your ISP's nameservers's addresses on the last line. Then you can
jettison the root nameserver hints; bind will answer all requests that it
knows already at once, and try to contact your ISP's nameservers for
anything it doesn't know.
The caching can interact with dynamic IPs to make difficulties; I hear
that this is all working much more easily with recent kernels that provide
the ip_dynaddr settings (recently discussed), but beyond that I don't
really know much about this. Yet. I expect I'll be moving to a dynamic
IP environment before the end of the month, and I'm not looking forward to
the learning experience I expect it to be. ;-( :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
