nslookup fails after a time

Barry Margolin barmar at genuity.net
Tue Jan 23 19:41:28 UTC 2001


In article <94klig$3te at pub3.rc.vix.com>,
Veatch, David <David.Veatch at eScout.com> wrote:
>Greetings all, brand new to the list... hope you don't mind a relative
>newbie question.  I don't mind an RTFM (in fact, I have a coffee mug with
>those letters on them ;), as long as you give me some direction as to the
>which and where of the RTFM... O'Reilly's book is assumed. :)
>
>On to the question.
>
>I'm confused by an odd, yet frequent occurrence on a FreeBSD box of mine.
>After an undetermined amount of time, and for an undetermined reason, a
>certain domain ceases to resolve.   Once I restart named (`ndc restart`),
>the domain resolves again just fine, but after awhile, invariably, it fails
>to resolve with "*** localhost can't find [domain-name]: Non-existent
>host/domain".  There could very well be other unresolvable names at this
>time, but this is the only one I've identified.

Often this is due to problems with NS records for the domain.  If you said
what domain it is, maybe we could tell what's wrong.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.



More information about the bind-users mailing list