Re: DNS error? Something wrong with TCP?

Richard B. Johnson (root@chaos.analogic.com)
Fri, 5 Mar 1999 21:40:16 -0500 (EST)


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.

The "final solution" is to have only one machine that claims it's
authoritive and the others should be caching-only servers.

Cheers,
Dick Johnson
***** FILE SYSTEM WAS MODIFIED *****
Penguin : Linux version 2.2.2 on an i686 machine (400.59 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.
Bait : plutonium Cuba president assassination killed Iran Honduras
nitrate tritium toluene ammonium subway 747 pits iodine critical nuclear

-
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/