6 replies
by ins413
Let me try and get this straight. The member server you demoted was the root server for your domain? Are there other domain controllers availble on your network? If so, are there any others with a copy of the DNS database? If there is, I would suggest entering a static DNS entry in the DNS server for your domain. Try removing the account from AD, and re-enter the same account info without rebooting in between. I am just hoping that this server you demoted wasn't the master role holder forthe domain. Some more info might help, but I would try a deletion of the DNS entry for the server and computer account in AD. Then recreate the computer account and manually enter the DNS entry for it. You only need a host entry and DNS should take care of the rest.
Good Luck!!!
by ins413
by larryaoubre
by timwalsh
Need some more info here in order to give you a good answer.
Root server could be used in several contexts.
Are you talking the first server in the AD Forest root? If so are there other DCs at the Forest root level?
by larryaoubre
by larryaoubre
I am answering my own question. When the AD became corrupted and I was working with support to get it back up, they said that the ISP's DNS was not making my DNS the start of authority of the domain.
Of course since we restored my AD I can't run clean up or defragmentation. I hate to completely restore from back up.
Larry
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending