Config problem with Master and Slave Servers

Kevin Darcy kcd at daimlerchrysler.com
Mon Oct 7 19:55:25 UTC 2002


Philippe.Garcet at steria.be wrote:

> Hy there,
>
> I have a very strange problem and I don't know if this is a config or
> network problem.
>
> Both servers are defined in the network config of the NT4 Workstation.
>
> In fact, I've setup a Master and a slave server, when I stop the master
> server to test the Slave to see if he's answering request, I get the
> following when running the NSLOOKUP tool:
>
> Master: 10.10.10.65
> Slave 10.10.10.66
>
> c:\>nslookup
> DNS request timed out.
>     timeout was 2 seconds.
> timeout (2 secs)
> *** Can't find server name for address 10.10.10.65: Timed out
> *** Default servers are not available
> Default Server:  UnKnown
> Address:  10.10.10.65
>
> > exit
>
> On another way if I manually set up the default server to the slave, it
> works perfect.
>
> I have defined in the named.conf two NS records pointing to both servers
> ....

NS records don't belong in named.conf.

Chances are the the 10.in-addr.arpa (or the appropriate descendant zone
thereof) is not defined properly on what you are calling the
"master" server...


- Kevin




More information about the bind-users mailing list