|Subject:||Reload DNS from AD recovers wrong IP address for host - pls help|
|Posted by:||Jools (julianchappell2-hat-hotmail.com)|
|Date:||Fri, 05 Jan 2007|
This problem is driving me nuts. Any help gratefully received :-)
My "active directory" and "AD integrated DNS" server recently got a new
static IP address reserved in the router's DHCP table. Periodically the
servers DNS record for itself gets its IP address changed to the old one,
which causes problems when clients try to access the server.
This usually coincides with the following error in the DNS event log:
DNS server has updated its own host (A) records. In order to ensure that
its DS-integrated peer DNS servers are able to replicate with this server,
an attempt was made to update them with the new records through dynamic
update. An error was encountered during this update, the record data is
the error code.
(There are no other DNS servers on the LAN - does this mean that the error
can be ignored?)
I can recreate the "wrong IP address" problem by opening the DNS
management console, right clicking the forward lookup zone for our LAN and
selecting reload from the menu - this always sets the server's IP address
to the old one.
When I manually update the IP address for the DNS host record in the
console, if the "update PTR record" box is ticked then I see the following
Warning: The associated pointer (PTR) record cannt be createdm probably
because the referenced reverse lookup zone cannot be found.
(I have no reverse lookup zone defined; I didn't think it was necessary
for a small LAN setup. Have I misinterpreted the relevance of this?)
Thanks in advance for your help, nice forum :-)
Using Opera's revolutionary e-mail client:http://www.opera.com/mail/