[SunHELP] Bind 9.2.3
vipul.bhadra at techpacindia.com
Tue May 25 10:14:38 CDT 2004
HI Lara ,
Sorry if the suggestion is offending ... but try the Linux Howto on DNS... I
always fall back on this howto's. Maybe it will help.
For ur problem .. iam out of suggestions.
Thanks & Regards ,
From: sunhelp-bounces at sunhelp.org [mailto:sunhelp-bounces at sunhelp.org]On
Behalf Of Lara Matthews
Sent: Tuesday, May 25, 2004 8:35 PM
To: The SunHELP List
Subject: Re: [SunHELP] Bind 9.2.3
George Munk wrote:
> I'm not sure if it is considered a bug or a limitation, but nslookup
> tries a reverse name resolution on the name server (22.214.171.124 in
> your case) before trying to resolve the name being queried. If the
> reverse lookup on the name server fails, it doesn't continue.
> In my experience, dig doesn't append any domains from the "domain" or
> "search" directives in resolv.conf. But I don't know that I have ever
> seen any direct statements that this is the correct behavior. So dig is
> not equivalent to the nslookup command. In newer bind versions, "host"
> is the equivalent of nslookup without the reverse lookup limitation.
Thanks for the info about nslookup, everything seems to be pointing to a
messed up reverse name resolution, now if I could Just figure out what I
have typed wrongly :)
[demime 1.01d removed an attachment of type application/x-pkcs7-signature
which had a name of smime.p7s]
SunHELP maillist - SunHELP at sunhelp.org
More information about the SunHELP