DC not using proper FQDN
Posted on 2007-03-24
We have a domain controller that cannot see itself. I patched up a few errors regarding the DNS, but it seems that the server refuses to look at itself with a FQDN. For example, on the server's DNS it will only register server1 as the FQDN. I can manually enter server1.domainname.com, but the server will update and add server1 with an unknown IP address for the NS entry and SOA. Also, the computer name under System Properties is server1. rather than server.domainname.com. Needless to say this is causing a lot of problems on my network, the biggest of which is Exchange.
In every aspect this server refuses to list it's FQDN as anything but server1. What can I do to remedy this?