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

["Dan Kriwitsky" <webhosting@xxxxxxxxx>]

> There's absolutely nothing to worry about here. This is the way DNS
> works. Basically the first time you look up a name the server is
> authoritative. The second time you look up a name it is not. The
> reason is simple. The first lookup is just that - a lookup - the
> information is passed to nslookup and it is also Cached by the local
> name server. The second time you look it up the answer is pulled
> from the Cache which results in the nonauthoritative answer.
>
> 	It makes sense if you think about it. How can a cache be
> authoritative? In other words, is it real (name server - authoritative),
> or is it Memorex (cache - nonauthoritative)?
>

If you look up a domain in the server that's supposed to be authoritative,
e.g.:
--- DNS lookup for "fuddpucker.com", please wait...
--- contacting nameserver: maven.webokay.com [209.94.85.163]

fuddpucker.com	A	209.94.85.172
fuddpucker.com	NS	maven.webokay.com
fuddpucker.com	NS	macher.webokay.com
fuddpucker.com	NS	ns1.everquick.net
fuddpucker.com	SOA
etc.

you'll notice, that unlike ns1.hardynet.com, your DNS does not reply
"Non-authoritative answer" for a domain that is hosted there.
--- DNS lookup for "hardynet.net", please wait...
--- contacting nameserver: ns1.hardynet.net [63.67.240.146]

Non-authoritative answer:
hardynet.net	SOA
    origin = www.hardynet.net
etc.

Your DNS properly replies for any of the domains hosted there:
--- DNS lookup for "lexingtons.com", please wait...

lexingtons.com	A	195.170.235.200
--- DNS lookup for "gpdd.org", please wait...

gpdd.org	A	209.94.85.171

At no time, no matter how many times the DNS server is queried, will it
reply "Non-authoritative".

It does indeed indicate a problem with his DNS setup.
--
Dan Kriwitsky