Solved

DC not using proper FQDN

Posted on 2007-03-24
2
388 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
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

Office 365 Training for IT Pros

Learn how to provision Office 365 tenants, synchronize your on-premise Active Directory, and implement Single Sign-On.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
LDAP Setup 6 56
Office 365: Assigning MailboxPlan to a mailbox 8 66
Changing email address in Exchange 2010 2 45
Export Photos from Active Directory using Powershell 4 24
This article runs through the process of deploying a single EXE application selectively to a group of user.
A hard and fast method for reducing Active Directory Administrators members.
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

738 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