topic Re: BT DNS Server Timeout for Non existing records causing slow logon times in Broadband & Landline

BT DNS Server Timeout for Non existing records causing slow logon times

blackops786187 — Fri, 29 May 2026 12:21:22 GMT

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]

Re: BT DNS Server Timeout for Non existing records causing slow logon times

JimM11 — Fri, 29 May 2026 12:41:30 GMT

@blackops786187 Are you both using the SAME EE Hubs on the same EE service connection?

https://ee.co.uk/help/broadband/getting-started/compare-our-range-of-broadband-hubs

Re: BT DNS Server Timeout for Non existing records causing slow logon times

blackops786187 — Fri, 29 May 2026 12:52:16 GMT

I am using the smart hub 6 plus on the same EE connection at home

Re: BT DNS Server Timeout for Non existing records causing slow logon times

JimM11 — Fri, 29 May 2026 12:56:26 GMT

@blackops786187 Was it all working before, EE have just pushed a new FW update to the 6 Plus hubs latest version now below.

FW: r3.8.24-R-1531355-PROD-83002 and the gui is at App version 3.1.3 10/10/2025 Now https://
FW: r3.8.29-R-1627298-PROD-83002 Op Posted
FW: r3.8.30-R-1627300-PROD-83002 and the gui is at App version 3.1.18 05/12/2025
FW: r4.26.1-R-1860948-PROD-83002 and the gui is at App version 3.14.5 25/05/2026 OP Posted

Re: BT DNS Server Timeout for Non existing records causing slow logon times

blackops786187 — Fri, 29 May 2026 13:01:30 GMT

yes it was working fine early in the week

Re: BT DNS Server Timeout for Non existing records causing slow logon times

JimM11 — Fri, 29 May 2026 13:06:08 GMT

@blackops786187 Can you take the look and see were the Hub is sitting with it all, did you change the IP scope range down on the EE Hub as i see you are getting assigned 0.1 from the DHCP on the EE Hub?

Re: BT DNS Server Timeout for Non existing records causing slow logon times

blackops786187 — Fri, 29 May 2026 13:15:45 GMT

yes ive changed the hubs dhcp range between 0.10 to 0.240 so its aligned with my access points which are on the 0.X range. The access points (3 in total are outside of the dhcp range 0.241, 0.242,0.243)

The tests ive conducted were done on my personal and work laptop which is connected directly to the EE smart hub removing anything else from the equation. No other changes to the ee hub have been made.

As i have mentioned above, i do have another team member who is also on EE (using an EE smart hub where he hasnt modified any settings) and hes also seeing the same problem

Re: BT DNS Server Timeout for Non existing records causing slow logon times

JimM11 — Fri, 29 May 2026 13:34:32 GMT

@blackops786187 Check were the FW is at on your hub, the versions are all up in your post earlier entry. That will let you know were it is at, just incase update is messing with your assigned wan IP's.

Test your IPv6.

Re: BT DNS Server Timeout for Non existing records causing slow logon times

blackops786187 — Fri, 29 May 2026 13:46:26 GMT

yep it matches the latest version

Re: BT DNS Server Timeout for Non existing records causing slow logon times

JimM11 — Fri, 29 May 2026 14:41:28 GMT

@blackops786187 Captured test....

IpV6 when working correct.

Re: BT DNS Server Timeout for Non existing records causing slow logon times

blackops786187 — Fri, 29 May 2026 14:43:04 GMT

@JimM11 - i cant see the image you posted

Re: BT DNS Server Timeout for Non existing records causing slow logon times

JimM11 — Fri, 29 May 2026 14:46:14 GMT

@blackops786187 Has to be cleared for general viewing, once checked and approved, you will see it soon.

Have you tried powering down the hub for 5 minutes since you just had the FW update?

Re: BT DNS Server Timeout for Non existing records causing slow logon times

JimM11 — Fri, 29 May 2026 15:11:26 GMT

@blackops786187 Have you tried giving EE CS a call?

Re: BT DNS Server Timeout for Non existing records causing slow logon times

blackops786187 — Fri, 29 May 2026 15:21:03 GMT

@JimM11

Tried a reboot to no avail.

Just realized that it’s not simply an issue with sending queries to the IPv6 DNS server where the domain doesn’t exist — it seems like the IPv6 DNS server isn’t responding to anything at all.

PS C:\Users\Home> nslookup - [REDACTED - IPV6 DNS Server]
DNS request timed out.
timeout was 2 seconds.
Default Server: UnKnown
Address: [REDACTED - IPV6 DNS Server]

> bbc.co.uk
Server: UnKnown
Address: [REDACTED - IPV6 DNS Server]

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
>
PS C:\Users\Home> nslookup - 192.168.0.1
Default Server: hub.home.arpa
Address: 192.168.0.1

> bbc.co.uk
Server: hub.home.arpa
Address: 192.168.0.1

Non-authoritative answer:
Name: bbc.co.uk
Addresses: 2a04:4e42:200::81
2a04:4e42:600::81
2a04:4e42::81
2a04:4e42:400::81
151.101.0.81
151.101.64.81
151.101.192.81
151.101.128.81

I’ll try a factory reset tomorrow morning and see if it comes back to life. If not, I’ll give EE customer support a call.

Re: BT DNS Server Timeout for Non existing records causing slow logon times

blackops786187 — Wed, 03 Jun 2026 09:58:22 GMT

Ok. It looks like a factory reset solved it. Thanks for the help