RE: [cobalt-users] NSLOOKUP Produces Non-Authoritative Answer to queries

["Dan Kriwitsky" <webhosting@xxxxxxxxx>]

> On Fri, 1 Jun 2001, Dan Kriwitsky wrote:
>
> } It does indeed indicate a problem with his DNS setup.
>
> My DNS isn't running on a Cobalt. Nothing wrong with the Cobalt way
> but I have much more control over it via the manual method and our
> DNS here is massaged much more than most. But, while I didn't do a
> lookup on the domain in quesiton, I stand by my words. I can't give
> you a link Dan, but I can refer you to the book, DNS and Bind (page
> 268 of the 3rd addition) where the reason for getting a
> non-authoritive answer is explained in great detail.
>
I don't have the book to look it up in, but my guess would be it doesn't
refer to doing a lookup on the DNS server that's supposed to be
authoritative for the domain in question.
I only get the non-authoritative answer from DNS servers, like my ISP's
server, when I first do a trace to a domain and then do a DNS lookup on my
ISP's server. It will properly give me the correct A record.

--- DNS lookup for "www.fudpucker.com", please wait...

Non-authoritative answer:
www.fudpucker.com	A	204.49.154.92

Authoritative answers can be found from:
fudpucker.com	NS	NS1.NETSMITH.NET
fudpucker.com	NS	SERVER.CNTFL.com
NS1.NETSMITH.NET	A	204.49.160.2
SERVER.CNTFL.com	A	199.44.2.10

--- DNS Lookup completed

--- DNS lookup for "www.fudpucker.com", please wait...
--- contacting nameserver: ns1.netsmith.net [204.49.160.2]

www.fudpucker.com	A	204.49.154.92

--- DNS Lookup completed

No domain name I have ever looked up on any DNS server that is authoritative
for a domain ever responds with "Non-authoritative answer". I only see that
from caching nameservers, like my ISP's that will respond that way until the
TTL expires.
Another explanation can be found at
http://www.isc.org/ml-archives/bind-users/2000/04/msg00162.html

--
Dan Kriwitsky