DrRichard
asked on
DNS: No Entry But Nslookup Finds It
Running Bind v8 on Solaris 2.6 Sun box. This is the one and only primary DNS server.
Cache has been flushed. No other problems are apparent except for one particular entry being described below.
Doing an "nslookup" finds and reports back name and IP of a local server off the DNS table but this entry (local server) is not found in the DNS table. The IP Address reported by the nslookup is NOT assigned to this local server but may have been in the past. Can someone explain what could be happening here?
Also, running "nslookup" on name responds back correctly but give the full name and it fails.
Example: Our domain is: localserver.net
nslookup johndoe responds CORRECTLY while nslookup johndoe.localserver.net FAILS.
What could be wrong?
Cache has been flushed. No other problems are apparent except for one particular entry being described below.
Doing an "nslookup" finds and reports back name and IP of a local server off the DNS table but this entry (local server) is not found in the DNS table. The IP Address reported by the nslookup is NOT assigned to this local server but may have been in the past. Can someone explain what could be happening here?
Also, running "nslookup" on name responds back correctly but give the full name and it fails.
Example: Our domain is: localserver.net
nslookup johndoe responds CORRECTLY while nslookup johndoe.localserver.net FAILS.
What could be wrong?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
/etc/resolv.conf is correct showing the correct domain and nameserver IP address.
The "named" process has been stopped and started several times which is suppose to flush the cache each time. The DNS server has been up running for the past 155 days. The same behavior is seen elsewhere.
The "named" process has been stopped and started several times which is suppose to flush the cache each time. The DNS server has been up running for the past 155 days. The same behavior is seen elsewhere.
Seeing the same behaviour from other systems does tend to imply that this is a DNS server problem. if you do:
# nslookup
> ls my-domain.tld
do you see the IP & hostname of the server in question in the output?
# nslookup
> ls my-domain.tld
do you see the IP & hostname of the server in question in the output?
ASKER
Rebooting the server worked. It took about 10 minutes to come back up but that worked. We are going to upgrade to Solaris 2.7
Are there other DNS servers defined.
And do you have the next entry : domain localserver.net