Windows Server 2022 AD-integrated DNS Split

Question

Windows Server 2022 AD-integrated DNS: How to separate the existing integrated DNS into an independent DNS for resolution and uninstall the existing AD-integrated DNS service, and whether this will cause failures in resolution for existing domain-joined computers and users?

Answer 1

HI Domic,

I have performed the migration. Currently, the dcdiag /test:dns test is successful, but the system log keeps reporting errors.

The dynamic registration of the DNS record '_kpasswd._udp.xx01.com. 600 IN SRV 0 100 464 dc03.xx01.com.' failed on the following DNS server:

DNS server IP address: x.x.3.169

Returned Response Code (RCODE): 0

Returned Status Code: 10054

For computers and users to locate this domain controller, this record must be registered in DNS.

USER ACTION

Determine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller. To determine what might have caused this failure, run DCDiag.exe. To learn more about DCDiag.exe, see Help and Support Center. To initiate registration of the DNS records by this domain controller, run 'nltest.exe /dsregdns' from the command prompt on the domain controller or restart Net Logon service.

Or, you can manually add this record to DNS, but it is not recommended.

ADDITIONAL DATA

Error Value: An existing connection was forcibly closed by the remote host.

Answer 2

HI Domic，

Do I just need to change the AD-integrated zone to a standard zone, and then copy the DNS file to a standalone DNS for import?

Answer 3

Hi 超 邓,

Has your issue been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)

Domic V.

Answer 4

Hi 超 邓,

To separate an Active Directory-integrated DNS zone into an independent instance, open the zone's properties in the DNS Manager console under the General tab and change the zone type to a standard Primary zone. This action converts the zone from Active Directory storage into a standard text-based file located at %SystemRoot%\System32\dns\yourdomain.com.dns, which can then be transferred to your new independent DNS server.

Uninstalling the original DNS service without prior planning will cause immediate resolution failures for all domain-joined computers and users. Because clients rely on the specific DNS IP addresses provided by DHCP scopes or static TCP/IP settings, removing the service cuts off their authentication and lookup pathways. To prevent disruption, you must first host the zone on the new independent server, configure it to allow dynamic updates so clients can register their records, update the domain controllers to point to the new server so critical SRV locator records remain intact, and update all client IP configurations before decommissioning the original DNS role.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Domic Vo.