- last edited on by
ErikaB1
Hi all,
Posting this in case anyone has seen something similar or can point me in the right direction. I have another work colleague who is also on EE and is having the same problem.
On my work laptop, DNS queries for domains which don't exist in public DNS — both A and AAAA — are extremely slow to time out (around 8-10 seconds) when directed at the IPv6 DNS server assigned by DHCP. The IPv6 address being handed out points to my router's IPv6 DNS server, and it seems like queries sent to that address just stall rather than failing fast. This delay stalls the entire DNS resolution process on my work laptop, causing slow logon times.
The delay doesn't manifest when using the IPv4 DNS server or Google's DNS servers (IPv4 or IPv6). Disabling IPv6 allocation via DHCP also fixes it although i dont believe that is a good solution. I suspect a recent change was made to DHCP on the router, as I don't recall an IPv6 entry being present in the advertised DNS servers previously.
Below are the network details for my work laptop and the tests I've conducted to showcase this issue. Note that I'm able to replicate this delay on my personal laptop, so it's not specific to the device itself.
Wireless LAN adapter WiFi:
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX201 160MHz
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a00:23c8:xxxx:xxxx::xxxx(Preferred)
Lease Obtained. . . . . . . . . . : 29 May 2026 08:32:57
Lease Expires . . . . . . . . . . : 30 May 2026 08:32:55
IPv6 Address. . . . . . . . . . . : 2a00:23c8:xxxx:xxxx::xxxx(Preferred)
Link-local IPv6 Address . . . . . : fe80::xxxx:xxxx:xxxx:xxxx%15(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.119(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 29 May 2026 08:32:58
Lease Expires . . . . . . . . . . : 30 May 2026 08:32:56
Default Gateway . . . . . . . . . : fe80::xxxx:xxxx:xxxx:xxxx%15
192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 98620516
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-28-E8-80-E0-74-78-XX-XX-XX-XX
DNS Servers . . . . . . . . . . . : 2a00:23c8:xxxx:xxxx::1 192.168.0.1 2a00:23c8:xxxx:xxxx::1
NetBIOS over Tcpip. . . . . . . . : Disabled
TC-01 — A record query against IPv4 DNS server
Resolve-DnsName -Name "nonexistent.invalid.com" -Type A -Server 192.168.0.1
Result: Resolve-DnsName : nonexistent.invalid.com: DNS name does not exist
TC-02 — AAAA record query against IPv4 DNS server
Resolve-DnsName -Name "nonexistent.invalid.com" -Type AAAA -Server 192.168.0.1
Result: Resolve-DnsName : nonexistent.invalid.com : DNS name does not exist
TC-03 — A record query against IPv6 DNS server
Resolve-DnsName -Name "nonexistent.invalid.com" -Type A -Server 2a00:23c8:xxxx:xxxx::1
Resolve-DnsName : nonexistent.invalid.com : This operation returned because the timeout period expired
TC-04 — AAAA record query against IPv6 DNS server
Resolve-DnsName -Name "nonexistent.invalid.com" -Type AAAA -Server 2a00:23c8:xxxx:xxxx::1
Resolve-DnsName : nonexistent.invalid.com : This operation returned because the timeout period expired
TC-05 — A record query against Google IPv4 DNS server
Resolve-DnsName -Name "nonexistent.invalid.com" -Type A -Server 8.8.8.8
Resolve-DnsName : nonexistent.invalid.com : DNS name does not exist
TC-06 — AAAA record query against Google IPv6 DNS server
Resolve-DnsName -Name "nonexistent.invalid.com" -Type AAAA -Server 2001:4860:4860::8888
Resolve-DnsName : nonexistent.invalid.com : DNS name does not exist
Wireshark is showing the retransmission of the AAAA query to the IPV6 DNS server due to a lack of response. The windows DNS resolver eventually times out and terminates
I hope the information i've provided is enough to troubleshoot the issue and devlop a suitable fix.
[Mod edit: Personal device and network identifiers redacted from technical output]
