Windows 11 Insider Preview build 26300 on DHCP and not getting registered in Active Directory DNS

Question

This workstation is part of a homelab setup. It's running Windows 11 Insider Preview 26300.8687, so the most recent updates are installed. It gets a DHCP lease from the (Windows Server 2025) DHCP server, but the workstation's FQDN is not being registered in my local DNS server (also Windows Server 2025). Doing ipconfig /registerdns doesn't work. The System log in Event Viewer gives Event ID 8020, and states:

"The reason the system could not register these RRs during the update request was because of a system problem."

As a result, I cannot use Remote Desktop to access the workstation using the FQDN, but I can access it when I use the NetBIOS name. All the other devices running Windows 11 are running 25H2 (26200) and are not having any problems.

I suspect this is probably a bug in 26300. Has anyone else encountered this issue?

Answer 1

The behavior is consistent with known DHCP/DNS dynamic update issues rather than something specific in the provided context about build 26300.

Use the following checks and mitigations that apply to DHCP/DNS registration problems in general:

1. Verify DHCP is actually doing the DNS registration
   • On the Windows Server 2025 DHCP server, confirm that the scope or server is configured to perform dynamic DNS updates for clients (A and PTR records) and that the DNS servers configured at the scope options, server options, or TCP/IP level support dynamic updates.
   • If DNS servers specified at the scope level do not support dynamic updates, DHCP will repeatedly retry and queue updates, delaying or preventing registrations for other clients.
2. Confirm DNS zones and reverse lookup zones
   • Ensure the forward lookup zone for the workstation’s FQDN exists and allows dynamic updates.
   • Ensure the appropriate reverse lookup zone exists and allows dynamic updates. Missing or misconfigured reverse zones are a common cause of DHCP DNS registration failures.
   • Use the DHCP server event logs to check for events such as DHCPv4.ForwardRecordDNSFailure or DHCPv4.PTRRecordDNSFailure, which indicate missing or misconfigured forward/reverse zones.
3. Check DHCP/DNS logging
   • Review the DHCP Server debug logs in %windir%\System32\Dhcp for detailed information about the DNS dynamic updates attempted for this client.
   • Use these logs together with the DNS server logs to see whether the DNS server is rejecting or failing the update.
4. Validate client-side DHCP behavior
   • On the Windows 11 Insider client, ensure the DHCP Client service is running and that no firewall is blocking DHCP traffic.
   • Run ipconfig /release and ipconfig /renew to force a full DORA cycle so the client refreshes any cached DHCP options (including Option 81, which controls who performs DNS registration).
   • If the client previously cached a different Option 81 configuration, a full DORA cycle is required to update that cache.
5. If DHCP is configured to “Always dynamically update DNS records”
   • In environments where DHCP is intended to own DNS records, but both client and server are creating or overwriting records, configure the client to honor the DHCP server override:
     1. Create RegistrationOverwrite (REG_DWORD) under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters.
     2. Set its value to 2 so that records created by the DHCP server overwrite those created by the DNS client.
     3. Restart the client and then verify forward and reverse lookup zones, cleaning up any stale A/PTR records that DHCP cannot modify.
6. Collect additional data if the issue persists
   • Capture DHCP server logs and, if needed, a network trace while renewing the client’s lease to see at which stage DNS registration fails.
   • Use these artifacts to determine whether the failure is on the client, DHCP server, or DNS server side.

If all other Windows 11 25H2 clients register correctly with the same DHCP/DNS infrastructure, focus on:

• Whether this Insider client is receiving different DHCP options (especially Option 81) or using a different scope.
• Whether the DNS zones and reverse zones used by this client are configured identically to those used by the working clients.

---

References:

• DHCP dynamic updates of DNS registrations are delayed or not processed
• Unexpected DNS record registration behavior if DHCP server uses "Always dynamically update DNS records"
• Client machines don't send DDNS updates when the DHCP server stops sending Option 81
• DHCP Logging Events for DNS Registrations
• Troubleshoot problems on the DHCP server
• Troubleshoot problems on the DHCP client