New Contributor
•
12 Messages
IPv6 Slows down the host resolve
Hello.
I've done some tests and noticed that whenever I have IPv6 enabled on my router, visiting websites slows down immensely. Direct connections through VOIP's seem fine. It just seems that whenever I use a web-browser, the internet takes a while to resolve a host. I suspect it's a DNS issue with IPv6 enabled. Because when I disable IPv6 (or use a 6to4 Tunnel) on the router, loading up webpages seem to go back to instantaneous speeds.
I use the Motorola SB6183 modem and a Netgear Nighthawk R7000 router. Intel NIC and Windows 7.
If you need any additional info, let me know.
I would like to have the delay when "Resolving Host" fixed.
when i do:
>nslookup google.com
it seems to timeout the initial DNS request.
Related Content
Closed
3
0
Closed
1
0
Closed
5
0
Closed
1
0
Closed
5
0
ChrisL
Former Moderator
•
7.1K Messages
I've actually seen another report of this with the same router. Can you try connecting an IPv6 PC directly to the modem and see if you get the same result?
0
0
MondayCS
New Contributor
•
12 Messages
Yes. Same results with the modem directly connected to the PC. Both on a Windows 7 desktop and a Windows 10 Laptop
0
0
ChrisL
Former Moderator
•
7.1K Messages
If it's happening without the router there may be something else going on then. Can you post your ipconfig /all with the PC connected directly to the modem?
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
::double post::
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
Yea, I think its something with Cox IPv6 DNS. I bet it goes away when you use Google IPv6 as static DNS.
The Google Public DNS IPv6 addresses are as follows:
0
0
MondayCS
New Contributor
•
12 Messages
Here is the ipconfig /all with the PC directly connected to the modem:
Windows IP Configuration
Host Name . . . . . . . . . . . . : ANt-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I218-V
Physical Address. . . . . . . . . : 38-2C-4A-BB-13-DA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2600:8801:ff04:800:19d0:39ca:fba3:76d3(Pr
eferred)
Lease Obtained. . . . . . . . . . : Thursday, November 19, 2015 10:11:00 AM
Lease Expires . . . . . . . . . . : Friday, November 20, 2015 10:10:59 AM
Link-local IPv6 Address . . . . . : fe80::45e6:a83d:32f6:570b%11(Preferred)
IPv4 Address. . . . . . . . . . . : 68.7.193.73(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Lease Obtained. . . . . . . . . . : Thursday, November 19, 2015 10:10:57 AM
Lease Expires . . . . . . . . . . : Friday, November 20, 2015 10:10:56 AM
Default Gateway . . . . . . . . . : fe80::226:99ff:fe89:ced9%11
68.7.192.1
DHCP Server . . . . . . . . . . . : 172.19.97.117
DHCPv6 IAID . . . . . . . . . . . : 238562378
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-92-ED-84-38-2C-4A-BB-13-DA
DNS Servers . . . . . . . . . . . : 2001:578:3f::30
2001:578:3f:1::30
2001:578:3f::30
2001:578:3f:1::30
68.105.28.11
68.105.29.11
68.105.28.12
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{661D69E9-173A-4BDA-9A05-8D4A3BFE2A29}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5cf2:8c02:3083:3c35:bbf8:3eb6(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::3083:3c35:bbf8:3eb6%13(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
0
0
ChrisL
Former Moderator
•
7.1K Messages
One thing I see there is that IPv4 is the preferred connection and it's not showing a correct default gateway address. I suspect that could be part of what is going on here.
0
0
MondayCS
New Contributor
•
12 Messages
So how would I fix this?
0
0
ChrisL
Former Moderator
•
7.1K Messages
Unfortunately I don't have an IPv6 setup available to me to test with. Some of our peers here may have seen this before and have some suggestions. The Microsoft support site may also have some useful info relating to dual-stack setup.
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
If DHCPv6 is in use, how is there any user configuration to change? If it's effecting both a PC and a router, wouldn't the common theme be Cox's IPv6? I have a feeling this will be a more and more common issue that Cox will deny until they absolutely have to. My guess is the priority Cox is is putting on IPv6 queries for AAAA compard to A.
One thing I would suggest is try disabling IPv4 on the PC and JUST use IPv6 and see if you still have a issue.
0
0