<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
The below cache info is old. There is definitely lame server problems:
<br>
<blockquote TYPE=CITE>
<pre>519 wwinzer@Sun-E3000:~ ==> ew_host -Z -a -l adaptec.com.
adaptec.com AXFR record query refused by AUTH00.NS.UU.NET
adaptec.com SOA record currently not present at AUTH00.NS.UU.NET
adaptec.com has lame delegation to AUTH00.NS.UU.NET
adaptec.com AXFR record query refused by AUTH61.NS.UU.NET
adaptec.com SOA record currently not present at AUTH61.NS.UU.NET
adaptec.com has lame delegation to AUTH61.NS.UU.NET
No nameservers for adaptec.com responded
Within the whois db it shows:
Domain servers in listed order:
AUTH00.NS.UU.NET 198.6.1.65
AUTH61.NS.UU.NET 198.6.1.182
It looks no SOA record exists on both nameservers @ UU.NET:
Jul 5 00:00:24 Sun-E3000 named[10874]: Lame server on 'www.adaptec.com' (in
'ADAPTEC.com'?): [198.6.1.182].53 'AUTH61.NS.UU.NET'
Jul 5 00:00:24 Sun-E3000 named[10874]: Lame server on 'www.adaptec.com' (in
'ADAPTEC.com'?): [198.6.1.65].53 'AUTH00.NS.UU.NET'
What has developed is every A RR is 100% lame:
Jul 5 00:02:24 Sun-E3000 named[10874]: XX+/207.21.123.4/www.adaptec.com/A
Jul 5 00:02:24 Sun-E3000 named[10874]: ns_forw: query(www.adaptec.com) All
possible A RR's lame
I even tried ftp.adaptec.com:
Jul 5 00:10:50 Sun-E3000 named[10874]: Lame server on 'ftp.adaptec.com' (in
'ADAPTEC.com'?): [198.6.1.182].53 'AUTH61.NS.UU.NET'
Jul 5 00:10:50 Sun-E3000 named[10874]: Lame server on 'ftp.adaptec.com' (in
'ADAPTEC.com'?): [198.6.1.65].53 'AUTH00.NS.UU.NET'
You'll need to contact UU.NET and get your zones transferred and updated ASAP.
</pre>
</blockquote>
The above is from an excerpt I sent to the Technical Advisor
<br>for Adaptec, who's a former co-worker. He'll need to contact
UU.NET
<br>to straighten out his DNS woes.
<p>- Wally Winzer Jr.
<p>Michael Voight wrote:
<blockquote TYPE=CITE>I get different NS records for adaptec.com.
<p>Non-authoritative answer:
<br>adaptec.com nameserver = auth60.ns.uu.net
<br>adaptec.com nameserver = auth02.ns.uu.net
<br>
<p>Authoritative answers can be found from:
<br>auth60.ns.uu.net internet
address = 198.6.1.181
<br>auth02.ns.uu.net internet
address = 198.6.1.82
<p>For SOA, I get:
<p>Non-authoritative answer:
<br>adaptec.com
<br> origin = auth02.ns.uu.net
<br> mail addr = hostmaster.uu.net
<br> serial = 1999031506
<br> refresh = 21600 (6 hours)
<br> retry = 3600
(1 hour)
<br> expire = 1728000 (20
days)
<br> minimum ttl = 1800 (30 mins)
<p>You might want to do the same and check what you get.
<br>It looks like you might be getting old info.
<p>You might want to clear the cache on your nameserver and/or forwarder,
<br>if you have one. Usually this is done by restarting named.
<p>Michael Voight
<br>Cisco TAC
<p>Charles Wilkins wrote:
<br>>
<br>> Hi,
<br>>
<br>> We are running bind-8.2 as our primary nameserver.
<br>> I just noticed yesterday that we can' lookup www.adaptec.com or
<br>> ftp.adaptec.com.
<br>>
<br>> This wasn't always the case, but I can't say for sure when this
<br>> happened.
<br>>
<br>> After running a few checks i was able to confirm that www.adaptec.com
<br>> is up, and other domain nameservers can resolve this host.
<br>>
<br>> Why can't we?
<br>>
<br>> My domain is pcscs.com.
<br>> The primary authoritative nameserver for our domain is ns2.pcscs.com.
<br>>
<br>> After trying to perform a lookup on adaptec.com I get these entries
in
<br>> the messages log:
<br>>
<br>> Lame server on 'www.adaptec.com' ( 'ADAPTEC.com' ?): [198.6.1.182].53
<br>> 'AUTH61.NS.UU.NET'
<br>> Lame server on 'www.adaptec.com' ( 'ADAPTEC.com' ?): [198.6.1.65].53
<br>> 'AUTH00.NS.UU.NET'
<br>>
<br>> It would appear that the nameservers for adaptec.com are these two
<br>> listed above.
<br>>
<br>> If I do a dig @ns2.pcscs.com any adaptec.com, I can see the
<br>> nameservers.
<br>>
<br>> If I do a nslookup www.adaptec.com ns2.pcscs.com I get:
<br>> NS2.pcscs.com can't find www.adaptec.com: Non-existent host/domain
<br>>
<br>> Other nameservers can do the lookup:
<br>> If i do a nslookup www.adaptec.com ns1.home.com the proper addresses
<br>> are printed.
<br>>
<br>> We don't seem to be having any other lookup problems that I can tell.
<br>> Other hosts resolve fine.
<br>>
<br>> Any ideas anybody?
<br>>
<br>> Charles Wilkins CNE / MCP / A+
<br>> Network Design Consultant
<br>> Practical Computer Solutions
<br>> <a href="http://www.pcscs.com">http://www.pcscs.com</a>
<br>> 609-321-1530
<br>> 609-321-0840 - fax
<br>> --</blockquote>
</html>