Ahbaid Gaffoor wrote:
> Hi All,
>
snip
> b) /etc/resolv.conf has
> nameserver 199.1.1.2
> nameserver 204.127.160.2
> nameserver 204.127.129.2
>
> snip
> Now, if I edit /etc/resolv.conf and place the outside nameserver as
> follows:
>
> nameserver 204.127.160.2
> nameserver 199.1.1.2
> nameserver 204.127.129.2
>
> the lookup works for entries on the internet, but now it fails for
> lookups on my LAN...
>
> Makes me think that there is something I have to do to tell BIND to read
> all the
> lines in /etc/resolv.conf when resolving names...
>
> My question is: Why doesn't the first configuration of /etc/resolv.conf
> allow the second nameserver to be pulled once it doesn't find it on
> 199.1.1.2? What am I missing?
>
> thanks,
>
> Ahbaid.
I believe that the additional hosts will not be contacted unless the first
one(s) are down. Not do to a failure to lookup a name. I set up my dns
through linux conf and added the additional servers as forwarders.
Basically this tells bind to use these servers to forward requests to if it
does not know about a particular host. It will slow down bad requests
since it will first fail at the local machine and then be forwarded to the
"real" server where it will fail and then back to the requesting machine as
a bad lookup. One cool thing is that the succesfull outside lookups will
be cached and then served imediately to a requeting local machine.
Hope this helps.
Bret
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
