Solved

DC not using proper FQDN

Posted on 2007-03-24
2
387 Views
Last Modified: 2010-05-18
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
Comment
Question by:novoconst
2 Comments
 

Author Comment

by:novoconst
ID: 18787318
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
 

Accepted Solution

by:
EE_AutoDeleter earned 0 total points
ID: 18962808
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

Free Tool: Postgres Monitoring System

A PHP and Perl based system to collect and display usage statistics from PostgreSQL databases.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
This article outlines the process to identify and resolve account lockout in an Active Directory environment.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question