Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Windows Server: DNS Suffix is Missing on Domain Controller Name Server Records

Summary: Refer to the information about troubleshooting a missing DNS suffix on name server records for a Windows Server domain controller.

This article may have been automatically translated. If you have any feedback regarding its quality, please let us know using the form at the bottom of this page.

Article Content


Symptoms

ISSUE:

When the Netlogon service is restarted on a domain controller (DC), the DC's name server (NS) records in DNS are missing the domain suffix.

SOLUTION:

This is most likely due to a missing primary DNS suffix on the DC. To resolve the issue, add the primary DNS suffix, which is typically identical to the DNS name of the Active Directory domain (company.com, for example) in the DC's System Properties window.

Steps:

1. Open the System Properties window.

    a. Server 2012 and later: This can be done by clicking on the Computer name link in the Local Server tab of Server Manager.

    b. Server 2008 R2 and earlier: This can be done by choosing Change System Properties under Server Summary on the right side of Server Manager.

SLN286525_en_US__11387301216611.630806-1

2. Click Change.

SLN286525_en_US__21387301367755.630806-2

3. Click More.

SLN286525_en_US__31387301475616.630806-3

4. Enter the DNS suffix in the appropriate field (circled in red above). The system will prompt for a reboot. Reboot the system when possible.

Check the DNS Manager console when the system comes back up to validate that the domain controller's name server records have the correct DNS suffix.


Additional Information

A domain controller with a missing or incorrect primary DNS suffix will not register its DNS records properly, which can result in a litany of Active Directory issues, including failure of clients to join the domain, replication failure, and Group Policy processing failure.
 

Cause

 

Resolution

 

Article Properties


Affected Product

Servers, PowerEdge

Last Published Date

12 Mar 2021

Version

3

Article Type

Solution