Upgrade the computer to the domain controller for troubleshooting

Each domain must haveDomain ControllerHowever, when upgrading a server to a domain controller, there are usually minor faults for various reasons. This article lists an example of minor faults.

When a Windows 2003 Server is converted to a domain controller, the system will write some special domain name resolution records toDNSService (in general, it is Microsoft's own DNS service, but the third-party DNS Service will also have the same situation ). These records include the Globally Unique Identifier (GUID) of the entire domain environment.Activity directoryYou can use the GUID address for DNS resolution.

If an administrator upgrades the DNS to a domain controller without installing and configuring the DNS service for a machine in advance, the DNS resolution records in the above Active Directory will not be correctly configured. This will cause the DNS service to not save these special resolution records, resulting in some network connection problems. You can use a command dcdiag to perform the test. It fails to connect to the DNS server. Generally, the error message is similar to the following:

The guid dns name of the service cannot be resolved as an IP address. Check the DNS service name and DHCP name. Although the guid dns name (. _ msdcs. domain-name.local) cannot be resolved, the server name can still be resolved to an IP address and can be pinged. Check whether the IP address is correctly registered in the DNS service.

Obviously, this problem will cause your Active Directory to fail to work normally. The following is a solution to this problem:

1. Ensure that the system's TCP/IP settings are correct and that they are configured to support the local DNS service.

2. open "My network connection" | "Local Connection" (or any network connection you are currently using) | "Internet Protocol (TCP/IP) "|" attribute "|" advanced "|" DNS ".

3. Set the first DNS server to a local computer. It can be the local network address or 127.0.0.1 (loopback address ).

4. Select "add primary DNS suffix" and "add parent suffix to primary DNS suffix.

5. register the connection address in DNS, and click OK to exit.

6. In command prompt line mode, enter the command ipconfig/flushdns and run it. Then, enter ipconfig/registerdns to clear the local DNS resolution cache and register DNS source records separately.

7. Open the DNS console and find the host records, SOA records, and Name Server records for the computer Name.

8. In the Forward query area (Forward Lookup Zones), locate the DNS region used for the Active Directory domain and view its attributes.

9. Select "Active Directory integration" in the region type, select "only security" in the dynamic update type, and click "OK" to exit.

10. Enter netdiag/fix in the command prompt line mode and run it. Then, run the net stop netlogon and net start netlogon commands to apply the changes you just made.

11. Finally, run dcdiag to test whether the DNS Service of the domain controller works properly.

This minor fault occurred when the computer was promoted to the domain controller. If the reader had encountered this problem, it would not be a problem. I hope this article will be helpful to readers.