Hi all, I want to open a general discussion whether or not to disable Dynamic DNS registration on Servers.
The problem I have been seeing is that Dynamic DNS record are removed although DNS savaging is disabled. I have been troubleshooting the issue, as DNS records normally do not disappear out of the blue. Now troubleshooting has pointed out that the problem usually occurs when the network drivers are re installed or Updated. We see the issue when Vmware tools are being Updated, or when the physically servers are being patched with HP service pack (PSP). I am aware that Dynamic DNS should not be a problem because in normal circumstances, as the record is being recreated after reboot by the same DDNS.
However this is not always the case, in which DNS records go missing. It could be related to following issue: http://support.microsoft.com/default.aspx?scid=kb;EN-US;2520155
although the article only menntioned Windows Server 2008 (and R2), I have seen the problem occurring on Windows Server 2008, 2008 R2 and Windows Server 2012.
It is not that we deliberately rely on DDNS for our servers, but people forget to disable DDNS on the Interface settings in which Static DNS records are overwritten by DDNS records.
Seeing those issues, i am thinking of completely disabling DDNS and move to a complete static DNS procedure for our servers. However moving to a complete Static DNS requires the proper procedures to be in place, and that they are implemented when creating and/or demoting servers. This brings on extra administrative overhead, How do would you handle DNS for servers, in an environment running close to 200 servers?
The problem is not related to duplicate DNS zones in AD, because I have checked that. The problem seems to be related to what is described in previous article, as we are also moving to new DNS servers in our environment.
Answers provided are coming from personal experience, and come with no warranty of success. I as everybody else do make mistakes.