Servers will not register with DNS after NIC swap

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 - was basically no help.

EventId 11164:

"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.



Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Actually, it's not the same as a NIC failing.

Reinstate the Team.
Dissolve the Team correctly in the software.
Now disable the extra NIC.

RTPITAuthor Commented:
OK - when you say "dissolve the team correctly in the software" how is that done? I used the Dissolve button. Am I missing something?
Yes, in the HP software there is a dissolve button.

You should now show 2 green network connections in the software - is that correct?

Now select the NIC that is at the top of the binding order - Advanced>Advanced Settings in the Properties of My Network Places - and put the IP information on that one.

Disable to other NIC.

10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

RTPITAuthor Commented:
That's exactly what I did to break it. I have re-established the team and the DNS on the APP and SQL servers were able to re-register. I'm going to leave it alone and not dissolve the team. And buy a second DC.


some problem here  "Primary Domain Suffix : domain.local name "
seems to single name  DNS

I thikn some problem with DNS configaratiion when first installayion . singel name not allow to dynamic registration.

you have do some setting manualy, follwoing MS article explain it

Sounds like the way I would do it.

At least you're back in business.

I forgot to add that the Team software has to be uninstalled to release both NICs after they have been teamed.  There are extra shims installed into the stack (you can see them in the properties of the NIC) that must be removed.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RTPITAuthor Commented:
I will absolutely retain that for the next time I try to screw up an AD domain!

Thanks Netman66.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.