Re: Named problem

Glynn Clements (glynn@sensei.co.uk)
Tue, 27 Oct 1998 12:11:54 +0000 (GMT)


mits@jimin.com wrote:

> What could be the problem . Is is the root.cache causing problem.
> When I start debugging by nslookup , It says
>
> can't find server name 192.168.10.202 : server failed.

For a start, your named.conf is completely bogus:

> ********************************************************************************
> NAMED.CONF
>
> directory /etc/named
>
> primary localhost localhost.zone
> primary 0.0.127.in-addr.arpa localhost.rev
>
> primary india.infogain.com infogain.com.zone
> primary 4.168.192.in-addr.arpa infogain.com.rev
>
> primary 0.in-addr.arpa all-zero.zone
> primary 255.in-addr.arpa all-one.zone
> cache . root.cache
>
> forwarders 192.187.205.32 192.187.205.12

This is correct for named.boot, but you're running 8.1.1, which uses
named.conf, which has a completely different format.

Second, you don't seem to have configured reverse DNS for
192.168.10.*.

Third, have you specified the correct nameserver(s) in
/etc/resolv.conf?

-- 
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