unable to resolve hosts at adaptec.com with our nameserver

Auteria Wally Winzer Jr. wally.winzer at ChampUSA.COM
Mon Jul 5 07:18:23 UTC 1999


The below cache info is old.  There is definitely lame server problems:


> 519 wwinzer at 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.
>
The above is from an excerpt I sent to the Technical Advisor
for Adaptec, who's a former co-worker.  He'll need to contact UU.NET
to straighten out his DNS woes.

- Wally Winzer Jr.

Michael Voight wrote:

> I get different NS records for adaptec.com.
>
> Non-authoritative answer:
> adaptec.com     nameserver = auth60.ns.uu.net
> adaptec.com     nameserver = auth02.ns.uu.net
>
>
> Authoritative answers can be found from:
> auth60.ns.uu.net        internet address = 198.6.1.181
> auth02.ns.uu.net        internet address = 198.6.1.82
>
> For SOA, I get:
>
> Non-authoritative answer:
> adaptec.com
>         origin = auth02.ns.uu.net
>         mail addr = hostmaster.uu.net
>         serial = 1999031506
>         refresh = 21600 (6 hours)
>         retry   = 3600 (1 hour)
>         expire  = 1728000 (20 days)
>         minimum ttl = 1800 (30 mins)
>
> You might want to do the same and check what you get.
> It looks like you might be getting old info.
>
> You might want to clear the cache on your nameserver and/or forwarder,
> if you have one. Usually this is done by restarting named.
>
> Michael Voight
> Cisco TAC
>
> Charles Wilkins wrote:
> >
> > Hi,
> >
> > We are running bind-8.2 as our primary nameserver.
> > I just noticed yesterday that we can' lookup www.adaptec.com or
> > ftp.adaptec.com.
> >
> > This wasn't always the case, but I can't say for sure when this
> > happened.
> >
> > After running a few checks i was able to confirm that www.adaptec.com
> > is up, and other domain nameservers can resolve this host.
> >
> > Why can't we?
> >
> > My domain is pcscs.com.
> > The primary authoritative nameserver for our domain is ns2.pcscs.com.
> >
> > After trying to perform a lookup on adaptec.com I get these entries in
> > the messages log:
> >
> > Lame server on 'www.adaptec.com' ( 'ADAPTEC.com' ?): [198.6.1.182].53
> > 'AUTH61.NS.UU.NET'
> > Lame server on 'www.adaptec.com' ( 'ADAPTEC.com' ?): [198.6.1.65].53
> > 'AUTH00.NS.UU.NET'
> >
> > It would appear that the nameservers for adaptec.com are these two
> > listed above.
> >
> > If I do a dig @ns2.pcscs.com any adaptec.com, I can see the
> > nameservers.
> >
> > If I do a nslookup www.adaptec.com ns2.pcscs.com  I get:
> > NS2.pcscs.com can't find www.adaptec.com: Non-existent host/domain
> >
> > Other nameservers can do the lookup:
> > If i do a nslookup www.adaptec.com ns1.home.com the proper addresses
> > are printed.
> >
> > We don't seem to be having any other lookup problems that I can tell.
> > Other hosts resolve fine.
> >
> > Any ideas anybody?
> >
> > Charles Wilkins  CNE / MCP / A+
> > Network Design Consultant
> > Practical Computer Solutions
> > http://www.pcscs.com
> > 609-321-1530
> > 609-321-0840 - fax
> > --
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/19990705/fa4e86d0/attachment-0001.html>


More information about the bind-users mailing list