Rebuilding client and adding back to AD causes DNS records to break

Andy 1

I've noticed that after rebuilding a Windows 10 client the DNS is often broken. Sometimes running "ipconfig /registerdns" will fix it, but maybe only 50% of the time. If ipconfig doesn't take care of it I have to contact the person that manages the DNS server to fix it manually. Is there something I can do to keep this from happening? We always remove the computer from the domain before rebuilding and image using SCCM which adds it back to the domain with the same name it had previously.

Andy

3 answers

Anonymous

2021-02-16T01:09:22.847+00:00

client the DNS is often broken
have to contact the person that manages the DNS server to fix it manually

What is broken and what is the manual fix?
Please sign in to rate this answer.
Andy 1 Reputation point

2021-02-16T01:27:06.51+00:00

Are you saying that having the server admin fix it manually is the best/only solution?
Sign in to comment
Anonymous

2021-02-16T01:28:21.813+00:00

Actually no, I was asking what is broken and what is the manual fix?
Please sign in to rate this answer.
Andy 1 Reputation point

2021-02-18T16:12:15.93+00:00

DSPatrick,

My apologies. I just glanced at your message and apparently only read the part of my message that you quoted and missed your question altogether.

What is broken is that the records do not match.
ping <computername> vs ping <computername.xx.xxxxxx.xxx> return different IP addresses.

What the actual fix is, I don't know. I report the problem to the admin and he does his magic. His suggestion when I asked him the same question was to assign static IP's to everything. I can do that, but would rather stick with DHCP if there's something I can do on my end to make it more reliable. That being said, I'm also seeing the same problem on a few of our systems that already have static IPs assigned.

Andy

Anonymous

2021-02-18T16:20:24.003+00:00

There's nothing to do from the client end of things. it simply sounds like something may be broken within the active directory / DNS infrastructure. Normally nothing needs to be done when rebuilding a desktop client, join domain, with DHCP setup. If the same computer name is being used then the simplest solution is to remove the computer account from active directory before the domain join.

--please don't forget to Accept as answer if the reply is helpful--

Andy 1 Reputation point

2021-02-18T17:01:33.857+00:00

SCCM deployment fails immediately if the computer's MAC address is found in AD or SCCM so we always remove the computer through ADUC before deployment. Would it make any difference if we were to remove the computer from AD using the Windows GUI for each system? Maybe waiting for some amount of time after removing it so to give it a chance to propagate through all of our DCs?

Andy

Anonymous

2021-02-18T17:29:29.737+00:00

I'd ask this one over here.
https://learn.microsoft.com/en-us/answers/topics/mem-cm-general.html

--please don't forget to Accept as answer if the reply is helpful--
Sign in to comment
Sunny Qi 10,926 Reputation points Microsoft Vendor

2021-02-16T05:03:04.237+00:00

Hi,

Thanks for posting in Q&A platform.

Before we go further, may I confirm with you if the issue is client cannot register DNS record in DNS server?

Best Regards,
Sunny

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Andy 1 Reputation point

2021-02-18T16:32:57.74+00:00

SunniQi,

Thanks for your reply. The problem is that the records do not match. That is, pinging <computername> vs pinging <computername.xx.xxxxxx.xxx> return different IP addresses.

Andy

Sunny Qi 10,926 Reputation points Microsoft Vendor

2021-02-22T08:01:40.413+00:00

Hi,

Thank you very much for your feedback.

May I know if the problematic client has 2 or more network adapters?

If the DNS Scavenging was enabled on DNS server, it may because the DNS scavenging was not working properly which having the refresh/non-refresh timer set too long. Please configure short refresh and non-refresh interval to see if the issue can be resolved.

Best Regards,
Sunny
Sign in to comment

Share via

Rebuilding client and adding back to AD causes DNS records to break

3 answers