Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 392
  • Last Modified:

DC not using proper FQDN

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?

Colin
0
novoconst
Asked:
novoconst
1 Solution
 
novoconstAuthor Commented:
Found the solution, hopefully this helps anyone else out there avoid the hell I just went through:

http://support.microsoft.com/?id=257623&sd=RMVP

Run the script and it will append the DNS name so that you have the FQDN.

Colin
0
 
EE_AutoDeleterCommented:
novoconst,
Because you have presented a solution to your own problem which may be helpful to future searches, this question is now PAQed and your points have been refunded.

EE_AutoDeleter
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now