Strange - Server will not perform DNS update of it's new IP address (DR scenario) to the domain
We are testing a failover of services for a number of servers. One of those portions is bringing up our Lotus Notes server at a remote office. In our main branch office we have our mail server as 10.0.0.120 and when it comes up in our transatlantic remote office it is on a different IP scheme (10.1.7.120). The failover is fine and all services work however, the DNS A record does not update for the domain (even if you do a /flushdns /registerdns manually from the 10.1.7.120 server (which has not taken the same hostname).
The strange thing is that there is even a active DC (GC/DNS/DHCP) at the remote office (10.1.7.2).
The only way we've gotten this to work is to manually go into DNS management and update the A and PTR record manually.
The strange thing is that there is even a active DC (GC/DNS/DHCP) at the remote office (10.1.7.2).
The only way we've gotten this to work is to manually go into DNS management and update the A and PTR record manually.
Is your DNS server setup for only Secure Dynamic updates? Try to change it to Nonsecure and Secure or change the security permissions on the A record itself.
Are there any errors in the DC's DNS event log?
ASKER
No errors in the DC's DNS event log.
How do I check if the DNS servers are setup for only Secur Dynamic updates or not?
How do I check if the DNS servers are setup for only Secur Dynamic updates or not?
In the server's DNS console, right-click the appropriate forward lookup zone and select Properties. Under the General tab of the properties window, you'll see a dropdown for dynamic updates. The three options are Secure only, Nonsecure and secure, and None.
ASKER
It is set to secure only.
Changing to to nonsecure - won't this present a security problem/limitation?
Changing to to nonsecure - won't this present a security problem/limitation?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok tried that just to test it out. Looks like the problem is still there even though we had both DCs on Nonsecure and secure updates.
Actually, I just checked the event logs and there was a DNSAPI error saying that the computer failed to update the A record and to run a /registerdns manually... I'm a little curious to find out why though. Any ideas on how to troubleshoot?
Actually, I just checked the event logs and there was a DNSAPI error saying that the computer failed to update the A record and to run a /registerdns manually... I'm a little curious to find out why though. Any ideas on how to troubleshoot?
Post the text of the DnsApi error, if you don't mind. There may be something in there that indicates why the registration failed.