Servers will not register with DNS after NIC swap
Posted on 2006-03-29
OK - first of all I know I'm stupid for only having 1 Domain Controller. Let's let that go for now.
My AD Domain is very small - 3 servers. 1 app server, 1 SQL server, 1 DC. This is for an application that users are accessing remotely, but the domain is necessary for the servers to start services using a single account.
I have been using the HP Network Teaming software to increase throughput and today I disabled it on the DC and assigned the static address that the teamed configuration was using to one of the adapters and disabled the other. Now, the app server and the SQL server cannot update DNS and the MSSQLSERVER service (and agent) will not start. The servers basically cannot see the DC/domain. I am seeing EventId: 11164 in the log of the app and sql server - eventid.net was basically no help.
"The system failed to register host (A) resource records (RRs) for network adapter with settings:
Adapter Name : <adapter>
Host Name : 2003 server name
Primary Domain Suffix : domain.local name
DNS server list : <dns server ip address>
Sent update to server : <Domain controller>
IP Address(es) : <ip>
The reason the system could not register these RRs was because either (a) the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not accept dynamic updates.
To register the DNS host (A) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator."
Again, I know running a single DC is silly.
What troubles me is that this is the same scenario, basically, as a NIC failing and being replaced on a DC. Would DNS/Domain Services basically break down then too (assuming the idiot was only running 1 DC - like me)?
Is there any way for me to recover from this? I tried ipconfig /registerdns and it failed. My DC is set to allow secure updates.