Migration from PlusNet to EE - nslookup timeout if server not specified

[YorkshireMidge]

Just been migrated from Plusnet to EE today, and everything went well but I just noticed something a bit odd when I came to do an nslookup from my desktop.  

Basically, if the DNS servers weren't specified, the request would time out and you can see the address that pops up in the first nslookup is the IPv6 global unicast address. 

The only difference I can see from my old PlusNet hub is IPv6 is disabled on that, and enabled on the EE one and it doesn't look like it can be changed. 

You can see in the second example, I stipulate the default BT DNS address 81.139.56.100 used by my hub, and it then works. Ditto, if I specify the Google DNS server 8.8.8.8. 

Hub is SH31B running r4.26.2-R-1923137-PROD-83002

Any ideas? Thanks. 

[JimM11]

@YorkshireMidge While your posted pics are being checked for general viewing can you double check your current FW that you have posted, here is what the latest others have posted....

FW: r4.26.3-R-1923144-PROD-83002 and the gui is at App version 3.14.5 12/06/2026 OP Posted

If your hub is just new OOB as today it may be the version you are quoting so still to FW update.

PN were only recently playing about getting iPv6 to work on there system EE has had it for years.

[XRaySpeX]

Don't worry, the images were awaiting approval. I have now done so & they should appear soon.

[JimM11]

@YorkshireMidge Just to keep them the same i repeated yours for you with the results below. There is nothing wrong with your values.

Microsoft Windows [Version 10.0.26200.8875]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>nslookup bbc.co.uk
Server: UnKnown
Address: 2a0a:ef40:1738:6400::1

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

C:\Windows\System32>nslookup bbc.co.uk 81.139.56.100
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 81.139.56.100

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

C:\Windows\System32>nslookup bbc.co.uk 8.8.8.8
Server: dns.google
Address: 8.8.8.8

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

[XRaySpeX]

1st & 2nd NSLOOKUP results are about reversed between you.

[JimM11]

@XRaySpeX Yes that would be correct, my router is already using the correct DNS resolver, and know idea what the IP the OP has posted if it is a DNS IP or the wan IP on the posting.

[YorkshireMidge]

That's correct Jim - this is straight out the box which arrived a few days back. Presumably there is no way to force a firmware update to the latest version.

[YorkshireMidge]

Thanks - hopefully my question will make more sense now!

[JimM11]

@YorkshireMidge You are correct there is no forcing or finding for an EE box, they do it all, and with the way that the FW updates have been going lately it's maybe a good reason yours has not been touched when first connected. Linked the pinned posting for you. The latest may or may not be just the 100% correct another experienced user trying to work out if it's the FW updated latest or the app with the issue or just both, but sure looking like FW currently my opinion only.....

EE Hub firmware versions - The EE Community

[YorkshireMidge]

OK thanks Jim - at least I can work around it which is the main thing.