Came across this researching some upgrade issues, may be relevant
DNS Host record of a computer is deleted after you change the DNS server assignment https://support.microsoft.com/en-us/kb/2520155 · You perform one of the following operations on the client computer: You restart the computer. · You restart the DNS client service. · You run the ipconfig /registerdns command. In this scenario, the DNS Host record of the computer is deleted from the DNS server. Therefore, name resolution issues occur. From: [email protected] [mailto:[email protected]] On Behalf Of Russ Sent: Wednesday, May 04, 2016 1:37 PM To: [email protected] Subject: [spam] [dkim-failure] Re: [NTSysADM] Servers not registering in DNS after reboot That's interesting - I don't think that's our issue as we've not had any unusual uptime or changes in DNS configurations, but that's a good one to know - thanks for sharing! On Mon, May 2, 2016 at 2:30 PM, Shaun Arrowsmith <[email protected]<mailto:[email protected]>> wrote: What’s the uptime on the boxes? We had something like this a while ago, the uptime on our servers was quite high though, we found and installed this https://support.microsoft.com/en-us/kb/2520155<https://urldefense.proofpoint.com/v2/url?u=https-3A__support.microsoft.com_en-2Dus_kb_2520155&d=BQMFaQ&c=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI&r=TA_mjBT8bS0r8rLrnubGjA&m=U9taNaplBk9KoG5eRwVngbrfZIQ4rPI5_FVU4iCiNPg&s=g45chd2HTZT9BPDFDPburMMtgkwrYbh3MYyHt42_xdM&e=> From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Russ Sent: 02 May 2016 18:19 To: [email protected]<mailto:[email protected]> Subject: Re: [NTSysADM] Servers not registering in DNS after reboot We may do something like that - we are looking at putting together a monitor in SCOM which checks and if it notices that a server goes unreachable by name it tries to run a command to register DNS. But it just seems a bit backwards to be "fixing" something rather than preventing. Oh well - just thought someone might have run into a similar issue. Thanks! On Fri, Apr 29, 2016 at 2:11 PM, Charles F Sullivan <[email protected]<mailto:[email protected]>> wrote: As a workaround, you could create a simple batch file with the command to register DNS and add it to a Scheduled Task GPO preference setting. The task could be set to run 5 minutes after startup, or 10 minutes if you think the servers can spare it. Not a solution, but as I said, a workaround. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Russ Sent: Friday, April 29, 2016 4:25 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] Servers not registering in DNS after reboot So we have had issues with servers registering properly in DNS after a restart. They seem to deregister as they shut down but then when they come back up, the DNS servers do not have their address again. It doesn't happen every time, or with the same servers every time. The servers are static IP addresses, but register in DNS dynamically. If I find they haven't register, and I manually run ipconfig /registerdns, then everything registers properly and works the way it should. Any ideas? DNS is AD enabled, servers are in the same domain. We have many many more servers which are rebooting and are not having issues dynamically registering, and it's not these particular servers. It just seems that after a monthly patch cycle and reboot we have a handful (or one or two) who lose their DNS. Anyone seen anything like this? We'd rather not have to set all the DNS entries manually.
