nslookup fails on secondary DNS

[Mathias Körber]

That error is from nslookup. It tried to reverse resolve
the nameserver it is to query (from /etc/resolv.conf if you don't
specify another on the commandline or per 'server' command) and
cannot find the entry.

If your resolv.conf points to your own nameserver (212.76.68.201 ?)
it means that that nameserver is not authoritative for its
own reverse entry, but also cannot return a referral for=20
it. Most likely it is set up to be authoritative for the
reverse domain 68.76.212.in-addr.arpa (or a subdomain of that
if you own an IP block with a prefix > 24, see RFC2317),
but that the PTR record for your secondary NS has not been configures
properly.


> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
> Behalf Of muheeb
> Sent: Sunday, July 30, 2000 2:26 PM
> To: bind
> Subject: nslookup fails on secondary DNS
>=20
>=20
> Hello All,
>=20
> I am running BIND 4.X on Windows NT 4.0
>=20
> Everything is running fine with the primary DNS Server,
>=20
> However, when I checked the secondary DNS and tried to use the=20
> 'nslookup' utility it gave me the following,
>=20
> C:\>nslookup
> *** Can't find server name for address 212.76.68.201: Server failed
> *** Default servers are not available
> Default Server:  UnKnown
> Address:  212.76.68.201
>=20
> when I do the same on my primary server it gives no errors and=20
> nothing. The secondary DNS is getting the zone list from the=20
> primary DNS with no problem.=20
>=20
> Any ideas why this is happening????
>=20
> Muheeb
>=20