You need to put forwarders in your named.conf file:
options {
forwarders {204.127.160.2; 204.127.129.2; };
};
Then restart bind. This will tell you lan dns server to forward any dns
requests it doesn't know to another server that would.
-----Original Message-----
From: Ahbaid Gaffoor [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 04, 2000 6:20 PM
To: redhat list
Subject: BIND Problem
Hi All,
thanks to the persons who kindly answered previous posts regarding route
configuration...
Now it' sthe next step... named
I setup BIND on my machine and I have in the following files:
a) /etc/host.conf has
order hosts,bind
multi on
b) /etc/resolv.conf has
nameserver 199.1.1.2
nameserver 204.127.160.2
nameserver 204.127.129.2
My entire LAN has machines with IP Addresses 199.1.1.x and 199.1.1.2 is
setup
as my name server...
Now, with /etc/resolv.conf configured as above, I can do an nslookup on
all machines
setup within BIND fine, but as soon as I try something on the outside
world, I get:
[root@rehanna /root]# nslookup www.compaq.com
Server: rehanna.ilmtech.com
Address: 199.1.1.2
*** rehanna.ilmtech.com can't find www.compaq.com: Server failed
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.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
