Date: Sun, 25 Jan 2004 19:43:45 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Matthew Fremont <m_fremont@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: nslookup and reverse lookup failure of nameserver under 5.2-RELEASE Message-ID: <20040125194345.GC12995@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <20040125191306.98522.qmail@web20025.mail.yahoo.com> References: <20040125191306.98522.qmail@web20025.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Fig2xvG2VGoz8o/s
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Jan 25, 2004 at 11:13:06AM -0800, Matthew Fremont wrote:
> The nameserver is working properly, and commands like
> dig(1), host(1), telnet(1), and ftp(1), are able to
> sucessfully resolve names. The problem appears to be
> isolated to nslookup(8).
>=20
> If memory serves me correctly, at some time in the
> past nslookup handled a reverse lookup failure of the
> server more gracefully, identifying the server as
> "Unknown", and continuing with the query.
As I recall, this quirk of nslookup(8) was one of the reasons why the
BIND project has deprecated it in favour of the better behaved tools
like dig(1) and host(1). If you used a version of nslookup(8) that
didn't have this problem, then it must have been specially patched to
do so.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--Fig2xvG2VGoz8o/s
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFAFBxxdtESqEQa7a0RAmX5AJ9fBW5OQUPaXTdzy4H6Oh3H8THbAwCeNxsI
Es6XMi11xAmA3t8YVgayu6A=
=VC3v
-----END PGP SIGNATURE-----
--Fig2xvG2VGoz8o/s--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040125194345.GC12995>