lkml.org 
[lkml]   [1999]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: DNS error? Something wrong with TCP?
On Fri, 5 Mar 1999, Richard B. Johnson wrote:

> On Fri, 5 Mar 1999, Mike A. Harris wrote:
>
> > Mar 5 15:03:22 red named[362]: sysquery: findns error (NXDOMAIN) on red.prv?
> > Mar 5 15:03:43 red last message repeated 4 times
> >
> > Kernel 2.0.36
> >
>
> This normally means that another name-server says it is "authoritive" for
> the domain so your name-server has removed references to this name from
> its cache. It is not a TCP error (named/bind uses UDP). If the name
> that has been removed, can't be resolved, find that M$GARBAGE machine
> that claims that it is authoritive and shoot it. Otherwise ignore it.

While MS boxes are responsible for a lot of stupid things, this is most
likely the case when there was no such domain in the first place. Local
box simply has hostname red, /etc/hosts has red and red.prv, and there is
no any .prv. zone on the local nameserver or anywhere. Once some program
queries local nameserver with red.prv, it can't find a nameserver for
red.prv. because there really isn't such a thing.

--
Alex

----------------------------------------------------------------------
Excellent.. now give users the option to cut your hair you hippie!
-- Anonymous Coward


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.029 / U:0.556 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site