- Dec
- 39
- 0
I have IPv6-connectivety just fine. All these commands works:
c:\> ping.exe -6 ipv6.google.com
c:\> tracert.exe -6 ipv6.google.com
c:\> adig.exe @1.1.1.1 -t aaaa ipv6.google.com
c:\> dig.exe @1.1.1.1 -t aaaa ipv6.google.com -- gives 2a00:1450:400f:803::200e
(and BTW ipv6.google.com has no IPv4 address).
But the built-in DNS command; c:\>dns 1.1.1.1 ipv6.google.com hangs TCC real good.
To the extent I have to use ProcessExplorer to kill it.
Do the bundled IPWorks20.dll really do not support IPv6? Or is it another known issue WRT this?
c:\> ping.exe -6 ipv6.google.com
c:\> tracert.exe -6 ipv6.google.com
c:\> adig.exe @1.1.1.1 -t aaaa ipv6.google.com
c:\> dig.exe @1.1.1.1 -t aaaa ipv6.google.com -- gives 2a00:1450:400f:803::200e
(and BTW ipv6.google.com has no IPv4 address).
But the built-in DNS command; c:\>dns 1.1.1.1 ipv6.google.com hangs TCC real good.
To the extent I have to use ProcessExplorer to kill it.
Do the bundled IPWorks20.dll really do not support IPv6? Or is it another known issue WRT this?