I just upgraded an NT domain from 4.0 to Windows 2000 Active Directory. Now I am having a problem with only some Windows 2000 Pro workstations. They can log into the domain no problem. But their DNS is not working right. They are pointed to the proper W2K DC DNS server.
However, when you go into the properties of My Computer and then the Network Identification tab, the Full Computer Name shows the computer name without the AD DNS suffix (.local). If you go into Properties and then More from here, you can set the Primary DNS Suffix to ".local" and then everything works fine.
I've done a lot of these upgrades, and never seen anything like this. Again this is only on some of the W2K computers. Others dynamically changed their computer name as they were supposed to and everything works fine.
As another note, there is a DNS suffix being pushed out by DHCP for the company's public web server XYZCompany.com. This is an appended DNS suffix so they can access the website internally. Could this be the problem? When we created another zone in DNS called XYZCompany.com and added a few necessary host records, the computers with DNS problems could resolve things no problem.
So the questions are, why hasn't the primary DNS suffix change dynamically on some of the computers and why is this XYZCompany zone addition a working temporary solution.
Thanks for any thoughts.