1

I had to remove to old DCs from my network that were DNS Servers. They both died and I deleted the DCs from AD users and computers Domain Controllers manually. Now I am having issues with DNS. Can I go into the DNS and remove all the indicators of the old dead DCs?

6 Spice ups
2

This is even causing permissions mapping drives to the data server which is the DNS server.

Computers don’t have authorization to access the data server. No computers are getting the group policy to map drives. Right now I am at a loss of what the problem could be.

1 Spice up
3

Is there at least one remaining working domain controller?
If so make sure all current DCs have their DNS server settings updated to use a valid other DC first then themselves for dns.

does “netdom query fsmo” list working valid DCs for all the roles? If not you will have to manually seize them.
Only then can you manually clean the old DCs out of AD - https://techcommunity.microsoft.com/blog/itopstalkblog/step-by-step-manually-removing-a-domain-controller-server/280564

4 Spice ups
4

For those seeing this, it relates to here.

Computer not seeing AD Server - Networking - Spiceworks Community.

I am wondering if your clients are not syncing with the domain and this domain never synced with the now, dead DCs.

They may have been running alongside each other without noticing an issue.

1 Spice up
5

I think I figured it out. It was a DNS issue. I had to go through each item in DNS to remove all the old DCs. NTDSUTIL did not remove all the settings from DNS which was causing the issue. Thanks for your help in pushing me in the right direction.