This is the nslookup for the google dns IPv6 address

C:\Users\Reagan>tracert 2001:4860:4860::8888

Tracing route to google-public-dns-a.google.com [2001:4860:4860::8888]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

And here's one for the 8844 address

Tracing route to google-public-dns-b.google.com [2001:4860:4860::8844]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Also this is the page for IPv6 settings on my HH5


IPv6 Configuration

Hub IPv6 Gateway Address

Name: BThomehub.home
Global Unicast Address: Not available
Link Local Address: fe80::9272:82ff:fea1:6ac4
Global Unicast prefix / length: Not available

ULA

Enabled: Option Yes (Recommended) for ula is selectedYes (Recommended)


I've already had my DNS settings (LAN connection settings) for IPv4 and 6 set to the google ones for a long time, this problem kinda came out of nowhere.

Plus tracert's for 8.8.8.8 and 8.8.4.4

C:\Users\Reagan>tracert 8.8.4.4

Tracing route to google-public-dns-b.google.com [8.8.4.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BTHUB5 [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 7 ms 6 ms 7 ms 31.55.186.184
5 6 ms 6 ms 6 ms core4-hu0-16-0-1.faraday.ukcore.bt.net [195.99.1
27.204]
6 12 ms 7 ms 7 ms 213.121.193.195
7 7 ms 7 ms 6 ms 109.159.253.67
8 7 ms 7 ms 7 ms 108.170.246.129
9 8 ms 7 ms 7 ms 216.239.57.65
10 7 ms 7 ms 7 ms google-public-dns-b.google.com [8.8.4.4]

Trace complete.

C:\Users\Reagan>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms BTHUB5 [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 7 ms 6 ms 6 ms 31.55.186.176
5 7 ms 6 ms 6 ms core4-hu0-16-0-3.faraday.ukcore.bt.net [195.99.1
27.206]
6 8 ms 7 ms 7 ms peer1-hu0-10-0-0.slough.ukcore.bt.net [62.172.10
3.3]
7 7 ms 7 ms 7 ms peer5-te0-0-0-32.telehouse.ukcore.bt.net [195.99
.126.77]
8 8 ms 8 ms 7 ms 108.170.246.225
9 8 ms 8 ms 8 ms 216.239.58.91
10 8 ms 8 ms 8 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\Users\Reagan>

In reply to a post by Jwest90:

IPv6 Configuration

Hub IPv6 Gateway Address

Name: BThomehub.home
Global Unicast Address: Not available
Link Local Address: fe80::9272:82ff:fea1:6ac4
Global Unicast prefix / length: Not available

You have no globally routable IPv6 address for the Hub and no globally routable prefix for your LAN devices, so IPv6 will be totally non-functional. This lack of IPv6 may well be the root cause of your issues.

You could try a single reboot of the Hub to see if IPv6 returns, though I have heard others complain of flaky IPv6 via their Hub. As I'm not on BT, I don't know what to suggest beyond that. For the sake of stability, I suggest that you remove any IPv6 DNS servers from your configuration for now, as that will dramatically reduce if not totally eliminate DNS related timeouts.

I feel this is a classic case of faffing around causing issues.

Set DNS and IP to automatic. Set homehub to factory settings.

Let the OS decide whether IPv6 DNS is needed or not, in your case it should not be enabled.

BTs IPv6 is flakey at best.

Tried removing all IPv6 and that didn't help. Then reset everything to default and had it pick DNS automatically, which is now allowing tracert and nslookup to both IPv4 and 6. However the issues inconsistent browsing and high game latency are still there (on all my devices).

I'll give it a few days see if it stabilises.

Edited by deleted (Tue 11-Apr-17 20:45:32)