SUMMARY: dig and dns problem

The problem as described in the first mail occured only on solaris
boxes; but not on linux. Researching further showed that
/etc/inet/hosts and /etc/hosts are out of sync. /etc/inet/hosts    was
mapping ns1.domain to x.y.z.130. Changing that fixed the problem.

Thanks, Pedro.




My original question:

I have changed the IP address of one of our name servers (ns1).
ns1 old IP is x.y.z.130; now ns1old is the hostname for the old IP, x.y.z.130
ns1 new IP x.y.z.150

on ns1:

When I do, nslookup ns1, I am getting x.y.z.150 (no problems at all).
When I do, host ns1, i am getting x.y.z.150 (no issues at all).
When I do, dig ns1, i am getting x.y.z.150 (no issues at all).

When I do, dig @ns1 ns1.ourdomain, I am getting the proper A record in
the answer question.

However, I am getting FALSE information in the comments.

;; Query time: 31 msec
;; SERVER: x.y.z.130#53(x.y.z.130) <------- THIS IS THE PROBLEM
;; WHEN: Thu Nov 29 01:54:34 2007
;; MSG SIZE  rcvd: 107


The @ns1 is leading to old IP address. Any suggestions?



My resolver.conf is perfectly fine. I even changed keep_hot_count
hosts to 0 in nscd.conf, and bounced that daemon.

Even the reverse lookup of x.y.z.130 is giving me ns1old.domain.



Thanks, Pedro
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers