RE: BIND Problem

2000-07-05 Thread Jeff Graves
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:

Re: BIND Problem

2000-07-04 Thread Darryl Harvey
You need to add an entry in /etc/named.conf to tell your name server where to get info if it can't find it. forwarders { 204.127.160.2; 204.127.129.2; }; This should fix the problem. nslookup only loads one nameserver when you invoke it; IE; [root@rehanna /root]# nslookup www.compaq

Re: BIND Problem

2000-07-04 Thread Bret Hughes
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 > nameserv

Re: bind problem

2000-04-19 Thread Rick Warner
Yes, a non-privileged user should be created and used to to run named. RH6.2 does, but default on new installs, create a user called 'named' and runs the named process as that user. There have been some well-documented buffer overflow problems in named. Exploits to these are automated and s

Re: bind problem

2000-04-18 Thread Brad Cramer
in the script /etc/rc.d/init.d/named it calls for named to start as: named -u named I am not sure how it worked in 6.1 but you might try changing the script or adding a user named. I think I did not have a problem because i did a clean install Hope that helps Brad -Original Message- From: