C:\Users\kitz>tracert loopsofzen.co.uk
Tracing route to loopsofzen.co.uk [2001:8b0:0:30::666:102]
over a maximum of 30 hops:
1 * * 66 ms 2001:1488:ffff::18
2 188 ms 144 ms 100 ms 2001:1488:ffff::ffff
3 177 ms 44 ms 47 ms 20ge1-3.core1.prg1.he.net [2001:7f8:14::6e:1]
4 188 ms 279 ms 94 ms 100ge8-1.core1.fra1.he.net [2001:470:0:213::1]
5 * 336 ms 61 ms 100ge6-1.core1.lon2.he.net [2001:470:0:37::1]
6 235 ms 108 ms 93 ms a.aimless.thn.aa.net.uk [2001:8b0:0:53::41]
7 139 ms 121 ms 73 ms a.needless.mh.aa.net.uk [2001:8b0:0:89a::1]
8 138 ms 108 ms 84 ms a.homeless.aa.net.uk [2001:8b0:0:30::51bb:1e02]
9 143 ms 71 ms 100 ms loopsofzen.uk [2001:8b0:0:30::666:102]
Trace complete.
racing route to homeless.aa.net.uk [81.187.30.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 14 ms 13 ms lo0.central10.pcn-bng01.plus.net [195.166.130.248]
3 15 ms 15 ms 14 ms 411.be5.pcn-ir02.plus.net [84.93.253.71]
4 15 ms 15 ms 14 ms 195.99.125.140
5 16 ms 15 ms 15 ms peer1-et-1-3-0.telehouse.ukcore.bt.net [195.99.127.19]
6 * * * Request timed out.
7 16 ms 16 ms 16 ms a.needless.tch.aa.net.uk [90.155.53.11]
8 17 ms 17 ms 17 ms router.mh.aa.net.uk [81.187.30.1]
So how are you accessing it then? You must be using some sort of tunnel.The only tunnel round here is the Channel one and don't think it's that ??? IPV6 is disabled here everywhere.
Domain name:
loopsofzen.co.uk
Registrant:
James Kennard
Registrant type:
UK Individual
Registrant's address:
The registrant is a non-trading individual who has opted to have their
address omitted from the WHOIS service.
Data validation:
Nominet was able to match the registrant's name and address against a 3rd party data source on 27-Sep-2016
Registrar:
Andrews & Arnold Limited [Tag = AAISP]
URL: http://www.aa.net.uk
Relevant dates:
Registered on: 10-Aug-2010
Expiry date: 10-Aug-2018
Last updated: 09-Aug-2016
Registration status:
Registered until expiry date.
Name servers:
primary-dns.co.uk 81.187.30.41 2001:8b0:0:30::51bb:1e29
secondary-dns.co.uk 81.187.81.32 2001:8b0:0:81::51bb:5120
WHOIS lookup made at 15:39:11 12-Nov-2016
[Duo2 ~]$ sudo traceroute -I loopsofzen.co.uk
connect: Network is unreachable
[Duo2 ~]$ sudo traceroute -T loopsofzen.co.uk
connect: Network is unreachable
[Duo2 ~]$ sudo traceroute -U loopsofzen.co.uk
traceroute to loopsofzen.co.uk (2001:8b0:0:30::666:102), 30 hops max, 80 byte packets
connect: Network is unreachable
[Duo2 ~]$ host 2001:8b0:0:30::666:102
2.0.1.0.6.6.6.0.0.0.0.0.0.0.0.0.0.3.0.0.0.0.0.0.0.b.8.0.1.0.0.2.ip6.arpa domain name pointer loopsofzen.uk.
2.0.1.0.6.6.6.0.0.0.0.0.0.0.0.0.0.3.0.0.0.0.0.0.0.b.8.0.1.0.0.2.ip6.arpa domain name pointer loopsofzen.co.uk.
[Duo2 ~]$
A host that has IPv4 connectivity to the Internet from behind a NAT and uses the Teredo tunneling protocol to access the IPv6 Internet. Teredo clients are assigned an IPv6 address that starts with the Teredo prefix (2001::/32
Your IPv4 address on the public Internet appears to be x.x.x.x
Your IPv6 address on the public Internet appears to be 2001:0:53aa:64c:2c65:1bc5:ccf9:cdb1
Your IPv6 service appears to be: Teredo
Your Internet Service Provider (ISP) appears to be PLUSNET UK Internet Service Provider, GB
Your IPv6 connection appears to be using Teredo, a type of IPv4/IPv6 gateway. Your particular teredo configuration is only used as a protocol of last resort. When visiting a site with both IPv4 and IPv6, IPv4 will be preferred.
Good news! Your current configuration will continue to work as web sites enable IPv6.
Your DNS server (possibly run by your ISP) appears to have IPv6 Internet access.
Your readiness score
7/10 for your IPv6 stability and readiness, when publishers are forced to go IPv6 only
C:\Users\John>ping loopsofzen.co.uk
Pinging loopsofzen.co.uk [2001:8b0:0:30::666:102] with 32 bytes of data:
Reply from 2001:8b0:0:30::666:102: time=10ms
Reply from 2001:8b0:0:30::666:102: time=10ms
Reply from 2001:8b0:0:30::666:102: time=10ms
Reply from 2001:8b0:0:30::666:102: time=10ms
Ping statistics for 2001:8b0:0:30::666:102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 10ms, Average = 10ms
eric@nuthatch:~$ ping loopsofzen.co.uk
ping: unknown host loopsofzen.co.uk
eric@nuthatch:~$ traceroute loopsofzen.co.uk
traceroute to loopsofzen.co.uk (2001:8b0:0:30::666:102), 30 hops max, 80 byte packets
1 2001:1488:ffff::18 (2001:1488:ffff::18) 357.455 ms 357.431 ms 357.428 ms
2 2001:1488:ffff::ffff (2001:1488:ffff::ffff) 357.758 ms 357.758 ms 357.765 ms
3 * * *
4 * * *
5 * * *
6 a.aimless.thn.aa.net.uk (2001:8b0:0:53::41) 391.397 ms 126.614 ms 126.608 ms
7 a.needless.mh.aa.net.uk (2001:8b0:0:89a::1) 263.226 ms 225.722 ms 225.681 ms
8 a.homeless.aa.net.uk (2001:8b0:0:30::51bb:1e02) 258.516 ms 258.495 ms 169.377 ms
9 loopsofzen.uk (2001:8b0:0:30::666:102) 153.088 ms 143.729 ms 143.737 ms
I'm using Google DNS, so there's some other cause.
For those who don't know, there's a site where you can get your IPv6 status tested: http://test-ipv6.com/ (http://test-ipv6.com/)
With miredo installed, it reports as follows for my connection:
1. I'm presuming people using a tunnel will see worse latency.
Oddly enough, I can't ping that site, . . .
eric@nuthatch:~$ ping6 loopsofzen.co.uk
PING loopsofzen.co.uk(loopsofzen.uk) 56 data bytes
64 bytes from loopsofzen.uk: icmp_seq=1 ttl=47 time=187 ms
64 bytes from loopsofzen.uk: icmp_seq=2 ttl=47 time=90.2 ms
64 bytes from loopsofzen.uk: icmp_seq=3 ttl=47 time=73.6 ms
64 bytes from loopsofzen.uk: icmp_seq=4 ttl=47 time=96.3 ms
64 bytes from loopsofzen.uk: icmp_seq=5 ttl=47 time=52.6 ms
64 bytes from loopsofzen.uk: icmp_seq=6 ttl=47 time=57.1 ms
64 bytes from loopsofzen.uk: icmp_seq=7 ttl=47 time=59.2 ms
^C
--- loopsofzen.co.uk ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6009ms
rtt min/avg/max/mdev = 52.655/88.110/187.393/43.401 ms
kitz your score is at odds with the summary, there is a sort of debug page you can click tho that shows the individual test results.
A bad dns server would not cause a 0/10 anyway as some of the tests make direct connections to ipv6 ips without dns lookups been carried out.
@Kitz, hurrican is a free IPV6tunnel broker/service, which I am just signing up to now, for a test, so this maybe how you are able to receive IPV6 perhaps,
It was suggested on another forum that this cold (and perahps should) be done in a router. Has anyone tried IPv6 tunnelling in a router?
Stuart