nslookup works locally, fails remotely

Rik Thomas rikt at delaware.net
Tue Sep 7 19:18:57 UTC 1999


It looks like they need to pay their Internic Bill.  They owe $70
perpetualtides.com  7325279  $70.00
A good place to start after you do the local and remote nslookup thing is to
dig the root servers next.

Then check the payment page at Network Solutions.
--
Rik Thomas, CTO, Delaware.Net, Inc.
web: http://www.delaware.net  email: rikt at delaware.net
phone: 302-736-5515  toll free: 888-432-7965
We host Delaware's premier Internet address: http://www.Delaware.com
wje at wje.net <root at wje.net> wrote in message news:37d5335f at news.csinet.net...
> Greets,
>
> I'm seeing some strangeness for a domain we've hosted for ages.
>
> Recently, a customer called to complain that users of our DNS servers can
get to perpetualtides.com, while users of !(our DNS servers) cannot.
>
> This domain has been registered w/InterNIC for quite a while and has been
working flawlessly until just very recently, and whois returns the correct
numbers for the primary and secondary name-servers.  I'm not aware of any
changes made to the domain data, and all indications are that no changes
have been made.
>
> Of course, Step One is Reproduce The Problem and sure enough, "nslookup
perpetualtides.com ns[2].csinet.net" gives the correct results, but
"nslookup perpetualtides.com some.other.dns" fails with a "*** other.dns.box
can't find perpetualtides.com: Non-existent host/domain" message.
>
> Neither the Linux2+BIND8 nor the WinNT4+MS-DNS name-servers complain about
anything in the domain data, and both serve the correct answers locally.
>
> Most puzzling -- any clues as to where to look next?
>
> jim
>
> jimw(at)csinet(dot)net
>
>




More information about the bind-users mailing list