It's not. The command goes in /etc/named.boot (assuming you're using bind
version 3 and the default directories, and it's the "forwarders" line.
Here's mine, which works:
;
; a caching only nameserver config
;
directory /var/named
cache . named.ca
primary 7cedars.com named.hosts
primary 0.0.127.in-addr.arpa named.local
primary 168.192.in-addr.arpa named.rev
forwarders 204.255.24.254 137.39.1.3
options query-log
The "forwarders" line should contain the nameservers your ISP supplied.
The "query-log" option is nice because every lookup gets logged to syslog.
I use it to keep an eye on what web sites my kids are hitting and to track
the odd "phantom" phone call, which is usually caused by some product I'm
fiddling with trying to connect to someone behind the scenes.
If you're on the new bind (v8), it's named.conf and the syntax is different,
but not too hard to figure out.
You also need to make sure your diald setup allows dialing for DNS lookups.
That's covered by these two lines in standard.filter, which must not be
commented-out:
accept udp 30 udp.dest=udp.domain
accept udp 30 udp.source=udp.domain
One caveat: If your local nameserver doesn't get a hit in its' cache, it
will always dial even if the host name is not fully qualified (meaning it's
supposed to be local).
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Michael Wirz
Sent: Saturday, December 05, 1998 12:47 PM
To: [EMAIL PROTECTED]
Subject: RE: Diald and the Ghostly phantom phone-call
Hello!
It seems to me that setting up a local nameserver shouldn�t be as
difficult as it appeared to me???
How do you instruct named to respond to other than local name request
by forcing diald to connect and look up my ISPs Nameserver?
Thank you very much for your help.
Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
