Hi,
I have a Windows Server 2022 Workgroup (non-domain) server running DNS role only as a forwarder. It forwards all queries to 2 internal DC/DNS servers. Clients point directly to this server for DNS resolution.
What happened:
Last night I manually installed the April 2026 Cumulative Update and rebooted the server. After reboot I noticed Event ID 404 in the DNS Server event log:
"The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 172.x.x.x"
The DNS service was in Running state after reboot, but forwarder was not working — clients couldn't resolve anything.
Environment:
Windows Server 2022 Workgroup (not domain joined)
DNS role configured as forwarder-only
Forwards to 2 internal DC/DNS servers
Primary DNS on NIC is set to 127.0.0.1
DC/DNS IPs are only in DNS Manager forwarder list — NOT configured in NIC settings
TCP port 53 to both DC/DNS servers is reachable (Test-NetConnection confirmed)
What I've checked:
Test-NetConnection -Port 53 to both forwarder…