Hi all, I just set up a fresh install of UCS, but seem to be having some DNS issues, or possibly something with AD.
I created the UCS install with a hostname like ucsdc.mydomain.home, where mydomain.home is the current running domain. My windows domain controller was something like windc.mydomain.home. I successfully logged into the UCS machine and it joined the domain properly. I then initiated a domain takeover. All the processes completed successfully, so I shut down the old Windows domain controller, and reassigned the UCS machine with the IP addresses formerly assigned to the Windows DC so I didn't have to change much else in my system. I was able to verify that DNS seemed to be working last night, but that was it.
This morning I came to find that, in fact, most things were not working properly; my Windows domain client PCs couldn't seem to find the domain controller this morning. Figuring I might have to remove them and re-add them, I took a Windows 10 VM that was on the old DC and removed it from the domain, then attempted to re-add it, and that's where the real fun began. I was seeing some weird behavior with DNS; basically, I found that I could ping ucsdc from the command line successfully, but if I pinged ucsdc.mydomain.home, the address could not be found.
I scoured the DNS settings in my server, and only found one old record for the former windows domain controller, but I also noticed that all of the settings didn't seem to include the domain. For example, I found a record for ldap.tcp.dc.msdcs., but it should have said _ldap.tcp.dc._msdcs.mydomain.home. So, I went through and corrected all of those entries (I think); in particular, the entries referenced on this page.
Once I tried to add the machine back to the domain, I ran across an error as follows:
If I try nslookup ucsdc.mydomain.home, it works, but I get a message stating
I'm basically out of ideas right now, so I'm hoping someone here can help me figure this out. I'll be happy to provide more info as needed.