nslookup problems
Mark.Andrews at iengines.com
Mark.Andrews at iengines.com
Wed Dec 8 04:57:08 UTC 1999
I would bet that named found errors in your zone files and
as a result the search performed by nslookup is aborting.
Check your syslog (/var/adm/messages) for errors reported when
named starts and correct them.
Nslookup is *not* a good diagnostic tool as it does to much
other stuff.
Mark
> We have just updated all of our nameservers to 8.2.2 p5 and we are
> having problems doing nslookup:
>
> bash$ nslookup
> Default Server: picnic.ziplink.net
> Address: 206.15.168.65
>
> > sibor.com
> Server: picnic.ziplink.net
> Address: 206.15.168.65
>
> *** picnic.ziplink.net can't find sibor.com: Non-existent host/domain
>
> > server sundog.tiac.net
> Default Server: sundog.tiac.net
> Address: 199.0.65.9
>
> > sibor.com
> Server: sundog.tiac.net
> Address: 199.0.65.9
>
> Name: sibor.com
> Address: 207.221.47.232
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> This problem seems to come and go with some domains and like the one
> above, we have not been able to resolve the domain.
> Any help would be appreciated......
>
>
--
Mark Andrews, Internet Engines Inc. / Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at iengines.com
More information about the bind-users
mailing list