Machine lost DNS entry

  • 244 Views
  • Last Post 10 November 2016
kitaab posted this 27 September 2016

We have one server that loses its DNS entry sometimes. What can we check.

It happens to only this machine.

It has stactic IP address assigned

Once we run ipconfig /registerdns it starts working again. 

The timeline on how long before the issue may reapper (i.e lose the DNS entry) is not fixed. 

But it had done it over 4 time in past 1 year.

-- Only 1 machine that we have noticed does it --- so it doesnt look to be DNS Server related

We run DNS on the Domain controllers  (Windows 2008 AD)

 

Order By: Standard | Newest | Votes
kumarv389 posted this 27 September 2016

Hi Vivak,

If there is an issue with single member server (2008 R2), please refer the below link.

https://support.microsoft.com/en-us/kb/2520155

I had same issue one of my 2008 R2 member server, the DNS host entry will be disappear very often.

The issue will be fixed after DNS client service restart.


--------------------------------------------
On Tue, 27/9/16, vivakhangloo@xxxxxxxxxxxxxxxx wrote:

Subject: [ActiveDir] Machine lost DNS entry
To: activedir@xxxxxxxxxxxxxxxx
Date: Tuesday, 27 September, 2016, 12:46 PM



We have one server that loses its DNS entry
sometimes. What can we check.

It happens to only this machine.

It has stactic IP address assigned

Once we run ipconfig /registerdns it starts working
again. 

The timeline on how long before the issue may reapper
(i.e lose the DNS entry) is not fixed. 

But it had done it over 4 time in past 1 year.

-- Only 1 machine that we have noticed does it --- so it
doesnt look to be DNS Server related

We run DNS on the Domain controllers  (Windows 2008
AD)

show

Ravi.Sabharanjak posted this 28 September 2016

Some things to consider – Is there anything (acls etc) preventing the refresh of the record? And the DNS server is scavenging it? Are there registry entries on the DNS client that are setting the refresh period to be too long that the record is getting scavenged as stale? How are your refresh and norefresh settings on the zone? Do they allow enough time for clients to refresh? Is the up in a dhcp scope and the dhcp server sending a name release to the DNS server perhaps? (check the dhvp logs in windows\system32\dhcp. -Ravi   

show

kitaab posted this 28 September 2016

since it is only 1 client that has issue , i assume server settings may not be relevant.However looking at the clients eventlog i can see this entry . it feels that the client is trying to refresh old name (before joining to domain) instead of registring its domain name.
EventID 8004The system failed to register network adapter with settings:
           Adapter Name : {383412C9-DF83-4244-8C84-9D71782B799F}           Host Name : SERVERDBA101           Adapter-specific Domain Suffix : WIN-6O82CTS14JM           DNS server list :              192.168.1.1, 192.168.1.2, 192.168.1.3, 192.168.1.107           Sent update to server : <?>           IP Address(es) :             10.88.161.203
The cause of this DNS registration failure was because of DNS server failure. This may be due to a zone transfer that has locked the DNS server for the applicable zone that your computer needs to register itself with.
(The applicable zone should typically correspond to the Adapter-specific Domain Suffix that was indicated above.) You can manually retry registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your network systems administrator to verify network conditions.

show

kitaab posted this 10 November 2016

Any other suggestion for this.

Close