Microsoft has addressed a new known issue causing DNS stub zones loading failures that could lead to DNS resolution issues on Windows Server 2019 systems.
DNS stub zones are copies of DNS zones containing resource records needed to determine the authoritative DNS servers for a specific zone and resolve names between separate DNS namespaces.
According to details published on the Windows health dashboard, customers will encounter this known issue only after installing updates released on January 25 and later.
"After installing updates released January 25, 2022 (KB5009616) and later on affected versions of Windows Server running the DNS Server role, DNS stub zones might not load correctly, which might cause DNS name resolution to fail," Microsoft explained.
The other two Windows updates that might trigger these DNS resolution issues are KB5010427 (released on February 15) and KB5011551 (released two days ago, on March 22).
Microsoft has fixed this issue via the Known Issue Rollback (KIR) feature. However, it will not propagate to affected devices automatically.
Group policies for deploying the KIR fix
To fix the DNS issues on enterprise-managed devices where the buggy Window Server updates have been installed, the admins will have to install and configure two group policies.
"For information on deploying and configuring these special Group Policies, please see How to use Group Policy to deploy a Known Issue Rollback," Microsoft added.
The two group policies admins need to install and configure to resolve this known issue can be downloaded using the links below:
Microsoft has previously fixed multiple issues linked to the Windows January updates, including a Bluetooth issue causing Windows blue screens, Windows domain controller restarts caused by LSASS crashes, Netlogon issues, and a Windows Active Directory bug.
Redmond also released out-of-band (OOB) emergency updates to address issues caused by the January 2022 Patch Tuesday updates.
The problems they addressed were related to Windows Server Domain Controllers restarting, Virtual Machines failing to start, VPN connectivity, and ReFS-formatted removable media mount failures.
Comments
I_Rogue - 2 years ago
Every month we are lab rats.
BxN88 - 2 years ago
This issue occurred since Cumulative Update of January - It took 3 month to Microsoft to ack this issue. We have an open case open at Microsoft prior to this announcement and we still wait for a fix. Really a pain to troubleshoot.