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. 

[YorkshireMidge]

Just checked my hub and it seems to have updated itself and FW is now showing as r4.26.3-R-1923144-PROD-83002 but still seeing the same issue. 

[JimM11]

@YorkshireMidge It's worth doing the 5 minute power off reset to the EE Hub, then seeing what is going on when powered back up again from the fresh restart.

[YorkshireMidge · Accepted solution]

Issue resolved itself after a factory reset of the hub in connection with another fault I had (see  https://community.ee.co.uk/t5/Broadband-Landline/Migration-from-PlusNet-to-EE-CCTV-port-forwarding-i... ). 

I now see nslookups resolved without any timeouts and without having to specify the DNS service. 

[DougChandler]

I discovered the same issue today with the smart hub 6 plus supplied in the switch from plusnet. I have the same firmware which is the latest for this router.

A bit more digging and I have found that with IPv6 enabled, this router is advertising that it is a DNS server and windows preferring IPv6 over IPv4 attempts to connect to it to resolve addresses, just like your examples. The router however says IPv6 DNS is IPv4 only and appears not to be listening for IPv6 DNS so it times out.

I cannot believe that they have shipped the units like this with a partially implemented IPv6. My fix is to disable IPv6 and it works.

This needs to be reported as a bug.

[JimM11]

@DougChandler Although the Factory Reset is a rather drastic way to be doing it, have you tried as per the post, and seen if the iPv6 DNS server applied start's to play nice on your system.