[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

2003 DC Full Computer Name is not the FQDN causing netdiag and dcdiag errors

A few weeks ago the Full Computer Name of all our DC's started showing as the computer name with the IP address of the PDC appended. ie computer.192.168.1.1.
They can still replicate but //domain/sysvol is no longer available to PC's on the domain and dcdiag /fix and netdiag /fix produce many errors including not being able to register the domain name. All DNS queries work when supplying either just the computer name or the fqdn.
0
M_Holmes
Asked:
M_Holmes
  • 3
  • 2
  • 2
  • +1
1 Solution
 
Henrik JohanssonSystems engineerCommented:
If domain is 2003 functional level, you can rename the DC
System Properties (sysdm.cpl) -> Computer Name -> Change -> More
Change the primary DNS suffix to the correct domain's DNS suffix
0
 
Glen KnightCommented:
Probably the DNS Suffix.

Check the following:

properties of the network card, highlight TCP/IP select properties then advanced then under DNS suffix do you have the IP address listed instead of the domain name?

Also right click my computer select properties then computername and click more (not sure if you can change this when it's a DC but worth checking just in case)
0
 
M_HolmesAuthor Commented:
The Computer name is correct. The "Full Computer Name" shows up incorrectly. I have changed all incorrect instances of it from DNS. Changed the computername using netdom to FQDN and rebooted. After the reboot the "Full Compter Name" returns to "computername.10.0.10.5."
I am guessing this is being populated from AD.
TCP properties are correct so is the DNS suffix information and have not been changed in years.
king.bmp
0
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!

 
Glen KnightCommented:
Try changing the full computername to something else then changing it back.

Check you other DC's?
0
 
Henrik JohanssonSystems engineerCommented:
As the local configuration seems to be correct, check the GPOs
Use RSOP.msc to evaluate what GPO is configuring the policy setting and use GPMC.msc to edit it.

Computer Configuration\Administrative Templates\Network\DNS Client\Primary DNS Suffix
0
 
ChiefITCommented:
Check the NIC configuration "register this DNS suffix", as demazter was recommending.

0
 
ChiefITCommented:
Don't rename the DC. Then you will have all kinds of problems.

Something is causing your DNS registration to be askew.
0
 
Glen KnightCommented:
Sorry I didn't mean rename the DC I meant just change the suffix and then change it back!

My bad! :-/
0
 
M_HolmesAuthor Commented:
Someone had misconfigured the GPO and put the DNS in the DNSSuffix box.

Thanks for all your help.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now