Sometimes when I use DCPROMO to install AD and the DNS service on my Windows 2000 Server, it does not create the correct entries in the zone database. Why?
After you run Dcpromo.exe and Windows 2000 automatically installs and configures the Domain Name System (DNS), the primary DNS server is left as the current DNS server. This causes Netlogon error messages that are related to DNS registration not working. For example:
Event Source: NETLOGON Event Category: None Event ID: 5781 Date: Time: User: Computer: Description: Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available. Data: 0000: 0000232a
When an administrator chooses to automatically configure the DNS server to be authoritative for the new zone, the DNS service is installed and the DNS zone for the domain is created. The DNS client configuration for the computer’s primary or secondary DNS server is not changed.
To resolve this issue, use any of the following methods:
Devolutions Remote Desktop Manager
Devolutions RDM centralizes all remote connections on a single platform that is securely shared between users and across the entire team. With support for hundreds of integrated technologies — including multiple protocols and VPNs — along with built-in enterprise-grade password management tools, global and granular-level access controls, and robust mobile apps to complement desktop clients.
- Create a delegation to the new DNS server on the primary DNS server.
- Configure the DNS server’s primary DNS server address with its IP address, or remove the value for the Primary DNS Server setting so that the computer uses its IP address.