From: Mike's List (mikelist@sky.net)
Date: Tue Feb 25 2003 - 10:35:13 EST
Here's another strange thing, I can now do all nslookup at my nameserver
machine --then my clients can do nslookup on that particular domain just
fine. But if I don't do "nslookup nascar.com" then my clients can't do
nslookup nascar.com. So it seems the NS doesn't go to the root server
somehow?
I've done dig @a.root-servers.net . ns and pipe it into named.root file,
I've stop/start named. Bind is running w/permission of named:named not
as root.
- Mike
---------- original message ----------
~$ nslookup www.nfl.com ns1.sky.net
Server: ns1.sky.net
Address: 209.90.0.2
Non-authoritative answer:
Name: www.nfl.com
Addresses: 64.253.196.251, 64.253.196.252
-----
~$ nslookup www.nascar.com ns1.sky.net
Server: ns1.sky.net
Address: 209.90.0.2
*** No address (A) records available for www.nascar.com
Does the above indicates there's a problem w/my root caching? I can do
nslookup on most sites, but not on some sites, ie. displays on nascar.com
What do I need to look/check for? named.local? named.root?...been at this
for a couple of days now. Running Bind 9.2.1.
Thanks.
- Mike
[ Packages: ftp.patriots.net (sparc/x86) | www.ondruska.com (x86) ]
--
"Those willing to give up a little liberty for a little security
deserve neither security nor liberty."
-- Benjamin Franklin
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:25:52 EDT