Windows 11 26H2 update - IPV6 DNS Broken?

Mr Cheese 1 Reputation point
2026-10-14T01:56:35.9366667+00:00

I service a number of end users with basic peer to peer LAN setups.

Over the last week or 2, there have been multiple issues raised with some apps not able to resolve the DNS for a server PC.

This seems to have started after running the 26H2 update.

We tried doing network resets etc, but the problem remained persistent. Sometimes the name would resolve, and sometimes not.

The way we are fixing this, is to disable the IPV6 on the server.

After doing that, the DNS resolution issues problems stopped completely.

Seeking more information, as from our perspective, it seems that this 26H2 update has broken some aspect of IPV6 DNS.

Windows for home | Windows 11 | Windows update
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-10-14T01:56:52.68+00:00

    The available information supports a DNS client resolution issue, but not a confirmed Windows 11 26H2 IPv6-specific defect.

    What is supported:

    1. Windows DNS clients query configured DNS servers in order and can experience delays when earlier servers are unreachable.
      • With three or more DNS servers configured, Windows tries the first server at 0 seconds, the second at 1 second, the third at 2 seconds, then all servers at 4 and 8 seconds, and stops at 10 seconds.
      • If the only reachable server is in position 4 or later, resolution is delayed by at least 4 seconds, which can cause application timeouts.
    2. If several DNS servers are configured on the NIC and some are unreachable, name resolution can take nearly four seconds by design.
      • This can be long enough for some applications to fail even though DNS eventually succeeds.
    3. nslookup is not a reliable test in that scenario.
      • It contacts only the primary DNS server configured, so it can fail even when Windows name resolution through the DNS client can still succeed.
    4. If a Hosts file entry exists for the target name, Windows resolves from the Hosts file before querying DNS.
      • That can hide or change the observed behavior during testing.
    5. There has also been a documented case where corrupted DNS records from an external DNS provider prevented access to Microsoft services until ISP DNS caches refreshed.
      • That shows intermittent DNS failures can come from upstream DNS infrastructure, not only from the local Windows update.

    Based on that, the most likely interpretation is:

    • The update may have changed timing or exposed an existing DNS configuration weakness.
    • Disabling IPv6 may be acting as a workaround by changing which DNS path or server responses are used.
    • The context does not confirm that Windows 11 26H2 broke IPv6 DNS itself.

    Recommended checks for the affected systems:

    1. Review the DNS server list on the affected adapter.
      • Make sure the reachable and correct DNS servers are in the first three positions.
      • If unreachable servers are listed first, Windows can delay queries long enough for apps to time out.
    2. Test with Resolve-DnsName instead of relying on nslookup.
      • nslookup only tests the primary DNS server and can give misleading results in multi-DNS-server scenarios.
    3. Check whether the DNS suffix search list is long or misordered.
      • A long suffix list can add delays if the correct suffix is low in the list.
    4. Check the Hosts file at C:\Windows\System32\drivers\etc.
      • Remove stale entries for the server name if present, because Hosts entries override DNS queries.
    5. If the systems use ISP-provided DNS, verify whether the ISP or upstream DNS service is returning incomplete or corrupted answers.
      • The documented Windows Update DNS incident showed missing address data in DNS responses when upstream DNS was corrupted.
    6. If IPv6 disablement consistently fixes the issue, treat that as a workaround rather than proof of root cause.
      • The supported material here does not identify a 26H2 IPv6 regression.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Francisco Montilla 31,345 Reputation points Independent Advisor
    2026-10-14T04:37:14.98+00:00

    Hello,

    Starting prominently with the recent feature rollouts, the operating system aggressively prioritizes routing DNS requests over IPv6 anytime it detects that both network stacks are enabled on the adapter. Even if it just senses an automatic local link address starting with fe80, it will attempt to resolve hostnames via IPv6 first instead of gracefully falling back to your functional IPv4 local mapping. In basic peer to peer network environments, your switches and routers are likely not fully configured to manage or intercept these internal IPv6 queries.

    Simply disabling it is currently the most practical diagnosis and workaround for simple unmanaged LAN setups like you are dealing with.

    Since you service multiple clients with this setup, are all these local server PCs acting as file shares in standard simple workgroups, or do you have any actual Active Directory controllers in place where you might eventually need to leave IPv6 toggled on for network policy communication?

    I can run you through how to manually change the Windows network prefix priorities under the hood if you happen to need a scenario where IPv6 stays enabled.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.