dig server problem
Pedro Espinoza
raindoctor at gmail.com
Thu Nov 29 07:11:39 UTC 2007
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.
platform: solaris 10, sparc, blade
More information about the bind-users
mailing list