One of the the named.boot file I tried is like this.
;+++++++
directory /var/named
cache . named.ca
primary 0.0.127.in-addr.arpa named.local
forwarders 192.168.168.102
;+++++++
The named.ca file has nothing in it:
;+++++++
; cleared for testing
;+++++++
resolv.conf has:
;+++++++
nameserver 127.0.0.1
;+++++++
Is there any other things that I should check?
Thanks for your help.
Andy
----------
From: Glynn Clements
To: Siu, Andy
Cc: Mailing List, Linux Networking
Subject: Re: DNS: named ignores "forwarders"
Date: Wednesday, 7 October 1998 4:57PM
Siu, Andy wrote:
> Can anyone confirm if the "forwarders" statement in named.boot actually
> works?
Yes, it works.
> To test this, I used two linux box: one with Redhat 5.0 the other with
> Redhat 5.1. Both machines have been configured as name server but the 5.0
> machine has some names that are not defined in the 5.1 machine. In the
> resolv.conf file of both machine, there is only one line "nameserver
> 127.0.0.1". Individually the named in both machines appears to work ok,
eg
> can ping using name, nslookup works on either machine with either set as
> server etc.
Are the names which are missing from the 5.1 box in one of the domains
for which it is authoritative?
The `forwarders' directive won't have any effect upon these. If named
receives a query regarding a zone for which it is authoritative it
will provide a definite answer. If the name isn't in the zone file, it
will return a negative response; it won't try to forward the query
elsewhere.
--
Glynn Clements <glynn@sensei.co.uk>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu