From ek at google.com  Mon Nov  2 22:50:42 2009
From: ek at google.com (Erik Kline)
Date: Mon, 2 Nov 2009 13:50:42 -0800
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <4AE6E6EA.6050309@airwire.ie>
References: <4AE6D99C.5090307@linpro.no> <4AE6DA94.1090002@airwire.ie>
	<4AE6DB40.7000301@linpro.no> <4AE6DD87.1000207@airwire.ie>
	<4AE6E130.6000304@linpro.no> <4AE6E2D9.8040203@airwire.ie>
	<4AE6E33B.6060702@airwire.ie> <20091027121555.GA3204@boris.ghen.be>
	<4AE6E6EA.6050309@airwire.ie>
Message-ID: <2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>

2009/10/27 Martin List-Petersen <martin at airwire.ie>:
> Geert Hendrickx wrote:
>> On Tue, Oct 27, 2009 at 12:10:35PM +0000, Martin List-Petersen wrote:
>>> Martin List-Petersen wrote:
>>>> I wouldn't encourage that, but if your eyeball networks are that
>>>> paranoid, that's a way, how they can be in control. They could then
>>>> choose not to provide AAAA records to 6to4- and teredo- clients.
>>>>
>>>> Anyhow .. that's a hack and not to be encouraged, really.
>>> Arghh .. me not thinking today. Obviously they can't know, what the
>>> client has, but they could whitelist known good deployments then.
>>
>>
>> Or, on your side, you could not serve AAAA records to (the DNS chaches of)
>> the problematic network(s)?
>
> That is the better approach alright.

Until the IPv6 Internet gets less sucky it's the pretty much the only
approach we've been able to come up with.

From martin at airwire.ie  Mon Nov  2 23:08:01 2009
From: martin at airwire.ie (Martin List-Petersen)
Date: Mon, 02 Nov 2009 22:08:01 +0000
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>
References: <4AE6D99C.5090307@linpro.no> <4AE6DA94.1090002@airwire.ie>	
	<4AE6DB40.7000301@linpro.no> <4AE6DD87.1000207@airwire.ie>	
	<4AE6E130.6000304@linpro.no> <4AE6E2D9.8040203@airwire.ie>	
	<4AE6E33B.6060702@airwire.ie>
	<20091027121555.GA3204@boris.ghen.be>	
	<4AE6E6EA.6050309@airwire.ie>
	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>
Message-ID: <4AEF5841.8020502@airwire.ie>

Erik Kline wrote:
> 2009/10/27 Martin List-Petersen <martin at airwire.ie>:
>> Geert Hendrickx wrote:
>>> On Tue, Oct 27, 2009 at 12:10:35PM +0000, Martin List-Petersen wrote:
>>> Or, on your side, you could not serve AAAA records to (the DNS chaches of)
>>> the problematic network(s)?
>> That is the better approach alright.
> 
> Until the IPv6 Internet gets less sucky it's the pretty much the only
> approach we've been able to come up with.

Hi Eric.

No, you don't serve to anybody but who's on your whitelist.

The last approach here was to serve to everybody and blacklist networks
that suck.

I prefer the latter, but I do understand the approach. Some networks do
need the quality.

Kind regards,
Martin List-Petersen
-- 
Airwire - Ag Nascadh Pobail an Iarthair
http://www.airwire.ie
Phone: 091-865 968

From ek at google.com  Mon Nov  2 23:16:44 2009
From: ek at google.com (Erik Kline)
Date: Mon, 2 Nov 2009 14:16:44 -0800
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <4AEF5841.8020502@airwire.ie>
References: <4AE6D99C.5090307@linpro.no> <4AE6DB40.7000301@linpro.no>
	<4AE6DD87.1000207@airwire.ie> <4AE6E130.6000304@linpro.no>
	<4AE6E2D9.8040203@airwire.ie> <4AE6E33B.6060702@airwire.ie>
	<20091027121555.GA3204@boris.ghen.be> <4AE6E6EA.6050309@airwire.ie>
	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>
	<4AEF5841.8020502@airwire.ie>
Message-ID: <2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>

2009/11/2 Martin List-Petersen <martin at airwire.ie>:
> Erik Kline wrote:
>> 2009/10/27 Martin List-Petersen <martin at airwire.ie>:
>>> Geert Hendrickx wrote:
>>>> On Tue, Oct 27, 2009 at 12:10:35PM +0000, Martin List-Petersen wrote:
>>>> Or, on your side, you could not serve AAAA records to (the DNS chaches of)
>>>> the problematic network(s)?
>>> That is the better approach alright.
>>
>> Until the IPv6 Internet gets less sucky it's the pretty much the only
>> approach we've been able to come up with.
>
> Hi Eric.
>
> No, you don't serve to anybody but who's on your whitelist.
>
> The last approach here was to serve to everybody and blacklist networks
> that suck.
>
> I prefer the latter, but I do understand the approach. Some networks do
> need the quality.
>
> Kind regards,
> Martin List-Petersen
> --
> Airwire - Ag Nascadh Pobail an Iarthair
> http://www.airwire.ie
> Phone: 091-865 968
>

Right.  I meant the not-serving-to-problem-networks part.  We just
assume that all networks could have problems, unless otherwise
explicitly stated.  =)

From paul at timmins.net  Tue Nov  3 00:19:02 2009
From: paul at timmins.net (Paul Timmins)
Date: Mon, 02 Nov 2009 18:19:02 -0500
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>
References: <4AE6D99C.5090307@linpro.no>
	<4AE6DB40.7000301@linpro.no>	<4AE6DD87.1000207@airwire.ie>
	<4AE6E130.6000304@linpro.no>	<4AE6E2D9.8040203@airwire.ie>
	<4AE6E33B.6060702@airwire.ie>	<20091027121555.GA3204@boris.ghen.be>
	<4AE6E6EA.6050309@airwire.ie>	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>	<4AEF5841.8020502@airwire.ie>
	<2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>
Message-ID: <4AEF68E6.1000109@timmins.net>

Erik Kline wrote:
> 2009/11/2 Martin List-Petersen <martin at airwire.ie>:
>   
>> Erik Kline wrote:
>>     
>>> 2009/10/27 Martin List-Petersen <martin at airwire.ie>:
>>>       
>>>> Geert Hendrickx wrote:
>>>>         
>>>>> On Tue, Oct 27, 2009 at 12:10:35PM +0000, Martin List-Petersen wrote:
>>>>> Or, on your side, you could not serve AAAA records to (the DNS chaches of)
>>>>> the problematic network(s)?
>>>>>           
>>>> That is the better approach alright.
>>>>         
>>> Until the IPv6 Internet gets less sucky it's the pretty much the only
>>> approach we've been able to come up with.
>>>       
>> Hi Eric.
>>
>> No, you don't serve to anybody but who's on your whitelist.
>>
>> The last approach here was to serve to everybody and blacklist networks
>> that suck.
>>
>> I prefer the latter, but I do understand the approach. Some networks do
>> need the quality.
>>
>> Kind regards,
>> Martin List-Petersen
>> --
>> Airwire - Ag Nascadh Pobail an Iarthair
>> http://www.airwire.ie
>> Phone: 091-865 968
>>
>>     
>
> Right.  I meant the not-serving-to-problem-networks part.  We just
> assume that all networks could have problems, unless otherwise
> explicitly stated.  =)
>   
Is there a way to get on the approved list without a bunch of peering?

From ek at google.com  Tue Nov  3 00:25:39 2009
From: ek at google.com (Erik Kline)
Date: Mon, 2 Nov 2009 15:25:39 -0800
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <4AEF68E6.1000109@timmins.net>
References: <4AE6D99C.5090307@linpro.no> <4AE6E130.6000304@linpro.no>
	<4AE6E2D9.8040203@airwire.ie> <4AE6E33B.6060702@airwire.ie>
	<20091027121555.GA3204@boris.ghen.be> <4AE6E6EA.6050309@airwire.ie>
	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>
	<4AEF5841.8020502@airwire.ie>
	<2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>
	<4AEF68E6.1000109@timmins.net>
Message-ID: <2e8c64260911021525u409f9d9bl378f65d390bb92ba@mail.gmail.com>

>> Right. ?I meant the not-serving-to-problem-networks part. ?We just
>> assume that all networks could have problems, unless otherwise
>> explicitly stated. ?=)
>>
>
> Is there a way to get on the approved list without a bunch of peering?

If we see you behind 2 or more networks with whom we have good
connectivity that's usually good enough (though I'm not the final
arbiter in the matter).

We're still in the process of rolling out IPv6 to all geographic
regions, so sometimes that's the bigger blocker (like if we perform
maintenance on the datacenter nearest you and the next closest is
half-way around the world then that's a problem, regardless of how
well we're connected to one another).

From chaz at chaz6.com  Tue Nov  3 13:34:44 2009
From: chaz at chaz6.com (Chris Hills)
Date: Tue, 03 Nov 2009 13:34:44 +0100
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <2e8c64260911021525u409f9d9bl378f65d390bb92ba@mail.gmail.com>
References: <4AE6D99C.5090307@linpro.no>
	<4AE6E130.6000304@linpro.no>	<4AE6E2D9.8040203@airwire.ie>
	<4AE6E33B.6060702@airwire.ie>	<20091027121555.GA3204@boris.ghen.be>
	<4AE6E6EA.6050309@airwire.ie>	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>	<4AEF5841.8020502@airwire.ie>	<2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>	<4AEF68E6.1000109@timmins.net>
	<2e8c64260911021525u409f9d9bl378f65d390bb92ba@mail.gmail.com>
Message-ID: <hcp814$ogn$1@ger.gmane.org>

On 03/11/09 00:25, Erik Kline wrote:
> If we see you behind 2 or more networks with whom we have good
> connectivity that's usually good enough (though I'm not the final
> arbiter in the matter).
>
> We're still in the process of rolling out IPv6 to all geographic
> regions, so sometimes that's the bigger blocker (like if we perform
> maintenance on the datacenter nearest you and the next closest is
> half-way around the world then that's a problem, regardless of how
> well we're connected to one another).

Please consider setting up an alternate domain (for example google6.com) 
which has IPv6 DNS glue. At present it is impossible to directly access 
google from an IPv6-only network.



From martin at airwire.ie  Tue Nov  3 14:07:28 2009
From: martin at airwire.ie (Martin List-Petersen)
Date: Tue, 03 Nov 2009 13:07:28 +0000
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <hcp814$ogn$1@ger.gmane.org>
References: <4AE6D99C.5090307@linpro.no>	<4AE6E130.6000304@linpro.no>	<4AE6E2D9.8040203@airwire.ie>	<4AE6E33B.6060702@airwire.ie>	<20091027121555.GA3204@boris.ghen.be>	<4AE6E6EA.6050309@airwire.ie>	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>	<4AEF5841.8020502@airwire.ie>	<2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>	<4AEF68E6.1000109@timmins.net>	<2e8c64260911021525u409f9d9bl378f65d390bb92ba@mail.gmail.com>
	<hcp814$ogn$1@ger.gmane.org>
Message-ID: <4AF02B10.9090105@airwire.ie>

Chris Hills wrote:
> On 03/11/09 00:25, Erik Kline wrote:
>> If we see you behind 2 or more networks with whom we have good
>> connectivity that's usually good enough (though I'm not the final
>> arbiter in the matter).
>>
>> We're still in the process of rolling out IPv6 to all geographic
>> regions, so sometimes that's the bigger blocker (like if we perform
>> maintenance on the datacenter nearest you and the next closest is
>> half-way around the world then that's a problem, regardless of how
>> well we're connected to one another).
> 
> Please consider setting up an alternate domain (for example google6.com)
> which has IPv6 DNS glue. At present it is impossible to directly access
> google from an IPv6-only network.
> 

Google has done that. It's ipv6.google.com.

And there is no problem accessing Google from an IPv6 only network, if
your network is whitelisted. Contact Google to get it whitelisted. I use
Google every day from a IPv6 only box.

Services that don't work on IPv6 aren't available to IPv6 yet.

Kind regards,
Martin List-Petersen
-- 
Airwire - Ag Nascadh Pobail an Iarthair
http://www.airwire.ie
Phone: 091-865 968

From chaz at chaz6.com  Tue Nov  3 14:12:02 2009
From: chaz at chaz6.com (Chris Hills)
Date: Tue, 03 Nov 2009 14:12:02 +0100
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <4AF02B10.9090105@airwire.ie>
References: <4AE6D99C.5090307@linpro.no>	<4AE6E130.6000304@linpro.no>	<4AE6E2D9.8040203@airwire.ie>	<4AE6E33B.6060702@airwire.ie>	<20091027121555.GA3204@boris.ghen.be>	<4AE6E6EA.6050309@airwire.ie>	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>	<4AEF5841.8020502@airwire.ie>	<2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>	<4AEF68E6.1000109@timmins.net>	<2e8c64260911021525u409f9d9bl378f65d390bb92ba@mail.gmail.com>	<hcp814$ogn$1@ger.gmane.org>
	<4AF02B10.9090105@airwire.ie>
Message-ID: <4AF02C22.4030301@chaz6.com>

On 03/11/09 14:07, Martin List-Petersen wrote:
 > Google has done that. It's ipv6.google.com.
 >
 > And there is no problem accessing Google from an IPv6 only network, if
 > your network is whitelisted. Contact Google to get it whitelisted. I use
 > Google every day from a IPv6 only box.
 >
 > Services that don't work on IPv6 aren't available to IPv6 yet.

This is /not/ accessible from an IPv6-only network. The google 
nameservers are only v4-connected.

$ dig -6 +trace ipv6.google.com. in aaaa

; <<>> DiG 9.6.1-P1 <<>> -6 +trace ipv6.google.com. in aaaa
;; global options: +cmd
.                       112691  IN      NS      M.ROOT-SERVERS.NET.
.                       112691  IN      NS      L.ROOT-SERVERS.NET.
.                       112691  IN      NS      J.ROOT-SERVERS.NET.
.                       112691  IN      NS      B.ROOT-SERVERS.NET.
.                       112691  IN      NS      E.ROOT-SERVERS.NET.
.                       112691  IN      NS      C.ROOT-SERVERS.NET.
.                       112691  IN      NS      H.ROOT-SERVERS.NET.
.                       112691  IN      NS      D.ROOT-SERVERS.NET.
.                       112691  IN      NS      I.ROOT-SERVERS.NET.
.                       112691  IN      NS      G.ROOT-SERVERS.NET.
.                       112691  IN      NS      A.ROOT-SERVERS.NET.
.                       112691  IN      NS      F.ROOT-SERVERS.NET.
.                       112691  IN      NS      K.ROOT-SERVERS.NET.
;; Received 332 bytes from ::1#53(::1) in 2 ms

com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      k.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      m.gtld-servers.net.
;; Received 496 bytes from 2001:7fd::1#53(K.ROOT-SERVERS.NET) in 51 ms

google.com.             172800  IN      NS      ns1.google.com.
google.com.             172800  IN      NS      ns2.google.com.
google.com.             172800  IN      NS      ns3.google.com.
google.com.             172800  IN      NS      ns4.google.com.
;; Received 169 bytes from 2001:503:a83e::2:30#53(a.gtld-servers.net) in 
240 ms

;; connection timed out; no servers could be reached



From martin at airwire.ie  Tue Nov  3 14:18:54 2009
From: martin at airwire.ie (Martin List-Petersen)
Date: Tue, 03 Nov 2009 13:18:54 +0000
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <4AF02C22.4030301@chaz6.com>
References: <4AE6D99C.5090307@linpro.no>	<4AE6E130.6000304@linpro.no>	<4AE6E2D9.8040203@airwire.ie>	<4AE6E33B.6060702@airwire.ie>	<20091027121555.GA3204@boris.ghen.be>	<4AE6E6EA.6050309@airwire.ie>	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>	<4AEF5841.8020502@airwire.ie>	<2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>	<4AEF68E6.1000109@timmins.net>	<2e8c64260911021525u409f9d9bl378f65d390bb92ba@mail.gmail.com>	<hcp814$ogn$1@ger.gmane.org>
	<4AF02B10.9090105@airwire.ie> <4AF02C22.4030301@chaz6.com>
Message-ID: <4AF02DBE.6010902@airwire.ie>

Chris Hills wrote:
> On 03/11/09 14:07, Martin List-Petersen wrote:
>> Google has done that. It's ipv6.google.com.
>>
>> And there is no problem accessing Google from an IPv6 only network, if
>> your network is whitelisted. Contact Google to get it whitelisted. I use
>> Google every day from a IPv6 only box.
>>
>> Services that don't work on IPv6 aren't available to IPv6 yet.
> 
> This is /not/ accessible from an IPv6-only network. The google
> nameservers are only v4-connected.
> 
> $ dig -6 +trace ipv6.google.com. in aaaa

Different issue. The nameservers should either be made available via
IPv6 or your nameserver needs IPv4 connectivity.

marlow at sleipner:~$ dig -6 www.google.com aaaa

; <<>> DiG 9.4.1 <<>> -6 www.google.com aaaa
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2426
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com.                        IN      AAAA

;; ANSWER SECTION:
www.google.com.         80776   IN      CNAME   www.l.google.com.
www.l.google.com.       204     IN      AAAA    2001:4860:a005::68

;; Query time: 42 msec
;; SERVER: 2a02:278:50::1#53(2a02:278:50::1)
;; WHEN: Tue Nov  3 13:15:51 2009
;; MSG SIZE  rcvd: 80

Creating another domain for that cause is the wrong approach.

Kind regards,
Martin List-Petersen
-- 
Airwire - Ag Nascadh Pobail an Iarthair
http://www.airwire.ie
Phone: 091-865 968

From chaz at chaz6.com  Tue Nov  3 14:26:18 2009
From: chaz at chaz6.com (Chris Hills)
Date: Tue, 03 Nov 2009 14:26:18 +0100
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <4AF02DBE.6010902@airwire.ie>
References: <4AE6D99C.5090307@linpro.no>	<4AE6E130.6000304@linpro.no>	<4AE6E2D9.8040203@airwire.ie>	<4AE6E33B.6060702@airwire.ie>	<20091027121555.GA3204@boris.ghen.be>	<4AE6E6EA.6050309@airwire.ie>	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>	<4AEF5841.8020502@airwire.ie>	<2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>	<4AEF68E6.1000109@timmins.net>	<2e8c64260911021525u409f9d9bl378f65d390bb92ba@mail.gmail.com>	<hcp814$ogn$1@ger.gmane.org>	<4AF02B10.9090105@airwire.ie>
	<4AF02C22.4030301@chaz6.com> <4AF02DBE.6010902@airwire.ie>
Message-ID: <4AF02F7A.4070105@chaz6.com>

On 03/11/09 14:18, Martin List-Petersen wrote:
> Different issue. The nameservers should either be made available via
> IPv6 or your nameserver needs IPv4 connectivity.
 >
 > [..]
 >
> Creating another domain for that cause is the wrong approach.

I would of course prefer that they IPv6-enabled one or more of their 
primary DNS servers, but given they are taking a whitelisting approach 
for serving AAAA for www/mail/etc that seems unlikely to happen in the 
near future.


From gert at space.net  Tue Nov  3 15:12:17 2009
From: gert at space.net (Gert Doering)
Date: Tue, 3 Nov 2009 15:12:17 +0100
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <4AF02B10.9090105@airwire.ie>
References: <4AE6E33B.6060702@airwire.ie> <20091027121555.GA3204@boris.ghen.be>
	<4AE6E6EA.6050309@airwire.ie>
	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>
	<4AEF5841.8020502@airwire.ie>
	<2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>
	<4AEF68E6.1000109@timmins.net>
	<2e8c64260911021525u409f9d9bl378f65d390bb92ba@mail.gmail.com>
	<hcp814$ogn$1@ger.gmane.org> <4AF02B10.9090105@airwire.ie>
Message-ID: <20091103141217.GF32226@Space.Net>

Hi,

On Tue, Nov 03, 2009 at 01:07:28PM +0000, Martin List-Petersen wrote:
> Google has done that. It's ipv6.google.com.
> 
> And there is no problem accessing Google from an IPv6 only network, if
> your network is whitelisted. Contact Google to get it whitelisted. I use
> Google every day from a IPv6 only box.

There is no way to resolve www.google.com from an *IPv6 only* network,
as the white-listing part only relates to the records returned for "www",
not to the DNS chain.

$ dig www.google.com aaaa
www.google.com.		16h24m58s IN CNAME  www.l.google.com.
www.l.google.com.	2m32s IN AAAA	2001:4860:a003::68

$ dig google.com ns
;; ANSWER SECTION:
google.com.		1d7h32m35s IN NS  ns4.google.com.
google.com.		1d7h32m35s IN NS  ns2.google.com.
google.com.		1d7h32m35s IN NS  ns3.google.com.
google.com.		1d7h32m35s IN NS  ns1.google.com.

;; ADDITIONAL SECTION:
ns3.google.com.		3d16h25m43s IN A  216.239.36.10
ns1.google.com.		1d23h52m27s IN A  216.239.32.10
ns2.google.com.		1d23h52m27s IN A  216.239.34.10
ns4.google.com.		1d23h52m27s IN A  216.239.38.10


(And yes, I know that this is a hard problem to change, and that a
fully IPv6-only network that doesn't have a v4 fallback DNS won't go
very far today - but this is one of the steps that eventually need to
be done as well)

Gert Doering
        -- NetMaster
-- 
Total number of prefixes smaller than registry allocations:  144438

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

From ek at google.com  Tue Nov  3 19:20:29 2009
From: ek at google.com (Erik Kline)
Date: Tue, 3 Nov 2009 10:20:29 -0800
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <20091103141217.GF32226@Space.Net>
References: <4AE6E33B.6060702@airwire.ie> <4AE6E6EA.6050309@airwire.ie>
	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>
	<4AEF5841.8020502@airwire.ie>
	<2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>
	<4AEF68E6.1000109@timmins.net>
	<2e8c64260911021525u409f9d9bl378f65d390bb92ba@mail.gmail.com>
	<hcp814$ogn$1@ger.gmane.org> <4AF02B10.9090105@airwire.ie>
	<20091103141217.GF32226@Space.Net>
Message-ID: <2e8c64260911031020r4a945973o75ef9b8cc13d48@mail.gmail.com>

2009/11/3 Gert Doering <gert at space.net>:
> Hi,
>
> On Tue, Nov 03, 2009 at 01:07:28PM +0000, Martin List-Petersen wrote:
>> Google has done that. It's ipv6.google.com.
>>
>> And there is no problem accessing Google from an IPv6 only network, if
>> your network is whitelisted. Contact Google to get it whitelisted. I use
>> Google every day from a IPv6 only box.
>
> There is no way to resolve www.google.com from an *IPv6 only* network,
> as the white-listing part only relates to the records returned for "www",
> not to the DNS chain.

Yes, IPv6 DNS glue is on the TODO list, as is youtube, jabber, and
SIP(!).  The work is far from over...

From tore at linpro.no  Wed Nov  4 13:31:14 2009
From: tore at linpro.no (Tore Anderson)
Date: Wed, 04 Nov 2009 13:31:14 +0100
Subject: Norwegian IPv6 brokenness experiment, October results
Message-ID: <4AF17412.4050704@linpro.no>

Hi list,

I mentioned about a week ago that I was conducting an experiment here in
Norway, trying to figure out more about any eventual breakage that would
be caused by dualstacking web sites.  This generated quite a few
off-list messages from people wanting more information, so I thought
that I'd rather just post the October results here instead so that
anyone interested can take a look.  Feedback or questions are of course
very welcome.

The test was done with the help of my customer A-Pressen Interaktiv
(http://www.api.no), which is the publisher of about 55 online
newspapers (Norwegian-language and mostly regional).  The readers are
not particularly techical or anything like that.  The site is in the
Norwegian top five (when adding all the publications together).

API have added an IFRAME tag in their HTML templates for most of their
pages, which includes a linkgen.php script on my test server (loaded
from a IPv4-only hostname).  This scripts spits out two IMG tags both
pointing to a 1x1 pixel large PNG, one loaded from a dualstacked
hostname, and the other from an ipv4-only hostname.  The ordering of
these tags is random.  In addition, both of the URLs pointing to the
PNGs include an ID which is generated randomly each time the linkgen
script runs.

All the traffic is going to the same test server, but all the hostnames
are pointing to different IP addresses and the TTL is only five seconds
(in order to prevent any bias introduced by caching).

The executive summary:
- On the dualstack host 0.153% of all hits are lost
- IPv6 penetration (preference over IPv4) is at 0.334%

The Opera web browser (coupled with Windows Vista or newer, which
automatically configure Teredo and 6to4) is causing most of the
problems, because it unconditionally prefers IPv6 over IPv4.  If I
simply exclude all log lines which contains "Opera" in the user-agent
field, I get the following executive summary instead:

- On the dualstack host 0.023% of all hits are lost
- IPv6 penetration (preference over IPv4) is at 0.134%

I've submitted Opera bug DSK-269385 about this issue, but have yet to
receive any reply.  If anyone has any contacts in Opera they can poke,
that would be greatly appreciated.  I doubt I'd be able to convince API
(or any other of my customers) to dualstack their production web sites
until Opera have released a fixed version.

I've attached two tables with numbers, one excluding all hits from Opera
browsers.  A few things to note:

- I've been running a 6to4 relay on the test server
- Data from the 11th, 15th, and 20th are removed (apparently outliers)
- The 11th I started announcing 192.88.99.0/24 to my peers on NIX
- The 28th I implemented a split-horizon DNS scheme that masked the
  AAAA records for the dualstack host from two eyeball networks known to
  filter 6to4 (thanks to Geert Hendrickx for that suggestion)

Many thanks to API for allowing me to experiment with their users and
for letting me post the results, and to Steinar H. Gunderson of Google
for helping me out tremendously along the way.

Regards,
-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/
Tel: +47 21 54 41 27
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 200910.txt
Url: http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20091104/87ce7c0c/attachment.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 200910-noopera.txt
Url: http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20091104/87ce7c0c/attachment-0001.txt 

From chaz at chaz6.com  Tue Nov  3 14:12:02 2009
From: chaz at chaz6.com (Chris Hills)
Date: Tue, 03 Nov 2009 14:12:02 +0100
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <4AF02B10.9090105@airwire.ie>
References: <4AE6D99C.5090307@linpro.no>	<4AE6E130.6000304@linpro.no>	<4AE6E2D9.8040203@airwire.ie>	<4AE6E33B.6060702@airwire.ie>	<20091027121555.GA3204@boris.ghen.be>	<4AE6E6EA.6050309@airwire.ie>	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>	<4AEF5841.8020502@airwire.ie>	<2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>	<4AEF68E6.1000109@timmins.net>	<2e8c64260911021525u409f9d9bl378f65d390bb92ba@mail.gmail.com>	<hcp814$ogn$1@ger.gmane.org>
	<4AF02B10.9090105@airwire.ie>
Message-ID: <4AF02C22.4030301@chaz6.com>

On 03/11/09 14:07, Martin List-Petersen wrote:
 > Google has done that. It's ipv6.google.com.
 >
 > And there is no problem accessing Google from an IPv6 only network, if
 > your network is whitelisted. Contact Google to get it whitelisted. I use
 > Google every day from a IPv6 only box.
 >
 > Services that don't work on IPv6 aren't available to IPv6 yet.

This is /not/ accessible from an IPv6-only network. The google 
nameservers are only v4-connected.

$ dig -6 +trace ipv6.google.com. in aaaa

; <<>> DiG 9.6.1-P1 <<>> -6 +trace ipv6.google.com. in aaaa
;; global options: +cmd
.                       112691  IN      NS      M.ROOT-SERVERS.NET.
.                       112691  IN      NS      L.ROOT-SERVERS.NET.
.                       112691  IN      NS      J.ROOT-SERVERS.NET.
.                       112691  IN      NS      B.ROOT-SERVERS.NET.
.                       112691  IN      NS      E.ROOT-SERVERS.NET.
.                       112691  IN      NS      C.ROOT-SERVERS.NET.
.                       112691  IN      NS      H.ROOT-SERVERS.NET.
.                       112691  IN      NS      D.ROOT-SERVERS.NET.
.                       112691  IN      NS      I.ROOT-SERVERS.NET.
.                       112691  IN      NS      G.ROOT-SERVERS.NET.
.                       112691  IN      NS      A.ROOT-SERVERS.NET.
.                       112691  IN      NS      F.ROOT-SERVERS.NET.
.                       112691  IN      NS      K.ROOT-SERVERS.NET.
;; Received 332 bytes from ::1#53(::1) in 2 ms

com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      k.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      m.gtld-servers.net.
;; Received 496 bytes from 2001:7fd::1#53(K.ROOT-SERVERS.NET) in 51 ms

google.com.             172800  IN      NS      ns1.google.com.
google.com.             172800  IN      NS      ns2.google.com.
google.com.             172800  IN      NS      ns3.google.com.
google.com.             172800  IN      NS      ns4.google.com.
;; Received 169 bytes from 2001:503:a83e::2:30#53(a.gtld-servers.net) in 
240 ms

;; connection timed out; no servers could be reached


From chaz at chaz6.com  Tue Nov  3 14:26:18 2009
From: chaz at chaz6.com (Chris Hills)
Date: Tue, 03 Nov 2009 14:26:18 +0100
Subject: Dealing with filtered 6to4 clients
In-Reply-To: <4AF02DBE.6010902@airwire.ie>
References: <4AE6D99C.5090307@linpro.no>	<4AE6E130.6000304@linpro.no>	<4AE6E2D9.8040203@airwire.ie>	<4AE6E33B.6060702@airwire.ie>	<20091027121555.GA3204@boris.ghen.be>	<4AE6E6EA.6050309@airwire.ie>	<2e8c64260911021350u603d044chf83a8fdc8b43be6f@mail.gmail.com>	<4AEF5841.8020502@airwire.ie>	<2e8c64260911021416l30e9928dyb9a99dfe56c55fc5@mail.gmail.com>	<4AEF68E6.1000109@timmins.net>	<2e8c64260911021525u409f9d9bl378f65d390bb92ba@mail.gmail.com>	<hcp814$ogn$1@ger.gmane.org>	<4AF02B10.9090105@airwire.ie>
	<4AF02C22.4030301@chaz6.com> <4AF02DBE.6010902@airwire.ie>
Message-ID: <4AF02F7A.4070105@chaz6.com>

On 03/11/09 14:18, Martin List-Petersen wrote:
> Different issue. The nameservers should either be made available via
> IPv6 or your nameserver needs IPv4 connectivity.
 >
 > [..]
 >
> Creating another domain for that cause is the wrong approach.

I would of course prefer that they IPv6-enabled one or more of their 
primary DNS servers, but given they are taking a whitelisting approach 
for serving AAAA for www/mail/etc that seems unlikely to happen in the 
near future.

From LLE at dk.ibm.com  Fri Nov  6 16:03:34 2009
From: LLE at dk.ibm.com (Lasse Leegaard)
Date: Fri, 6 Nov 2009 16:03:34 +0100
Subject: AUTO: Lasse Leegaard is out of the office. (returning 09-11-2009)
Message-ID: <OF01FF1F7D.D594358F-ONC1257666.0052B986-C1257666.0052B986@dk.ibm.com>


I am out of the office until 09-11-2009.

For changes, incidents and problems contact SDDK infrastructure
(dm129core at dk.ibm.com) or Kim Lundsteen (kim5 at dk.ibm.com)
For management escalations contact Michael Claus Hansen
(hansenmi at dk.ibm.com)


Note: This is an automated response to your message  "ipv6-ops Digest, Vol
56, Issue 4" sent on 6/11/09 12:00:01.

This is the only notification you will receive while this person is away.


From mleber at he.net  Tue Nov 17 11:18:07 2009
From: mleber at he.net (Mike Leber)
Date: Tue, 17 Nov 2009 02:18:07 -0800
Subject: Top Websites Running IPv6
Message-ID: <4B02785F.8030402@he.net>


I updated the report that we run at 
http://bgp.he.net/ipv6-progress-report.cgi to check the Alexa top 1 
million websites.  We now also check www. and ipv6. for each domain as 
well.  It reveals that quite a few major websites have either added AAAA 
records for their main website or are testing ipv6 at an ipv6. subdomain.

Below is copy of the new section for your entertainment.

Mike.
---

Top Websites Running IPv6
A very quick way to measure IPv6 deployment for websites is just to
check for a AAAA record in DNS.

Alexa provides an approximate list of the most popular sites on the web.

In the report below, the raw domain is the base domain, such as free.fr,
which does not have an AAAA record (at the time of this writing). 
However www.free.fr *does* have a AAAA record. So we check both.

Another convention is to add an AAAA using ipv6 as a subdomain, i.e.
ipv6.google.com. The reason so many domains show up as having A records
for "ipv6." subdomains is because many domains use wildcard records in
DNS which respond to queries for any subdomain.

Alexa Top 1 Million Domains Downloaded: Sat Nov 14 21:47:15 2009
Alexa Top 1 Million Domains Processed: Sat Nov 14 22:25:51 2009

Alexa 1M raw domains: 1000000
Alexa 1M raw with a direct IPv4 address: 924219
Alexa 1M raw with a direct IPv6 address: 1441

(top 50)
ucla.edu 2607:f010:3fe:201:101d:9ff:fe32:adee
tribune.com 2002:a3c0:1712::a3c0:1712
internic.net 2620:0:2d0:200::9
freebsd.org 2001:4f8:fff6::28
gamershell.com 2a00:d00:ff:131:94:228:131:131
monash.edu.au 2001:388:608c:c91::117
animesuki.com 2001:4d88:ffff:ffff:30:524:ac23:2
koreus.com 2001:41d0:2:4133::1
geenstijl.nl 2a00:d00:ff:131:94:228:131:131
python.org 2001:888:2000:d::a2
filezilla-project.org 2a01:198:200:5b7::2
spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
kino.de 2001:a60:9003:a000::b004
torrentfreak.com 2607:f128:40::174
ripe.net 2001:610:240:11::c100:1319
fedoraproject.org 2610:28:200:1::fed0:1
cyberciti.biz 2607:f0d0:1002:11::4
hentai-foundry.com 2607:f0d0:1003:c::30
keenspot.com 2001:470:1:3a::13
snotr.com 2a00:d00:ff:131:94:228:131:131
icann.org 2620:0:2d0:200::7
crooksandliars.com 2001:470:a068:1:230:48ff:fe98:d1a8
softlayer.com 2607:f0d0:1000:11:1::2
itb.ac.id 2001:d30:3::22
infomaniak.ch 2001:1600:3:7::101
bayimg.com 2a01:298:3:1:1337::13
comicgenesis.com 2001:470:1:3a::14
steadfast.net 2607:f128::2
mediabiz.de 2001:a60:9003:a000::b00d
pastebin.ca 2610:1e8:2:20::e8b8:97
stream.ru 2a02:28:2::1076
weeronline.nl 2001:888:30af::206:85
maxconsole.net 2a00:d00:ff:131:94:228:131:131
he.net 2001:470:0:76::2
fernuni-hagen.de 2002:84b0:8101::84b0:8101
exchangecash.de 6563:6173:6802:6465:0:1c00:100:0
pcc.edu 192:192:168:168:1:1:1:1
sify.com 2001:e48:0:10::10
iana.org 2620:0:2d0:1::193
torrentbits.ro 2001:4d18:0:1::32
geenstijl.tv 2a00:d00:ff:131:94:228:131:131
starlink.ru 2a00:e78::7
netbynet.ru 2a00:d18:f00d:d401:fe0b:101:0:67
rcts.pt 2001:690:a00:1036:804::111
cbn.net.id 2001:d10:2:80::80
liu.se 2001:6b0:17:f005::148
phoenixlabs.org 2001:0:53aa:64c:4cc:2161:b717:a85
ubuntu.ru 2001:780:0:25:206:5bff:fe04:8bcb
luc.edu 192:192:168:168:1:1:1:1
menagea3.net 2001:470:1:3a::13

www. + Alexa 1M domains: 1000000
www. + Alexa 1M with a direct IPv4 address: 970789
www. + Alexa 1M with a direct IPv6 address: 1904

(top 50)
www.ucla.edu 2607:f010:3fe:301:101d:9ff:fe32:a7db
www.sakura.ne.jp 2001:e40:100:407::d2e0:ac35
www.free.fr 2a01:e0c:1:1599::1
www.doctissimo.fr 2a01:7b0:2:3::26
www.dti.ne.jp 2001:2e8:22:13::103
www.odn.ne.jp 2001:278:0:1106::4
www.leaseweb.com 2001:1af8:3100:1:214:22ff:fe1e:d380
www.ripe.net 2001:610:240:11::c100:1319
www.monash.edu.au 2001:388:608c:c91::117
www.kddi.com 2001:268:fd02::1
www.gamershell.com 2a00:d00:ff:131:94:228:131:131
www.freebsd.org 2001:4f8:fff6::21
www.internic.net 2620:0:2d0:200::9
www.koreus.com 2001:41d0:2:4136::1
www.animesuki.com 2001:4d88:ffff:ffff:30:524:ac23:2
www.geenstijl.nl 2a00:d00:ff:131:94:228:131:131
www.kino.de 2001:a60:9003:a000::b003
www.spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
www.torrentfreak.com 2607:f128:40::174
www.tvrage.com 2a02:898::110:1
www.rmc.fr 2001:41d0:1:7b1f::1
www.snotr.com 2a00:d00:ff:131:94:228:131:131
www.ulaval.ca 2620:0:1af0:144:ffff::fff2
www.fedoraproject.org 2610:28:200:1::fed0:1
www.icann.org 2620:0:2d0:200::7
www.spele.nl 2a00:f80::10
www.ietf.org 2001:1890:1112:1::20
www.arin.net 2001:500:4:13::81
www.hentai-foundry.com 2607:f0d0:1003:c::30
www.k12.pa.us 2001:5e8:0:1000::fc
www.keenspot.com 2001:470:1:3a::13
www.comicgenesis.com 2001:470:1:3a::14
www.01net.com 2001:41d0:1:118::1
www.hitachi.co.jp 2001:240:400::8591:e013
www.iastate.edu 2610:130:101:102::f0
www.cuhk.edu.hk 2405:3000:3:b0:137:189:11:71
www.ntua.gr 2001:648:2000:de::210
www.rtbf.be 2001:1600:3:6::101
www.nta.go.jp 2001:c80:a001:1::cad9:2c8f
www.up.pt 2001:690:2200:a10::13
www.cyberciti.biz 2607:f0d0:1002:11::4
www.steadfast.net 2607:f128::2
www.infomaniak.ch 2001:1600:3:7::101
www.softlayer.com 2607:f0d0:1000:11:1::1
www.maine.edu 2610:48:100:820::103
www.univie.ac.at 2001:62a:4:1::80:108
www.itb.ac.id 2001:d30:3::22
www.upc.edu 2001:40b0:7500:1::21
www.liu.se 2001:6b0:17:f005::148
www.nnm-club.ru 2001:470:1f0a:1505::2

ipv6. + Alexa 1M domains: 1000000
ipv6. + Alexa 1M with a direct IPv4 address: 243852
ipv6. + Alexa 1M with a direct IPv6 address: 1031

(top 50)
ipv6.netflix.com 2620:0:ef0:13::20
ipv6.2ch.net 2407:3000:6:175::12
ipv6.comcast.net 2001:558:1002:5:68:87:64:48
ipv6.google.com 2001:4860:b004::68
ipv6.google.co.jp 2001:4860:b002::68
ipv6.berkeley.edu 2607:f140:ffff:ffff::80
ipv6.zerolag.com 2001:470:1e::9
ipv6.seznam.cz 2a02:598:1::101
ipv6.21cn.com 2042:8800:1::3
ipv6.denic.de 2001:608:6::1
ipv6.iwiw.hu 2001:4c48:2:a::1
ipv6.freemail.hu 2001:4c48:2:f::100
ipv6.bt.com 2002:c171:3a71::1
ipv6.pku.edu.cn 2001:da8:201:1129:203:baff:fe2f:163c
ipv6.sony.co.jp 2001:cf8:0:6b::190
ipv6.df.eu 2a00:1158:0:100::3
ipv6.koreus.com 2001:41d0:2:4233::1
ipv6.vt.edu 2001:468:c80:210f:0:1c6:1a85:8564
ipv6.tsinghua.edu.cn 2001:da8:1:100::80
ipv6.24ur.com 2001:6f8:919::1
ipv6.dyndns.com 2607:f590:0:ffff::29
ipv6.gatech.edu 2001:468:300:ee01:a00:2bff:fec4:4e8e
ipv6.gazeta.pl 2a02:bd8:1::50fc:91
ipv6.italiansubs.net 2001:41d0:1:8364::1
ipv6.monash.edu.au 2001:388:608c:c91::117
ipv6.bsnl.co.in 2001:4490:100:ff:3::
ipv6.hopto.org 2001:470:8:145::1
ipv6.sify.com 2001:e48:0:6::5
ipv6.spoluzaci.cz 2a02:598:1::102
ipv6.twbbs.org 2001:e10:6840:20:20f:eaff:fe56:ea22
ipv6.peta.org 2001:4978:f:36f::2
ipv6.afraid.org 2001:470:d19b::203
ipv6.ku.ac.th 2001:3c8:1303:1125::18
ipv6.ovh.com 2001:41d0:1:10::d5ba:2122
ipv6.comicgenesis.com 2001:470:1:3a::14
ipv6.eircom.net 2001:bb0:dd0::2
ipv6.atw.hu 2a01:270::4
ipv6.unm.edu 3ffe:2900:11:10::1
ipv6.rtvslo.si 2a02:7a8:0:1::80:1
ipv6.itb.ac.id 2001:d30:3::19
ipv6.sjtu.edu.cn 2001:da8:8000:1::80
ipv6.weeronline.nl 2001:888:30af::206:87
ipv6.infomaniak.ch 2001:1600::ffff
ipv6.nnm-club.ru 2001:470:1f0a:1505::2
ipv6.lsu.edu 2620:0:da0:f001::7
ipv6.iana.org 2620:0:2d0:1::194
ipv6.trueinternet.co.th 2001:fb0:100:1:58:97:5:30
ipv6.gsa.gov 2620:0:150:ffad::5
ipv6.spele.nl 2a00:f80::10
ipv6.uni-erlangen.de 2001:638:a00:2::2

From daniel at bit.nl  Tue Nov 17 11:42:08 2009
From: daniel at bit.nl (Daniel Verlouw)
Date: Tue, 17 Nov 2009 11:42:08 +0100
Subject: Top Websites Running IPv6
In-Reply-To: <4B02785F.8030402@he.net>
References: <4B02785F.8030402@he.net>
Message-ID: <1258454528.13409.10.camel@daniel.office.bit.nl>

On Tue, 2009-11-17 at 02:18 -0800, Mike Leber wrote:
> gamershell.com 2a00:d00:ff:131:94:228:131:131
> geenstijl.nl 2a00:d00:ff:131:94:228:131:131
> spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
> snotr.com 2a00:d00:ff:131:94:228:131:131
> maxconsole.net 2a00:d00:ff:131:94:228:131:131
> geenstijl.tv 2a00:d00:ff:131:94:228:131:131
> www.gamershell.com 2a00:d00:ff:131:94:228:131:131

[...etc... you get the picture]

JFYI: these are all AAAA records pointing to an IPv6-to-IPv4 proxy. The
actual sites themselves don't have native IPv6 connectivity.

daniel at daniel:~$ dig -x 2a00:d00:ff:131:94:228:131:131 +short
ipv6proxy.prolocation.net.

   --Daniel.


From mleber at he.net  Tue Nov 17 11:50:19 2009
From: mleber at he.net (Mike Leber)
Date: Tue, 17 Nov 2009 02:50:19 -0800
Subject: Top Websites Running IPv6
In-Reply-To: <1258454528.13409.10.camel@daniel.office.bit.nl>
References: <4B02785F.8030402@he.net>
	<1258454528.13409.10.camel@daniel.office.bit.nl>
Message-ID: <4B027FEB.6020503@he.net>


Daniel Verlouw wrote:
> On Tue, 2009-11-17 at 02:18 -0800, Mike Leber wrote:
>> gamershell.com 2a00:d00:ff:131:94:228:131:131
>> geenstijl.nl 2a00:d00:ff:131:94:228:131:131
>> spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
>> snotr.com 2a00:d00:ff:131:94:228:131:131
>> maxconsole.net 2a00:d00:ff:131:94:228:131:131
>> geenstijl.tv 2a00:d00:ff:131:94:228:131:131
>> www.gamershell.com 2a00:d00:ff:131:94:228:131:131
> 
> [...etc... you get the picture]
> 
> JFYI: these are all AAAA records pointing to an IPv6-to-IPv4 proxy. The
> actual sites themselves don't have native IPv6 connectivity.
> 
> daniel at daniel:~$ dig -x 2a00:d00:ff:131:94:228:131:131 +short
> ipv6proxy.prolocation.net.

Yep, and if you look closely at the others listed you'll find other 
anomalous entries that either indicate interesting transitional choices 
or outright mistakes.  If notice something like that and know any of the 
people involved you might make a polite inquiry.

In any case, AAAA records are getting added for major websites.

Mike.

From gert at space.net  Tue Nov 17 12:13:28 2009
From: gert at space.net (Gert Doering)
Date: Tue, 17 Nov 2009 12:13:28 +0100
Subject: Top Websites Running IPv6
In-Reply-To: <1258454528.13409.10.camel@daniel.office.bit.nl>
References: <4B02785F.8030402@he.net>
	<1258454528.13409.10.camel@daniel.office.bit.nl>
Message-ID: <20091117111328.GC32226@Space.Net>

Hi,

On Tue, Nov 17, 2009 at 11:42:08AM +0100, Daniel Verlouw wrote:
> JFYI: these are all AAAA records pointing to an IPv6-to-IPv4 proxy. The
> actual sites themselves don't have native IPv6 connectivity.

Proxy is better than nothing :-)

How do you handle web server logging on the "real" server?  We considered
setting up such a proxy, and decided against it, because it would make
the access_log on the real server contain only the proxy address for
v6 connections - which is not what we wanted...

Gert Doering
        -- NetMaster
-- 
Total number of prefixes smaller than registry allocations:  144438

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

From ek at google.com  Tue Nov 17 12:17:52 2009
From: ek at google.com (Erik Kline)
Date: Tue, 17 Nov 2009 20:17:52 +0900
Subject: Top Websites Running IPv6
In-Reply-To: <20091117111328.GC32226@Space.Net>
References: <4B02785F.8030402@he.net>
	<1258454528.13409.10.camel@daniel.office.bit.nl>
	<20091117111328.GC32226@Space.Net>
Message-ID: <2e8c64260911170317u6878cc84x7f04cb636e6c8a82@mail.gmail.com>

> On Tue, Nov 17, 2009 at 11:42:08AM +0100, Daniel Verlouw wrote:
>> JFYI: these are all AAAA records pointing to an IPv6-to-IPv4 proxy. The
>> actual sites themselves don't have native IPv6 connectivity.
>
> Proxy is better than nothing :-)

I don't know about that.  What do you do for SSL?  And all the
IP-based geolocation goes out the window.  I suppose it works for
simpler websites, but the simpler websites could more easily to real
IPv6 because the associated risk is probably lower (perhaps).

From daniel at bit.nl  Tue Nov 17 12:21:33 2009
From: daniel at bit.nl (Daniel Verlouw)
Date: Tue, 17 Nov 2009 12:21:33 +0100
Subject: Top Websites Running IPv6
In-Reply-To: <20091117111328.GC32226@Space.Net>
References: <4B02785F.8030402@he.net>
	<1258454528.13409.10.camel@daniel.office.bit.nl>
	<20091117111328.GC32226@Space.Net>
Message-ID: <1258456893.13409.15.camel@daniel.office.bit.nl>

On Tue, 2009-11-17 at 12:13 +0100, Gert Doering wrote:
> How do you handle web server logging on the "real" server?  We considered
> setting up such a proxy, and decided against it, because it would make
> the access_log on the real server contain only the proxy address for
> v6 connections - which is not what we wanted...

you -could- have the proxy insert an 'X-Forwarder-For' header (or
whatever you wanna call it) with the orignal client IPv6 address and use
custom Apache logging on the real server, e.g.

LogFormat "%v %{X-Forwarded-For}i %l %u %t \"%r\" %>s %b"
X-Forwarded-For
CustomLog /var/log/apache/www.myexample.com-xforwarded.log X-Forwarded-For


   --Daniel.


From trejrco at gmail.com  Tue Nov 17 13:16:27 2009
From: trejrco at gmail.com (TJ)
Date: Tue, 17 Nov 2009 07:16:27 -0500
Subject: ipv6-ops Digest, Vol 56, Issue 6
In-Reply-To: <71bfd60c0911170413t63ba0565j452628ea1bf2304c@mail.gmail.com>
References: <mailman.1.1258455601.4685.ipv6-ops@lists.cluenet.de>
	<71bfd60c0911170413t63ba0565j452628ea1bf2304c@mail.gmail.com>
Message-ID: <71bfd60c0911170416n1aa635a3t232fb0b90d236859@mail.gmail.com>

Where do the 192:192:168:168:1:1:1:1 come from?  What builds an IPv6 address
this way from its IPv4 (rfc1918) addr and why??

On Nov 17, 2009 6:00 AM, <ipv6-ops-request at lists.cluenet.de> wrote:

Send ipv6-ops mailing list submissions to
       ipv6-ops at lists.cluenet.de

To subscribe or unsubscribe via the World Wide Web, visit
       http://lists.cluenet.de/mailman/listinfo/ipv6-ops
or, via email, send a message with subject or body 'help' to
       ipv6-ops-request at lists.cluenet.de

You can reach the person managing the list at
       ipv6-ops-owner at lists.cluenet.de

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ipv6-ops digest..."


Today's Topics:

  1. Top Websites Running IPv6 (Mike Leber)
  2. Re: Top Websites Running IPv6 (Daniel Verlouw)
  3. Re: Top Websites Running IPv6 (Mike Leber)


----------------------------------------------------------------------

Message: 1
Date: Tue, 17 Nov 2009 02:18:07 -0800
From: Mike Leber <mleber at he.net>
Subject: Top Websites Running IPv6
To: ipv6-ops at lists.cluenet.de
Message-ID: <4B02785F.8030402 at he.net>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed


I updated the report that we run at
http://bgp.he.net/ipv6-progress-report.cgi to check the Alexa top 1
million websites.  We now also check www. and ipv6. for each domain as
well.  It reveals that quite a few major websites have either added AAAA
records for their main website or are testing ipv6 at an ipv6. subdomain.

Below is copy of the new section for your entertainment.

Mike.
---

Top Websites Running IPv6
A very quick way to measure IPv6 deployment for websites is just to
check for a AAAA record in DNS.

Alexa provides an approximate list of the most popular sites on the web.

In the report below, the raw domain is the base domain, such as free.fr,
which does not have an AAAA record (at the time of this writing).
However www.free.fr *does* have a AAAA record. So we check both.

Another convention is to add an AAAA using ipv6 as a subdomain, i.e.
ipv6.google.com. The reason so many domains show up as having A records
for "ipv6." subdomains is because many domains use wildcard records in
DNS which respond to queries for any subdomain.

Alexa Top 1 Million Domains Downloaded: Sat Nov 14 21:47:15 2009
Alexa Top 1 Million Domains Processed: Sat Nov 14 22:25:51 2009

Alexa 1M raw domains: 1000000
Alexa 1M raw with a direct IPv4 address: 924219
Alexa 1M raw with a direct IPv6 address: 1441

(top 50)
ucla.edu 2607:f010:3fe:201:101d:9ff:fe32:adee
tribune.com 2002:a3c0:1712::a3c0:1712
internic.net 2620:0:2d0:200::9
freebsd.org 2001:4f8:fff6::28
gamershell.com 2a00:d00:ff:131:94:228:131:131
monash.edu.au 2001:388:608c:c91::117
animesuki.com 2001:4d88:ffff:ffff:30:524:ac23:2
koreus.com 2001:41d0:2:4133::1
geenstijl.nl 2a00:d00:ff:131:94:228:131:131
python.org 2001:888:2000:d::a2
filezilla-project.org 2a01:198:200:5b7::2
spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
kino.de 2001:a60:9003:a000::b004
torrentfreak.com 2607:f128:40::174
ripe.net 2001:610:240:11::c100:1319
fedoraproject.org 2610:28:200:1::fed0:1
cyberciti.biz 2607:f0d0:1002:11::4
hentai-foundry.com 2607:f0d0:1003:c::30
keenspot.com 2001:470:1:3a::13
snotr.com 2a00:d00:ff:131:94:228:131:131
icann.org 2620:0:2d0:200::7
crooksandliars.com 2001:470:a068:1:230:48ff:fe98:d1a8
softlayer.com 2607:f0d0:1000:11:1::2
itb.ac.id 2001:d30:3::22
infomaniak.ch 2001:1600:3:7::101
bayimg.com 2a01:298:3:1:1337::13
comicgenesis.com 2001:470:1:3a::14
steadfast.net 2607:f128::2
mediabiz.de 2001:a60:9003:a000::b00d
pastebin.ca 2610:1e8:2:20::e8b8:97
stream.ru 2a02:28:2::1076
weeronline.nl 2001:888:30af::206:85
maxconsole.net 2a00:d00:ff:131:94:228:131:131
he.net 2001:470:0:76::2
fernuni-hagen.de 2002:84b0:8101::84b0:8101
exchangecash.de 6563:6173:6802:6465:0:1c00:100:0
pcc.edu 192:192:168:168:1:1:1:1
sify.com 2001:e48:0:10::10
iana.org 2620:0:2d0:1::193
torrentbits.ro 2001:4d18:0:1::32
geenstijl.tv 2a00:d00:ff:131:94:228:131:131
starlink.ru 2a00:e78::7
netbynet.ru 2a00:d18:f00d:d401:fe0b:101:0:67
rcts.pt 2001:690:a00:1036:804::111
cbn.net.id 2001:d10:2:80::80
liu.se 2001:6b0:17:f005::148
phoenixlabs.org 2001:0:53aa:64c:4cc:2161:b717:a85
ubuntu.ru 2001:780:0:25:206:5bff:fe04:8bcb
luc.edu 192:192:168:168:1:1:1:1
menagea3.net 2001:470:1:3a::13

www. + Alexa 1M domains: 1000000
www. + Alexa 1M with a direct IPv4 address: 970789
www. + Alexa 1M with a direct IPv6 address: 1904

(top 50)
www.ucla.edu 2607:f010:3fe:301:101d:9ff:fe32:a7db
www.sakura.ne.jp 2001:e40:100:407::d2e0:ac35
www.free.fr 2a01:e0c:1:1599::1
www.doctissimo.fr 2a01:7b0:2:3::26
www.dti.ne.jp 2001:2e8:22:13::103
www.odn.ne.jp 2001:278:0:1106::4
www.leaseweb.com 2001:1af8:3100:1:214:22ff:fe1e:d380
www.ripe.net 2001:610:240:11::c100:1319
www.monash.edu.au 2001:388:608c:c91::117
www.kddi.com 2001:268:fd02::1
www.gamershell.com 2a00:d00:ff:131:94:228:131:131
www.freebsd.org 2001:4f8:fff6::21
www.internic.net 2620:0:2d0:200::9
www.koreus.com 2001:41d0:2:4136::1
www.animesuki.com 2001:4d88:ffff:ffff:30:524:ac23:2
www.geenstijl.nl 2a00:d00:ff:131:94:228:131:131
www.kino.de 2001:a60:9003:a000::b003
www.spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
www.torrentfreak.com 2607:f128:40::174
www.tvrage.com 2a02:898::110:1
www.rmc.fr 2001:41d0:1:7b1f::1
www.snotr.com 2a00:d00:ff:131:94:228:131:131
www.ulaval.ca 2620:0:1af0:144:ffff::fff2
www.fedoraproject.org 2610:28:200:1::fed0:1
www.icann.org 2620:0:2d0:200::7
www.spele.nl 2a00:f80::10
www.ietf.org 2001:1890:1112:1::20
www.arin.net 2001:500:4:13::81
www.hentai-foundry.com 2607:f0d0:1003:c::30
www.k12.pa.us 2001:5e8:0:1000::fc
www.keenspot.com 2001:470:1:3a::13
www.comicgenesis.com 2001:470:1:3a::14
www.01net.com 2001:41d0:1:118::1
www.hitachi.co.jp 2001:240:400::8591:e013
www.iastate.edu 2610:130:101:102::f0
www.cuhk.edu.hk 2405:3000:3:b0:137:189:11:71
www.ntua.gr 2001:648:2000:de::210
www.rtbf.be 2001:1600:3:6::101
www.nta.go.jp 2001:c80:a001:1::cad9:2c8f
www.up.pt 2001:690:2200:a10::13
www.cyberciti.biz 2607:f0d0:1002:11::4
www.steadfast.net 2607:f128::2
www.infomaniak.ch 2001:1600:3:7::101
www.softlayer.com 2607:f0d0:1000:11:1::1
www.maine.edu 2610:48:100:820::103
www.univie.ac.at 2001:62a:4:1::80:108
www.itb.ac.id 2001:d30:3::22
www.upc.edu 2001:40b0:7500:1::21
www.liu.se 2001:6b0:17:f005::148
www.nnm-club.ru 2001:470:1f0a:1505::2

ipv6. + Alexa 1M domains: 1000000
ipv6. + Alexa 1M with a direct IPv4 address: 243852
ipv6. + Alexa 1M with a direct IPv6 address: 1031

(top 50)
ipv6.netflix.com 2620:0:ef0:13::20
ipv6.2ch.net 2407:3000:6:175::12
ipv6.comcast.net 2001:558:1002:5:68:87:64:48
ipv6.google.com 2001:4860:b004::68
ipv6.google.co.jp 2001:4860:b002::68
ipv6.berkeley.edu 2607:f140:ffff:ffff::80
ipv6.zerolag.com 2001:470:1e::9
ipv6.seznam.cz 2a02:598:1::101
ipv6.21cn.com 2042:8800:1::3
ipv6.denic.de 2001:608:6::1
ipv6.iwiw.hu 2001:4c48:2:a::1
ipv6.freemail.hu 2001:4c48:2:f::100
ipv6.bt.com 2002:c171:3a71::1
ipv6.pku.edu.cn 2001:da8:201:1129:203:baff:fe2f:163c
ipv6.sony.co.jp 2001:cf8:0:6b::190
ipv6.df.eu 2a00:1158:0:100::3
ipv6.koreus.com 2001:41d0:2:4233::1
ipv6.vt.edu 2001:468:c80:210f:0:1c6:1a85:8564
ipv6.tsinghua.edu.cn 2001:da8:1:100::80
ipv6.24ur.com 2001:6f8:919::1
ipv6.dyndns.com 2607:f590:0:ffff::29
ipv6.gatech.edu 2001:468:300:ee01:a00:2bff:fec4:4e8e
ipv6.gazeta.pl 2a02:bd8:1::50fc:91
ipv6.italiansubs.net 2001:41d0:1:8364::1
ipv6.monash.edu.au 2001:388:608c:c91::117
ipv6.bsnl.co.in 2001:4490:100:ff:3::
ipv6.hopto.org 2001:470:8:145::1
ipv6.sify.com 2001:e48:0:6::5
ipv6.spoluzaci.cz 2a02:598:1::102
ipv6.twbbs.org 2001:e10:6840:20:20f:eaff:fe56:ea22
ipv6.peta.org 2001:4978:f:36f::2
ipv6.afraid.org 2001:470:d19b::203
ipv6.ku.ac.th 2001:3c8:1303:1125::18
ipv6.ovh.com 2001:41d0:1:10::d5ba:2122
ipv6.comicgenesis.com 2001:470:1:3a::14
ipv6.eircom.net 2001:bb0:dd0::2
ipv6.atw.hu 2a01:270::4
ipv6.unm.edu 3ffe:2900:11:10::1
ipv6.rtvslo.si 2a02:7a8:0:1::80:1
ipv6.itb.ac.id 2001:d30:3::19
ipv6.sjtu.edu.cn 2001:da8:8000:1::80
ipv6.weeronline.nl 2001:888:30af::206:87
ipv6.infomaniak.ch 2001:1600::ffff
ipv6.nnm-club.ru 2001:470:1f0a:1505::2
ipv6.lsu.edu 2620:0:da0:f001::7
ipv6.iana.org 2620:0:2d0:1::194
ipv6.trueinternet.co.th 2001:fb0:100:1:58:97:5:30
ipv6.gsa.gov 2620:0:150:ffad::5
ipv6.spele.nl 2a00:f80::10
ipv6.uni-erlangen.de 2001:638:a00:2::2


------------------------------

Message: 2
Date: Tue, 17 Nov 2009 11:42:08 +0100
From: Daniel Verlouw <daniel at bit.nl>
Subject: Re: Top Websites Running IPv6
To: Mike Leber <mleber at he.net>
Cc: ipv6-ops at lists.cluenet.de
Message-ID: <1258454528.13409.10.camel at daniel.office.bit.nl>
Content-Type: text/plain

On Tue, 2009-11-17 at 02:18 -0800, Mike Leber wrote:
> gamershell.com 2a00:d00:ff:131:94:228:131:131
> geenstijl.nl 2a00:d00:ff:131:94:228:131:131
> spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
> snotr.com 2a00:d00:ff:131:94:228:131:131
> maxconsole.net 2a00:d00:ff:131:94:228:131:131
> geenstijl.tv 2a00:d00:ff:131:94:228:131:131
> www.gamershell.com 2a00:d00:ff:131:94:228:131:131

[...etc... you get the picture]

JFYI: these are all AAAA records pointing to an IPv6-to-IPv4 proxy. The
actual sites themselves don't have native IPv6 connectivity.

daniel at daniel:~$ dig -x 2a00:d00:ff:131:94:228:131:131 +short
ipv6proxy.prolocation.net.

  --Daniel.



------------------------------

Message: 3
Date: Tue, 17 Nov 2009 02:50:19 -0800
From: Mike Leber <mleber at he.net>
Subject: Re: Top Websites Running IPv6
To: Daniel Verlouw <daniel at bit.nl>
Cc: ipv6-ops at lists.cluenet.de
Message-ID: <4B027FEB.6020503 at he.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed


Daniel Verlouw wrote:
> On Tue, 2009-11-17 at 02:18 -0800, Mike Leber wrote:
>> gamershell.com 2a00:d00:ff:131:94:228:131:131
>> geenstijl.nl 2a00:d00:ff:131:94:228:131:131
>> spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
>> snotr.com 2a00:d00:ff:131:94:228:131:131
>> maxconsole.net 2a00:d00:ff:131:94:228:131:131
>> geenstijl.tv 2a00:d00:ff:131:94:228:131:131
>> www.gamershell.com 2a00:d00:ff:131:94:228:131:131
>
> [...etc... you get the picture]
>
> JFYI: these are all AAAA records pointing to an IPv6-to-IPv4 proxy. The
> actual sites themselves don't have native IPv6 connectivity.
>
> daniel at daniel:~$ dig -x 2a00:d00:ff:131:94:228:131:131 +short
> ipv6proxy.prolocation.net.

Yep, and if you look closely at the others listed you'll find other
anomalous entries that either indicate interesting transitional choices
or outright mistakes.  If notice something like that and know any of the
people involved you might make a polite inquiry.

In any case, AAAA records are getting added for major websites.

Mike.


------------------------------

_______________________________________________
ipv6-ops mailing list
ipv6-ops at lists.cluenet.de
http://lists.cluenet.de/mailman/listinfo/ipv6-ops


End of ipv6-ops Digest, Vol 56, Issue 6
***************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20091117/11bbe211/attachment-0001.html 

From ryanczak at arin.net  Tue Nov 17 13:26:48 2009
From: ryanczak at arin.net (Matt Ryanczak)
Date: Tue, 17 Nov 2009 07:26:48 -0500
Subject: ipv6-ops Digest, Vol 56, Issue 6
In-Reply-To: <71bfd60c0911170416n1aa635a3t232fb0b90d236859@mail.gmail.com>
References: <mailman.1.1258455601.4685.ipv6-ops@lists.cluenet.de>
	<71bfd60c0911170413t63ba0565j452628ea1bf2304c@mail.gmail.com>
	<71bfd60c0911170416n1aa635a3t232fb0b90d236859@mail.gmail.com>
Message-ID: <1258460808.14441.14.camel@otto>

My guess is that they come from the same consultant that set up both of
those edu sites. 

On Tue, 2009-11-17 at 07:16 -0500, TJ wrote:
> Where do the 192:192:168:168:1:1:1:1 come from?  What builds an IPv6
> address this way from its IPv4 (rfc1918) addr and why??
> 
> > On Nov 17, 2009 6:00 AM, <ipv6-ops-request at lists.cluenet.de> wrote:
> > 
> > Send ipv6-ops mailing list submissions to
> >        ipv6-ops at lists.cluenet.de
> > 
> > To subscribe or unsubscribe via the World Wide Web, visit
> >        http://lists.cluenet.de/mailman/listinfo/ipv6-ops
> > or, via email, send a message with subject or body 'help' to
> >        ipv6-ops-request at lists.cluenet.de
> > 
> > You can reach the person managing the list at
> >        ipv6-ops-owner at lists.cluenet.de
> > 
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of ipv6-ops digest..."
> > 
> > 
> > Today's Topics:
> > 
> >   1. Top Websites Running IPv6 (Mike Leber)
> >   2. Re: Top Websites Running IPv6 (Daniel Verlouw)
> >   3. Re: Top Websites Running IPv6 (Mike Leber)
> > 
> > 
> > ----------------------------------------------------------------------
> > 
> > Message: 1
> > Date: Tue, 17 Nov 2009 02:18:07 -0800
> > From: Mike Leber <mleber at he.net>
> > Subject: Top Websites Running IPv6
> > To: ipv6-ops at lists.cluenet.de
> > Message-ID: <4B02785F.8030402 at he.net>
> > Content-Type: text/plain; charset=ISO-8859-15; format=flowed
> > 
> > 
> > I updated the report that we run at
> > http://bgp.he.net/ipv6-progress-report.cgi to check the Alexa top 1
> > million websites.  We now also check www. and ipv6. for each domain
> > as
> > well.  It reveals that quite a few major websites have either added
> > AAAA
> > records for their main website or are testing ipv6 at an ipv6.
> > subdomain.
> > 
> > Below is copy of the new section for your entertainment.
> > 
> > Mike.
> > ---
> > 
> > Top Websites Running IPv6
> > A very quick way to measure IPv6 deployment for websites is just to
> > check for a AAAA record in DNS.
> > 
> > Alexa provides an approximate list of the most popular sites on the
> > web.
> > 
> > In the report below, the raw domain is the base domain, such as
> > free.fr,
> > which does not have an AAAA record (at the time of this writing).
> > However www.free.fr *does* have a AAAA record. So we check both.
> > 
> > Another convention is to add an AAAA using ipv6 as a subdomain, i.e.
> > ipv6.google.com. The reason so many domains show up as having A
> > records
> > for "ipv6." subdomains is because many domains use wildcard records
> > in
> > DNS which respond to queries for any subdomain.
> > 
> > Alexa Top 1 Million Domains Downloaded: Sat Nov 14 21:47:15 2009
> > Alexa Top 1 Million Domains Processed: Sat Nov 14 22:25:51 2009
> > 
> > Alexa 1M raw domains: 1000000
> > Alexa 1M raw with a direct IPv4 address: 924219
> > Alexa 1M raw with a direct IPv6 address: 1441
> > 
> > (top 50)
> > ucla.edu 2607:f010:3fe:201:101d:9ff:fe32:adee
> > tribune.com 2002:a3c0:1712::a3c0:1712
> > internic.net 2620:0:2d0:200::9
> > freebsd.org 2001:4f8:fff6::28
> > gamershell.com 2a00:d00:ff:131:94:228:131:131
> > monash.edu.au 2001:388:608c:c91::117
> > animesuki.com 2001:4d88:ffff:ffff:30:524:ac23:2
> > koreus.com 2001:41d0:2:4133::1
> > geenstijl.nl 2a00:d00:ff:131:94:228:131:131
> > python.org 2001:888:2000:d::a2
> > filezilla-project.org 2a01:198:200:5b7::2
> > spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
> > kino.de 2001:a60:9003:a000::b004
> > torrentfreak.com 2607:f128:40::174
> > ripe.net 2001:610:240:11::c100:1319
> > fedoraproject.org 2610:28:200:1::fed0:1
> > cyberciti.biz 2607:f0d0:1002:11::4
> > hentai-foundry.com 2607:f0d0:1003:c::30
> > keenspot.com 2001:470:1:3a::13
> > snotr.com 2a00:d00:ff:131:94:228:131:131
> > icann.org 2620:0:2d0:200::7
> > crooksandliars.com 2001:470:a068:1:230:48ff:fe98:d1a8
> > softlayer.com 2607:f0d0:1000:11:1::2
> > itb.ac.id 2001:d30:3::22
> > infomaniak.ch 2001:1600:3:7::101
> > bayimg.com 2a01:298:3:1:1337::13
> > comicgenesis.com 2001:470:1:3a::14
> > steadfast.net 2607:f128::2
> > mediabiz.de 2001:a60:9003:a000::b00d
> > pastebin.ca 2610:1e8:2:20::e8b8:97
> > stream.ru 2a02:28:2::1076
> > weeronline.nl 2001:888:30af::206:85
> > maxconsole.net 2a00:d00:ff:131:94:228:131:131
> > he.net 2001:470:0:76::2
> > fernuni-hagen.de 2002:84b0:8101::84b0:8101
> > exchangecash.de 6563:6173:6802:6465:0:1c00:100:0
> > pcc.edu 192:192:168:168:1:1:1:1
> > sify.com 2001:e48:0:10::10
> > iana.org 2620:0:2d0:1::193
> > torrentbits.ro 2001:4d18:0:1::32
> > geenstijl.tv 2a00:d00:ff:131:94:228:131:131
> > starlink.ru 2a00:e78::7
> > netbynet.ru 2a00:d18:f00d:d401:fe0b:101:0:67
> > rcts.pt 2001:690:a00:1036:804::111
> > cbn.net.id 2001:d10:2:80::80
> > liu.se 2001:6b0:17:f005::148
> > phoenixlabs.org 2001:0:53aa:64c:4cc:2161:b717:a85
> > ubuntu.ru 2001:780:0:25:206:5bff:fe04:8bcb
> > luc.edu 192:192:168:168:1:1:1:1
> > menagea3.net 2001:470:1:3a::13
> > 
> > www. + Alexa 1M domains: 1000000
> > www. + Alexa 1M with a direct IPv4 address: 970789
> > www. + Alexa 1M with a direct IPv6 address: 1904
> > 
> > (top 50)
> > www.ucla.edu 2607:f010:3fe:301:101d:9ff:fe32:a7db
> > www.sakura.ne.jp 2001:e40:100:407::d2e0:ac35
> > www.free.fr 2a01:e0c:1:1599::1
> > www.doctissimo.fr 2a01:7b0:2:3::26
> > www.dti.ne.jp 2001:2e8:22:13::103
> > www.odn.ne.jp 2001:278:0:1106::4
> > www.leaseweb.com 2001:1af8:3100:1:214:22ff:fe1e:d380
> > www.ripe.net 2001:610:240:11::c100:1319
> > www.monash.edu.au 2001:388:608c:c91::117
> > www.kddi.com 2001:268:fd02::1
> > www.gamershell.com 2a00:d00:ff:131:94:228:131:131
> > www.freebsd.org 2001:4f8:fff6::21
> > www.internic.net 2620:0:2d0:200::9
> > www.koreus.com 2001:41d0:2:4136::1
> > www.animesuki.com 2001:4d88:ffff:ffff:30:524:ac23:2
> > www.geenstijl.nl 2a00:d00:ff:131:94:228:131:131
> > www.kino.de 2001:a60:9003:a000::b003
> > www.spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
> > www.torrentfreak.com 2607:f128:40::174
> > www.tvrage.com 2a02:898::110:1
> > www.rmc.fr 2001:41d0:1:7b1f::1
> > www.snotr.com 2a00:d00:ff:131:94:228:131:131
> > www.ulaval.ca 2620:0:1af0:144:ffff::fff2
> > www.fedoraproject.org 2610:28:200:1::fed0:1
> > www.icann.org 2620:0:2d0:200::7
> > www.spele.nl 2a00:f80::10
> > www.ietf.org 2001:1890:1112:1::20
> > www.arin.net 2001:500:4:13::81
> > www.hentai-foundry.com 2607:f0d0:1003:c::30
> > www.k12.pa.us 2001:5e8:0:1000::fc
> > www.keenspot.com 2001:470:1:3a::13
> > www.comicgenesis.com 2001:470:1:3a::14
> > www.01net.com 2001:41d0:1:118::1
> > www.hitachi.co.jp 2001:240:400::8591:e013
> > www.iastate.edu 2610:130:101:102::f0
> > www.cuhk.edu.hk 2405:3000:3:b0:137:189:11:71
> > www.ntua.gr 2001:648:2000:de::210
> > www.rtbf.be 2001:1600:3:6::101
> > www.nta.go.jp 2001:c80:a001:1::cad9:2c8f
> > www.up.pt 2001:690:2200:a10::13
> > www.cyberciti.biz 2607:f0d0:1002:11::4
> > www.steadfast.net 2607:f128::2
> > www.infomaniak.ch 2001:1600:3:7::101
> > www.softlayer.com 2607:f0d0:1000:11:1::1
> > www.maine.edu 2610:48:100:820::103
> > www.univie.ac.at 2001:62a:4:1::80:108
> > www.itb.ac.id 2001:d30:3::22
> > www.upc.edu 2001:40b0:7500:1::21
> > www.liu.se 2001:6b0:17:f005::148
> > www.nnm-club.ru 2001:470:1f0a:1505::2
> > 
> > ipv6. + Alexa 1M domains: 1000000
> > ipv6. + Alexa 1M with a direct IPv4 address: 243852
> > ipv6. + Alexa 1M with a direct IPv6 address: 1031
> > 
> > (top 50)
> > ipv6.netflix.com 2620:0:ef0:13::20
> > ipv6.2ch.net 2407:3000:6:175::12
> > ipv6.comcast.net 2001:558:1002:5:68:87:64:48
> > ipv6.google.com 2001:4860:b004::68
> > ipv6.google.co.jp 2001:4860:b002::68
> > ipv6.berkeley.edu 2607:f140:ffff:ffff::80
> > ipv6.zerolag.com 2001:470:1e::9
> > ipv6.seznam.cz 2a02:598:1::101
> > ipv6.21cn.com 2042:8800:1::3
> > ipv6.denic.de 2001:608:6::1
> > ipv6.iwiw.hu 2001:4c48:2:a::1
> > ipv6.freemail.hu 2001:4c48:2:f::100
> > ipv6.bt.com 2002:c171:3a71::1
> > ipv6.pku.edu.cn 2001:da8:201:1129:203:baff:fe2f:163c
> > ipv6.sony.co.jp 2001:cf8:0:6b::190
> > ipv6.df.eu 2a00:1158:0:100::3
> > ipv6.koreus.com 2001:41d0:2:4233::1
> > ipv6.vt.edu 2001:468:c80:210f:0:1c6:1a85:8564
> > ipv6.tsinghua.edu.cn 2001:da8:1:100::80
> > ipv6.24ur.com 2001:6f8:919::1
> > ipv6.dyndns.com 2607:f590:0:ffff::29
> > ipv6.gatech.edu 2001:468:300:ee01:a00:2bff:fec4:4e8e
> > ipv6.gazeta.pl 2a02:bd8:1::50fc:91
> > ipv6.italiansubs.net 2001:41d0:1:8364::1
> > ipv6.monash.edu.au 2001:388:608c:c91::117
> > ipv6.bsnl.co.in 2001:4490:100:ff:3::
> > ipv6.hopto.org 2001:470:8:145::1
> > ipv6.sify.com 2001:e48:0:6::5
> > ipv6.spoluzaci.cz 2a02:598:1::102
> > ipv6.twbbs.org 2001:e10:6840:20:20f:eaff:fe56:ea22
> > ipv6.peta.org 2001:4978:f:36f::2
> > ipv6.afraid.org 2001:470:d19b::203
> > ipv6.ku.ac.th 2001:3c8:1303:1125::18
> > ipv6.ovh.com 2001:41d0:1:10::d5ba:2122
> > ipv6.comicgenesis.com 2001:470:1:3a::14
> > ipv6.eircom.net 2001:bb0:dd0::2
> > ipv6.atw.hu 2a01:270::4
> > ipv6.unm.edu 3ffe:2900:11:10::1
> > ipv6.rtvslo.si 2a02:7a8:0:1::80:1
> > ipv6.itb.ac.id 2001:d30:3::19
> > ipv6.sjtu.edu.cn 2001:da8:8000:1::80
> > ipv6.weeronline.nl 2001:888:30af::206:87
> > ipv6.infomaniak.ch 2001:1600::ffff
> > ipv6.nnm-club.ru 2001:470:1f0a:1505::2
> > ipv6.lsu.edu 2620:0:da0:f001::7
> > ipv6.iana.org 2620:0:2d0:1::194
> > ipv6.trueinternet.co.th 2001:fb0:100:1:58:97:5:30
> > ipv6.gsa.gov 2620:0:150:ffad::5
> > ipv6.spele.nl 2a00:f80::10
> > ipv6.uni-erlangen.de 2001:638:a00:2::2
> > 
> > 
> > ------------------------------
> > 
> > Message: 2
> > Date: Tue, 17 Nov 2009 11:42:08 +0100
> > From: Daniel Verlouw <daniel at bit.nl>
> > Subject: Re: Top Websites Running IPv6
> > To: Mike Leber <mleber at he.net>
> > Cc: ipv6-ops at lists.cluenet.de
> > Message-ID: <1258454528.13409.10.camel at daniel.office.bit.nl>
> > Content-Type: text/plain
> > 
> > On Tue, 2009-11-17 at 02:18 -0800, Mike Leber wrote:
> > > gamershell.com 2a00:d00:ff:131:94:228:131:131
> > > geenstijl.nl 2a00:d00:ff:131:94:228:131:131
> > > spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
> > > snotr.com 2a00:d00:ff:131:94:228:131:131
> > > maxconsole.net 2a00:d00:ff:131:94:228:131:131
> > > geenstijl.tv 2a00:d00:ff:131:94:228:131:131
> > > www.gamershell.com 2a00:d00:ff:131:94:228:131:131
> > 
> > [...etc... you get the picture]
> > 
> > JFYI: these are all AAAA records pointing to an IPv6-to-IPv4 proxy.
> > The
> > actual sites themselves don't have native IPv6 connectivity.
> > 
> > daniel at daniel:~$ dig -x 2a00:d00:ff:131:94:228:131:131 +short
> > ipv6proxy.prolocation.net.
> > 
> >   --Daniel.
> > 
> > 
> > 
> > ------------------------------
> > 
> > Message: 3
> > Date: Tue, 17 Nov 2009 02:50:19 -0800
> > From: Mike Leber <mleber at he.net>
> > Subject: Re: Top Websites Running IPv6
> > To: Daniel Verlouw <daniel at bit.nl>
> > Cc: ipv6-ops at lists.cluenet.de
> > Message-ID: <4B027FEB.6020503 at he.net>
> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> > 
> > 
> > Daniel Verlouw wrote:
> > > On Tue, 2009-11-17 at 02:18 -0800, Mike Leber wrote:
> > >> gamershell.com 2a00:d00:ff:131:94:228:131:131
> > >> geenstijl.nl 2a00:d00:ff:131:94:228:131:131
> > >> spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
> > >> snotr.com 2a00:d00:ff:131:94:228:131:131
> > >> maxconsole.net 2a00:d00:ff:131:94:228:131:131
> > >> geenstijl.tv 2a00:d00:ff:131:94:228:131:131
> > >> www.gamershell.com 2a00:d00:ff:131:94:228:131:131
> > >
> > > [...etc... you get the picture]
> > >
> > > JFYI: these are all AAAA records pointing to an IPv6-to-IPv4
> > proxy. The
> > > actual sites themselves don't have native IPv6 connectivity.
> > >
> > > daniel at daniel:~$ dig -x 2a00:d00:ff:131:94:228:131:131 +short
> > > ipv6proxy.prolocation.net.
> > 
> > Yep, and if you look closely at the others listed you'll find other
> > anomalous entries that either indicate interesting transitional
> > choices
> > or outright mistakes.  If notice something like that and know any of
> > the
> > people involved you might make a polite inquiry.
> > 
> > In any case, AAAA records are getting added for major websites.
> > 
> > Mike.
> > 
> > 
> > ------------------------------
> > 
> > _______________________________________________
> > ipv6-ops mailing list
> > ipv6-ops at lists.cluenet.de
> > http://lists.cluenet.de/mailman/listinfo/ipv6-ops
> > 
> > 
> > End of ipv6-ops Digest, Vol 56, Issue 6
> > ***************************************
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20091117/e1911749/attachment.bin 

From trejrco at gmail.com  Tue Nov 17 14:26:23 2009
From: trejrco at gmail.com (TJ)
Date: Tue, 17 Nov 2009 08:26:23 -0500
Subject: ipv6-ops Digest, Vol 56, Issue 6
In-Reply-To: <1258460808.14441.14.camel@otto>
References: <mailman.1.1258455601.4685.ipv6-ops@lists.cluenet.de>	
	<71bfd60c0911170413t63ba0565j452628ea1bf2304c@mail.gmail.com>	
	<71bfd60c0911170416n1aa635a3t232fb0b90d236859@mail.gmail.com>
	<1258460808.14441.14.camel@otto>
Message-ID: <00f601ca6789$9567aaa0$c036ffe0$@com>

> -----Original Message-----
> From: Matt Ryanczak [mailto:ryanczak at arin.net]
> Sent: Tuesday, November 17, 2009 07:27
> To: trejrco at gmail.com
> Cc: ipv6-ops at lists.cluenet.de
> Subject: Re: ipv6-ops Digest, Vol 56, Issue 6
> 
> My guess is that they come from the same consultant that set up both of those
> edu sites.

Probably a reasonable guess.  Bad enough to do it that way, but to then put those entries is outside-facing DNS, thus encouraging connectivity problems/delays for the rest of the world.  "Awesome."  (Atleast the 6to4-based addresses _can_ work)

/TJ



> On Tue, 2009-11-17 at 07:16 -0500, TJ wrote:
> > Where do the 192:192:168:168:1:1:1:1 come from?  What builds an IPv6
> > address this way from its IPv4 (rfc1918) addr and why??
> >
> > > On Nov 17, 2009 6:00 AM, <ipv6-ops-request at lists.cluenet.de> wrote:
> > >
> > > Send ipv6-ops mailing list submissions to
> > >        ipv6-ops at lists.cluenet.de
> > >
> > > To subscribe or unsubscribe via the World Wide Web, visit
> > >        http://lists.cluenet.de/mailman/listinfo/ipv6-ops
> > > or, via email, send a message with subject or body 'help' to
> > >        ipv6-ops-request at lists.cluenet.de
> > >
> > > You can reach the person managing the list at
> > >        ipv6-ops-owner at lists.cluenet.de
> > >
> > > When replying, please edit your Subject line so it is more specific
> > > than "Re: Contents of ipv6-ops digest..."
> > >
> > >
> > > Today's Topics:
> > >
> > >   1. Top Websites Running IPv6 (Mike Leber)
> > >   2. Re: Top Websites Running IPv6 (Daniel Verlouw)
> > >   3. Re: Top Websites Running IPv6 (Mike Leber)
> > >
> > >
> > > --------------------------------------------------------------------
> > > --
> > >
> > > Message: 1
> > > Date: Tue, 17 Nov 2009 02:18:07 -0800
> > > From: Mike Leber <mleber at he.net>
> > > Subject: Top Websites Running IPv6
> > > To: ipv6-ops at lists.cluenet.de
> > > Message-ID: <4B02785F.8030402 at he.net>
> > > Content-Type: text/plain; charset=ISO-8859-15; format=flowed
> > >
> > >
> > > I updated the report that we run at
> > > http://bgp.he.net/ipv6-progress-report.cgi to check the Alexa top 1
> > > million websites.  We now also check www. and ipv6. for each domain
> > > as well.  It reveals that quite a few major websites have either
> > > added AAAA records for their main website or are testing ipv6 at an
> > > ipv6.
> > > subdomain.
> > >
> > > Below is copy of the new section for your entertainment.
> > >
> > > Mike.
> > > ---
> > >
> > > Top Websites Running IPv6
> > > A very quick way to measure IPv6 deployment for websites is just to
> > > check for a AAAA record in DNS.
> > >
> > > Alexa provides an approximate list of the most popular sites on the
> > > web.
> > >
> > > In the report below, the raw domain is the base domain, such as
> > > free.fr, which does not have an AAAA record (at the time of this
> > > writing).
> > > However www.free.fr *does* have a AAAA record. So we check both.
> > >
> > > Another convention is to add an AAAA using ipv6 as a subdomain, i.e.
> > > ipv6.google.com. The reason so many domains show up as having A
> > > records for "ipv6." subdomains is because many domains use wildcard
> > > records in DNS which respond to queries for any subdomain.
> > >
> > > Alexa Top 1 Million Domains Downloaded: Sat Nov 14 21:47:15 2009
> > > Alexa Top 1 Million Domains Processed: Sat Nov 14 22:25:51 2009
> > >
> > > Alexa 1M raw domains: 1000000
> > > Alexa 1M raw with a direct IPv4 address: 924219 Alexa 1M raw with a
> > > direct IPv6 address: 1441
> > >
> > > (top 50)
> > > ucla.edu 2607:f010:3fe:201:101d:9ff:fe32:adee
> > > tribune.com 2002:a3c0:1712::a3c0:1712 internic.net 2620:0:2d0:200::9
> > > freebsd.org 2001:4f8:fff6::28 gamershell.com
> > > 2a00:d00:ff:131:94:228:131:131 monash.edu.au 2001:388:608c:c91::117
> > > animesuki.com 2001:4d88:ffff:ffff:30:524:ac23:2 koreus.com
> > > 2001:41d0:2:4133::1 geenstijl.nl 2a00:d00:ff:131:94:228:131:131
> > > python.org 2001:888:2000:d::a2 filezilla-project.org
> > > 2a01:198:200:5b7::2 spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
> > > kino.de 2001:a60:9003:a000::b004 torrentfreak.com 2607:f128:40::174
> > > ripe.net 2001:610:240:11::c100:1319 fedoraproject.org
> > > 2610:28:200:1::fed0:1 cyberciti.biz 2607:f0d0:1002:11::4
> > > hentai-foundry.com 2607:f0d0:1003:c::30 keenspot.com
> > > 2001:470:1:3a::13 snotr.com 2a00:d00:ff:131:94:228:131:131 icann.org
> > > 2620:0:2d0:200::7 crooksandliars.com
> > > 2001:470:a068:1:230:48ff:fe98:d1a8
> > > softlayer.com 2607:f0d0:1000:11:1::2 itb.ac.id 2001:d30:3::22
> > > infomaniak.ch 2001:1600:3:7::101 bayimg.com 2a01:298:3:1:1337::13
> > > comicgenesis.com 2001:470:1:3a::14 steadfast.net 2607:f128::2
> > > mediabiz.de 2001:a60:9003:a000::b00d pastebin.ca
> > > 2610:1e8:2:20::e8b8:97 stream.ru 2a02:28:2::1076 weeronline.nl
> > > 2001:888:30af::206:85 maxconsole.net 2a00:d00:ff:131:94:228:131:131
> > > he.net 2001:470:0:76::2 fernuni-hagen.de 2002:84b0:8101::84b0:8101
> > > exchangecash.de 6563:6173:6802:6465:0:1c00:100:0 pcc.edu
> > > 192:192:168:168:1:1:1:1 sify.com 2001:e48:0:10::10 iana.org
> > > 2620:0:2d0:1::193 torrentbits.ro 2001:4d18:0:1::32 geenstijl.tv
> > > 2a00:d00:ff:131:94:228:131:131 starlink.ru 2a00:e78::7 netbynet.ru
> > > 2a00:d18:f00d:d401:fe0b:101:0:67 rcts.pt 2001:690:a00:1036:804::111
> > > cbn.net.id 2001:d10:2:80::80 liu.se 2001:6b0:17:f005::148
> > > phoenixlabs.org 2001:0:53aa:64c:4cc:2161:b717:a85 ubuntu.ru
> > > 2001:780:0:25:206:5bff:fe04:8bcb luc.edu 192:192:168:168:1:1:1:1
> > > menagea3.net 2001:470:1:3a::13
> > >
> > > www. + Alexa 1M domains: 1000000
> > > www. + Alexa 1M with a direct IPv4 address: 970789 www. + Alexa 1M
> > > with a direct IPv6 address: 1904
> > >
> > > (top 50)
> > > www.ucla.edu 2607:f010:3fe:301:101d:9ff:fe32:a7db
> > > www.sakura.ne.jp 2001:e40:100:407::d2e0:ac35 www.free.fr
> > > 2a01:e0c:1:1599::1 www.doctissimo.fr 2a01:7b0:2:3::26 www.dti.ne.jp
> > > 2001:2e8:22:13::103 www.odn.ne.jp 2001:278:0:1106::4
> > > www.leaseweb.com 2001:1af8:3100:1:214:22ff:fe1e:d380
> > > www.ripe.net 2001:610:240:11::c100:1319 www.monash.edu.au
> > > 2001:388:608c:c91::117 www.kddi.com 2001:268:fd02::1
> > > www.gamershell.com 2a00:d00:ff:131:94:228:131:131 www.freebsd.org
> > > 2001:4f8:fff6::21 www.internic.net 2620:0:2d0:200::9 www.koreus.com
> > > 2001:41d0:2:4136::1 www.animesuki.com
> > > 2001:4d88:ffff:ffff:30:524:ac23:2 www.geenstijl.nl
> > > 2a00:d00:ff:131:94:228:131:131 www.kino.de 2001:a60:9003:a000::b003
> > > www.spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
> > > www.torrentfreak.com 2607:f128:40::174 www.tvrage.com
> > > 2a02:898::110:1 www.rmc.fr 2001:41d0:1:7b1f::1 www.snotr.com
> > > 2a00:d00:ff:131:94:228:131:131 www.ulaval.ca
> > > 2620:0:1af0:144:ffff::fff2 www.fedoraproject.org
> > > 2610:28:200:1::fed0:1 www.icann.org 2620:0:2d0:200::7 www.spele.nl
> > > 2a00:f80::10 www.ietf.org 2001:1890:1112:1::20 www.arin.net
> > > 2001:500:4:13::81 www.hentai-foundry.com 2607:f0d0:1003:c::30
> > > www.k12.pa.us 2001:5e8:0:1000::fc www.keenspot.com 2001:470:1:3a::13
> > > www.comicgenesis.com 2001:470:1:3a::14 www.01net.com
> > > 2001:41d0:1:118::1 www.hitachi.co.jp 2001:240:400::8591:e013
> > > www.iastate.edu 2610:130:101:102::f0 www.cuhk.edu.hk
> > > 2405:3000:3:b0:137:189:11:71 www.ntua.gr 2001:648:2000:de::210
> > > www.rtbf.be 2001:1600:3:6::101 www.nta.go.jp
> > > 2001:c80:a001:1::cad9:2c8f www.up.pt 2001:690:2200:a10::13
> > > www.cyberciti.biz 2607:f0d0:1002:11::4 www.steadfast.net
> > > 2607:f128::2 www.infomaniak.ch 2001:1600:3:7::101 www.softlayer.com
> > > 2607:f0d0:1000:11:1::1 www.maine.edu 2610:48:100:820::103
> > > www.univie.ac.at 2001:62a:4:1::80:108 www.itb.ac.id 2001:d30:3::22
> > > www.upc.edu 2001:40b0:7500:1::21 www.liu.se 2001:6b0:17:f005::148
> > > www.nnm-club.ru 2001:470:1f0a:1505::2
> > >
> > > ipv6. + Alexa 1M domains: 1000000
> > > ipv6. + Alexa 1M with a direct IPv4 address: 243852
> > > ipv6. + Alexa 1M with a direct IPv6 address: 1031
> > >
> > > (top 50)
> > > ipv6.netflix.com 2620:0:ef0:13::20
> > > ipv6.2ch.net 2407:3000:6:175::12
> > > ipv6.comcast.net 2001:558:1002:5:68:87:64:48
> > > ipv6.google.com 2001:4860:b004::68
> > > ipv6.google.co.jp 2001:4860:b002::68
> > > ipv6.berkeley.edu 2607:f140:ffff:ffff::80
> > > ipv6.zerolag.com 2001:470:1e::9
> > > ipv6.seznam.cz 2a02:598:1::101
> > > ipv6.21cn.com 2042:8800:1::3
> > > ipv6.denic.de 2001:608:6::1
> > > ipv6.iwiw.hu 2001:4c48:2:a::1
> > > ipv6.freemail.hu 2001:4c48:2:f::100
> > > ipv6.bt.com 2002:c171:3a71::1
> > > ipv6.pku.edu.cn 2001:da8:201:1129:203:baff:fe2f:163c
> > > ipv6.sony.co.jp 2001:cf8:0:6b::190
> > > ipv6.df.eu 2a00:1158:0:100::3
> > > ipv6.koreus.com 2001:41d0:2:4233::1
> > > ipv6.vt.edu 2001:468:c80:210f:0:1c6:1a85:8564
> > > ipv6.tsinghua.edu.cn 2001:da8:1:100::80
> > > ipv6.24ur.com 2001:6f8:919::1
> > > ipv6.dyndns.com 2607:f590:0:ffff::29
> > > ipv6.gatech.edu 2001:468:300:ee01:a00:2bff:fec4:4e8e
> > > ipv6.gazeta.pl 2a02:bd8:1::50fc:91
> > > ipv6.italiansubs.net 2001:41d0:1:8364::1
> > > ipv6.monash.edu.au 2001:388:608c:c91::117
> > > ipv6.bsnl.co.in 2001:4490:100:ff:3::
> > > ipv6.hopto.org 2001:470:8:145::1
> > > ipv6.sify.com 2001:e48:0:6::5
> > > ipv6.spoluzaci.cz 2a02:598:1::102
> > > ipv6.twbbs.org 2001:e10:6840:20:20f:eaff:fe56:ea22
> > > ipv6.peta.org 2001:4978:f:36f::2
> > > ipv6.afraid.org 2001:470:d19b::203
> > > ipv6.ku.ac.th 2001:3c8:1303:1125::18
> > > ipv6.ovh.com 2001:41d0:1:10::d5ba:2122
> > > ipv6.comicgenesis.com 2001:470:1:3a::14
> > > ipv6.eircom.net 2001:bb0:dd0::2
> > > ipv6.atw.hu 2a01:270::4
> > > ipv6.unm.edu 3ffe:2900:11:10::1
> > > ipv6.rtvslo.si 2a02:7a8:0:1::80:1
> > > ipv6.itb.ac.id 2001:d30:3::19
> > > ipv6.sjtu.edu.cn 2001:da8:8000:1::80
> > > ipv6.weeronline.nl 2001:888:30af::206:87
> > > ipv6.infomaniak.ch 2001:1600::ffff
> > > ipv6.nnm-club.ru 2001:470:1f0a:1505::2
> > > ipv6.lsu.edu 2620:0:da0:f001::7
> > > ipv6.iana.org 2620:0:2d0:1::194
> > > ipv6.trueinternet.co.th 2001:fb0:100:1:58:97:5:30
> > > ipv6.gsa.gov 2620:0:150:ffad::5
> > > ipv6.spele.nl 2a00:f80::10
> > > ipv6.uni-erlangen.de 2001:638:a00:2::2
> > >
> > >
> > > ------------------------------
> > >
> > > Message: 2
> > > Date: Tue, 17 Nov 2009 11:42:08 +0100
> > > From: Daniel Verlouw <daniel at bit.nl>
> > > Subject: Re: Top Websites Running IPv6
> > > To: Mike Leber <mleber at he.net>
> > > Cc: ipv6-ops at lists.cluenet.de
> > > Message-ID: <1258454528.13409.10.camel at daniel.office.bit.nl>
> > > Content-Type: text/plain
> > >
> > > On Tue, 2009-11-17 at 02:18 -0800, Mike Leber wrote:
> > > > gamershell.com 2a00:d00:ff:131:94:228:131:131
> > > > geenstijl.nl 2a00:d00:ff:131:94:228:131:131
> > > > spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
> > > > snotr.com 2a00:d00:ff:131:94:228:131:131
> > > > maxconsole.net 2a00:d00:ff:131:94:228:131:131
> > > > geenstijl.tv 2a00:d00:ff:131:94:228:131:131
> > > > www.gamershell.com 2a00:d00:ff:131:94:228:131:131
> > >
> > > [...etc... you get the picture]
> > >
> > > JFYI: these are all AAAA records pointing to an IPv6-to-IPv4 proxy.
> > > The
> > > actual sites themselves don't have native IPv6 connectivity.
> > >
> > > daniel at daniel:~$ dig -x 2a00:d00:ff:131:94:228:131:131 +short
> > > ipv6proxy.prolocation.net.
> > >
> > >   --Daniel.
> > >
> > >
> > >
> > > ------------------------------
> > >
> > > Message: 3
> > > Date: Tue, 17 Nov 2009 02:50:19 -0800
> > > From: Mike Leber <mleber at he.net>
> > > Subject: Re: Top Websites Running IPv6
> > > To: Daniel Verlouw <daniel at bit.nl>
> > > Cc: ipv6-ops at lists.cluenet.de
> > > Message-ID: <4B027FEB.6020503 at he.net>
> > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> > >
> > >
> > > Daniel Verlouw wrote:
> > > > On Tue, 2009-11-17 at 02:18 -0800, Mike Leber wrote:
> > > >> gamershell.com 2a00:d00:ff:131:94:228:131:131
> > > >> geenstijl.nl 2a00:d00:ff:131:94:228:131:131
> > > >> spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
> > > >> snotr.com 2a00:d00:ff:131:94:228:131:131
> > > >> maxconsole.net 2a00:d00:ff:131:94:228:131:131
> > > >> geenstijl.tv 2a00:d00:ff:131:94:228:131:131
> > > >> www.gamershell.com 2a00:d00:ff:131:94:228:131:131
> > > >
> > > > [...etc... you get the picture]
> > > >
> > > > JFYI: these are all AAAA records pointing to an IPv6-to-IPv4
> > > proxy. The
> > > > actual sites themselves don't have native IPv6 connectivity.
> > > >
> > > > daniel at daniel:~$ dig -x 2a00:d00:ff:131:94:228:131:131 +short
> > > > ipv6proxy.prolocation.net.
> > >
> > > Yep, and if you look closely at the others listed you'll find other
> > > anomalous entries that either indicate interesting transitional
> > > choices
> > > or outright mistakes.  If notice something like that and know any of
> > > the
> > > people involved you might make a polite inquiry.
> > >
> > > In any case, AAAA records are getting added for major websites.
> > >
> > > Mike.
> > >
> > >
> > > ------------------------------
> > >
> > > _______________________________________________
> > > ipv6-ops mailing list
> > > ipv6-ops at lists.cluenet.de
> > > http://lists.cluenet.de/mailman/listinfo/ipv6-ops
> > >
> > >
> > > End of ipv6-ops Digest, Vol 56, Issue 6
> > > ***************************************
> >



From Chris at 7of9b.org  Tue Nov 17 15:31:05 2009
From: Chris at 7of9b.org (Chris Burton)
Date: Tue, 17 Nov 2009 14:31:05 -0000
Subject: ipv6-ops Digest, Vol 56, Issue 6
References: <mailman.1.1258455601.4685.ipv6-ops@lists.cluenet.de>	<71bfd60c0911170413t63ba0565j452628ea1bf2304c@mail.gmail.com>	<71bfd60c0911170416n1aa635a3t232fb0b90d236859@mail.gmail.com><1258460808.14441.14.camel@otto>
	<00f601ca6789$9567aaa0$c036ffe0$@com>
Message-ID: <2B123886E1B149758654CEA18A3F1EF1@murphy1>

>> My guess is that they come from the same consultant that set up both of 
>> those
>> edu sites.
>
> Probably a reasonable guess. <snip>

I can see a few others with an AAAA of 192:192:168:168:1:1:1:1 so it's not 
just a couple of .edu.

http://dnshistory.org/linksto/aaaa/1.0.0.0.1.0.0.0.1.0.0.0.1.0.0.0.8.6.1.0.8.6.1.0.2.9.1.0.2.9.1.0.ip6.arpa.

ChrisB. 


From michael.dillon at bt.com  Tue Nov 17 17:26:37 2009
From: michael.dillon at bt.com (michael.dillon at bt.com)
Date: Tue, 17 Nov 2009 16:26:37 -0000
Subject: ipv6-ops Digest, Vol 56, Issue 6
In-Reply-To: <71bfd60c0911170416n1aa635a3t232fb0b90d236859@mail.gmail.com>
Message-ID: <28E139F46D45AF49A31950F88C497458041A7C16@E03MVZ2-UKDY.domain1.systemhost.net>

> Where do the 192:192:168:168:1:1:1:1 come from?  What builds 
> an IPv6 address this way from its IPv4 (rfc1918) addr and why??

Sites running SUSE Linux.
Read this Technical Information Document from Novell for more info
<http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&ex
ternalId=10074602&sliceId=&docTypeID=DT_TID_1_1&dialogID=102635143&state
Id=0%200%20102633339>

Or you can go to this URL
<http://www.novell.com/support/microsites/microsite.do>,
type in 10074602 and press the search button.

I guess someone thought that if IPv6 addresses are longer than IPv4
ones, the private addresses are just the same numbers doubled to make
them longer ;-)

Given that it is Novell and commercially supported software, it might be
possible to get them to issue a bulletin to all customers to get this
corrected and teach them about ULA addresses.

--Michael Dillon.

From dwing at cisco.com  Tue Nov 17 19:03:44 2009
From: dwing at cisco.com (Dan Wing)
Date: Tue, 17 Nov 2009 10:03:44 -0800
Subject: Top Websites Running IPv6
In-Reply-To: <4B02785F.8030402@he.net>
References: <4B02785F.8030402@he.net>
Message-ID: <037701ca67b0$4dd76ff0$c2f0200a@cisco.com>

 

> -----Original Message-----
> From: ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de 
> [mailto:ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de] On 
> Behalf Of Mike Leber
> Sent: Tuesday, November 17, 2009 2:18 AM
> To: ipv6-ops at lists.cluenet.de
> Subject: Top Websites Running IPv6
> 
> 
> I updated the report that we run at 
> http://bgp.he.net/ipv6-progress-report.cgi to check the Alexa top 1 
> million websites.  We now also check www. and ipv6. for each 
> domain as 
> well.  It reveals that quite a few major websites have either 
> added AAAA 
> records for their main website or are testing ipv6 at an 
> ipv6. subdomain.
> 
> Below is copy of the new section for your entertainment.

Thanks.

You might also try connecting to port 80 of those sites.  Afterall,
if they were on Alexa's top-one million list yesterday they should
be listening on port 80.

>From the information currently posted at
http://bgp.he.net/ipv6-progress-report.cgi, I found the following sites didn't
accept connections to port 80 via their AAAA records:

die.net                        2607:f820:42::4 (failed)
netbynet.ru                    2a00:d18:f00d:d401:fe0b:101:0:67 (failed)
luc.edu                        192:192:168:168:1:1:1:1 (failed)
pcc.edu                        192:192:168:168:1:1:1:1 (failed)
bayimg.com                     2a01:298:3:1:1337::13 (failed)
tribune.com                    2002:a3c0:1712::a3c0:1712 (failed)
proua.com                      2a01:d0::10:1 (failed)
worldofwatches.com             2002:4087:6747:: (failed)
essex.ac.uk                    2002:9bf5:305e::9bf5:305e (failed)
fernuni-hagen.de               2002:84b0:8102::84b0:8102 (failed),
2002:84b0:8101::84b0:8101 (failed)

I noticed that essex.ac.uk was failing for IPv4, too, so they might be having
a site outage at the moment.  The others, however ...

-d

> Mike.
> ---
> 
> Top Websites Running IPv6
> A very quick way to measure IPv6 deployment for websites is just to
> check for a AAAA record in DNS.
> 
> Alexa provides an approximate list of the most popular sites 
> on the web.
> 
> In the report below, the raw domain is the base domain, such 
> as free.fr,
> which does not have an AAAA record (at the time of this writing). 
> However www.free.fr *does* have a AAAA record. So we check both.
> 
> Another convention is to add an AAAA using ipv6 as a subdomain, i.e.
> ipv6.google.com. The reason so many domains show up as having 
> A records
> for "ipv6." subdomains is because many domains use wildcard records in
> DNS which respond to queries for any subdomain.
> 
> Alexa Top 1 Million Domains Downloaded: Sat Nov 14 21:47:15 2009
> Alexa Top 1 Million Domains Processed: Sat Nov 14 22:25:51 2009
> 
> Alexa 1M raw domains: 1000000
> Alexa 1M raw with a direct IPv4 address: 924219
> Alexa 1M raw with a direct IPv6 address: 1441
> 
> (top 50)
> ucla.edu 2607:f010:3fe:201:101d:9ff:fe32:adee
> tribune.com 2002:a3c0:1712::a3c0:1712
> internic.net 2620:0:2d0:200::9
> freebsd.org 2001:4f8:fff6::28
> gamershell.com 2a00:d00:ff:131:94:228:131:131
> monash.edu.au 2001:388:608c:c91::117
> animesuki.com 2001:4d88:ffff:ffff:30:524:ac23:2
> koreus.com 2001:41d0:2:4133::1
> geenstijl.nl 2a00:d00:ff:131:94:228:131:131
> python.org 2001:888:2000:d::a2
> filezilla-project.org 2a01:198:200:5b7::2
> spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
> kino.de 2001:a60:9003:a000::b004
> torrentfreak.com 2607:f128:40::174
> ripe.net 2001:610:240:11::c100:1319
> fedoraproject.org 2610:28:200:1::fed0:1
> cyberciti.biz 2607:f0d0:1002:11::4
> hentai-foundry.com 2607:f0d0:1003:c::30
> keenspot.com 2001:470:1:3a::13
> snotr.com 2a00:d00:ff:131:94:228:131:131
> icann.org 2620:0:2d0:200::7
> crooksandliars.com 2001:470:a068:1:230:48ff:fe98:d1a8
> softlayer.com 2607:f0d0:1000:11:1::2
> itb.ac.id 2001:d30:3::22
> infomaniak.ch 2001:1600:3:7::101
> bayimg.com 2a01:298:3:1:1337::13
> comicgenesis.com 2001:470:1:3a::14
> steadfast.net 2607:f128::2
> mediabiz.de 2001:a60:9003:a000::b00d
> pastebin.ca 2610:1e8:2:20::e8b8:97
> stream.ru 2a02:28:2::1076
> weeronline.nl 2001:888:30af::206:85
> maxconsole.net 2a00:d00:ff:131:94:228:131:131
> he.net 2001:470:0:76::2
> fernuni-hagen.de 2002:84b0:8101::84b0:8101
> exchangecash.de 6563:6173:6802:6465:0:1c00:100:0
> pcc.edu 192:192:168:168:1:1:1:1
> sify.com 2001:e48:0:10::10
> iana.org 2620:0:2d0:1::193
> torrentbits.ro 2001:4d18:0:1::32
> geenstijl.tv 2a00:d00:ff:131:94:228:131:131
> starlink.ru 2a00:e78::7
> netbynet.ru 2a00:d18:f00d:d401:fe0b:101:0:67
> rcts.pt 2001:690:a00:1036:804::111
> cbn.net.id 2001:d10:2:80::80
> liu.se 2001:6b0:17:f005::148
> phoenixlabs.org 2001:0:53aa:64c:4cc:2161:b717:a85
> ubuntu.ru 2001:780:0:25:206:5bff:fe04:8bcb
> luc.edu 192:192:168:168:1:1:1:1
> menagea3.net 2001:470:1:3a::13
> 
> www. + Alexa 1M domains: 1000000
> www. + Alexa 1M with a direct IPv4 address: 970789
> www. + Alexa 1M with a direct IPv6 address: 1904
> 
> (top 50)
> www.ucla.edu 2607:f010:3fe:301:101d:9ff:fe32:a7db
> www.sakura.ne.jp 2001:e40:100:407::d2e0:ac35
> www.free.fr 2a01:e0c:1:1599::1
> www.doctissimo.fr 2a01:7b0:2:3::26
> www.dti.ne.jp 2001:2e8:22:13::103
> www.odn.ne.jp 2001:278:0:1106::4
> www.leaseweb.com 2001:1af8:3100:1:214:22ff:fe1e:d380
> www.ripe.net 2001:610:240:11::c100:1319
> www.monash.edu.au 2001:388:608c:c91::117
> www.kddi.com 2001:268:fd02::1
> www.gamershell.com 2a00:d00:ff:131:94:228:131:131
> www.freebsd.org 2001:4f8:fff6::21
> www.internic.net 2620:0:2d0:200::9
> www.koreus.com 2001:41d0:2:4136::1
> www.animesuki.com 2001:4d88:ffff:ffff:30:524:ac23:2
> www.geenstijl.nl 2a00:d00:ff:131:94:228:131:131
> www.kino.de 2001:a60:9003:a000::b003
> www.spitsnieuws.nl 2a00:d00:ff:131:94:228:131:131
> www.torrentfreak.com 2607:f128:40::174
> www.tvrage.com 2a02:898::110:1
> www.rmc.fr 2001:41d0:1:7b1f::1
> www.snotr.com 2a00:d00:ff:131:94:228:131:131
> www.ulaval.ca 2620:0:1af0:144:ffff::fff2
> www.fedoraproject.org 2610:28:200:1::fed0:1
> www.icann.org 2620:0:2d0:200::7
> www.spele.nl 2a00:f80::10
> www.ietf.org 2001:1890:1112:1::20
> www.arin.net 2001:500:4:13::81
> www.hentai-foundry.com 2607:f0d0:1003:c::30
> www.k12.pa.us 2001:5e8:0:1000::fc
> www.keenspot.com 2001:470:1:3a::13
> www.comicgenesis.com 2001:470:1:3a::14
> www.01net.com 2001:41d0:1:118::1
> www.hitachi.co.jp 2001:240:400::8591:e013
> www.iastate.edu 2610:130:101:102::f0
> www.cuhk.edu.hk 2405:3000:3:b0:137:189:11:71
> www.ntua.gr 2001:648:2000:de::210
> www.rtbf.be 2001:1600:3:6::101
> www.nta.go.jp 2001:c80:a001:1::cad9:2c8f
> www.up.pt 2001:690:2200:a10::13
> www.cyberciti.biz 2607:f0d0:1002:11::4
> www.steadfast.net 2607:f128::2
> www.infomaniak.ch 2001:1600:3:7::101
> www.softlayer.com 2607:f0d0:1000:11:1::1
> www.maine.edu 2610:48:100:820::103
> www.univie.ac.at 2001:62a:4:1::80:108
> www.itb.ac.id 2001:d30:3::22
> www.upc.edu 2001:40b0:7500:1::21
> www.liu.se 2001:6b0:17:f005::148
> www.nnm-club.ru 2001:470:1f0a:1505::2
> 
> ipv6. + Alexa 1M domains: 1000000
> ipv6. + Alexa 1M with a direct IPv4 address: 243852
> ipv6. + Alexa 1M with a direct IPv6 address: 1031
> 
> (top 50)
> ipv6.netflix.com 2620:0:ef0:13::20
> ipv6.2ch.net 2407:3000:6:175::12
> ipv6.comcast.net 2001:558:1002:5:68:87:64:48
> ipv6.google.com 2001:4860:b004::68
> ipv6.google.co.jp 2001:4860:b002::68
> ipv6.berkeley.edu 2607:f140:ffff:ffff::80
> ipv6.zerolag.com 2001:470:1e::9
> ipv6.seznam.cz 2a02:598:1::101
> ipv6.21cn.com 2042:8800:1::3
> ipv6.denic.de 2001:608:6::1
> ipv6.iwiw.hu 2001:4c48:2:a::1
> ipv6.freemail.hu 2001:4c48:2:f::100
> ipv6.bt.com 2002:c171:3a71::1
> ipv6.pku.edu.cn 2001:da8:201:1129:203:baff:fe2f:163c
> ipv6.sony.co.jp 2001:cf8:0:6b::190
> ipv6.df.eu 2a00:1158:0:100::3
> ipv6.koreus.com 2001:41d0:2:4233::1
> ipv6.vt.edu 2001:468:c80:210f:0:1c6:1a85:8564
> ipv6.tsinghua.edu.cn 2001:da8:1:100::80
> ipv6.24ur.com 2001:6f8:919::1
> ipv6.dyndns.com 2607:f590:0:ffff::29
> ipv6.gatech.edu 2001:468:300:ee01:a00:2bff:fec4:4e8e
> ipv6.gazeta.pl 2a02:bd8:1::50fc:91
> ipv6.italiansubs.net 2001:41d0:1:8364::1
> ipv6.monash.edu.au 2001:388:608c:c91::117
> ipv6.bsnl.co.in 2001:4490:100:ff:3::
> ipv6.hopto.org 2001:470:8:145::1
> ipv6.sify.com 2001:e48:0:6::5
> ipv6.spoluzaci.cz 2a02:598:1::102
> ipv6.twbbs.org 2001:e10:6840:20:20f:eaff:fe56:ea22
> ipv6.peta.org 2001:4978:f:36f::2
> ipv6.afraid.org 2001:470:d19b::203
> ipv6.ku.ac.th 2001:3c8:1303:1125::18
> ipv6.ovh.com 2001:41d0:1:10::d5ba:2122
> ipv6.comicgenesis.com 2001:470:1:3a::14
> ipv6.eircom.net 2001:bb0:dd0::2
> ipv6.atw.hu 2a01:270::4
> ipv6.unm.edu 3ffe:2900:11:10::1
> ipv6.rtvslo.si 2a02:7a8:0:1::80:1
> ipv6.itb.ac.id 2001:d30:3::19
> ipv6.sjtu.edu.cn 2001:da8:8000:1::80
> ipv6.weeronline.nl 2001:888:30af::206:87
> ipv6.infomaniak.ch 2001:1600::ffff
> ipv6.nnm-club.ru 2001:470:1f0a:1505::2
> ipv6.lsu.edu 2620:0:da0:f001::7
> ipv6.iana.org 2620:0:2d0:1::194
> ipv6.trueinternet.co.th 2001:fb0:100:1:58:97:5:30
> ipv6.gsa.gov 2620:0:150:ffad::5
> ipv6.spele.nl 2a00:f80::10
> ipv6.uni-erlangen.de 2001:638:a00:2::2


From mleber at he.net  Tue Nov 17 20:26:09 2009
From: mleber at he.net (Mike Leber)
Date: Tue, 17 Nov 2009 11:26:09 -0800
Subject: Top Websites Running IPv6
In-Reply-To: <037701ca67b0$4dd76ff0$c2f0200a@cisco.com>
References: <4B02785F.8030402@he.net>
	<037701ca67b0$4dd76ff0$c2f0200a@cisco.com>
Message-ID: <4B02F8D1.2080308@he.net>


Dan Wing wrote:
>> -----Original Message-----
>> From: ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de 
>> [mailto:ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de] On 
>> Behalf Of Mike Leber
>> Sent: Tuesday, November 17, 2009 2:18 AM
>> To: ipv6-ops at lists.cluenet.de
>> Subject: Top Websites Running IPv6
>>
>>
>> I updated the report that we run at 
>> http://bgp.he.net/ipv6-progress-report.cgi to check the Alexa top 1 
>> million websites.  We now also check www. and ipv6. for each 
>> domain as 
>> well.  It reveals that quite a few major websites have either 
>> added AAAA 
>> records for their main website or are testing ipv6 at an 
>> ipv6. subdomain.
>>
>> Below is copy of the new section for your entertainment.
> 
> Thanks.
> 
> You might also try connecting to port 80 of those sites.  Afterall,
> if they were on Alexa's top-one million list yesterday they should
> be listening on port 80.

Yep, that is a great idea and we will add an HTTP survey in the near future.

> From the information currently posted at
> http://bgp.he.net/ipv6-progress-report.cgi, I found the following sites didn't
> accept connections to port 80 via their AAAA records:
> 
> die.net                        2607:f820:42::4 (failed)
> netbynet.ru                    2a00:d18:f00d:d401:fe0b:101:0:67 (failed)
> luc.edu                        192:192:168:168:1:1:1:1 (failed)
> pcc.edu                        192:192:168:168:1:1:1:1 (failed)
> bayimg.com                     2a01:298:3:1:1337::13 (failed)
> tribune.com                    2002:a3c0:1712::a3c0:1712 (failed)
> proua.com                      2a01:d0::10:1 (failed)
> worldofwatches.com             2002:4087:6747:: (failed)
> essex.ac.uk                    2002:9bf5:305e::9bf5:305e (failed)
> fernuni-hagen.de               2002:84b0:8102::84b0:8102 (failed),
> 2002:84b0:8101::84b0:8101 (failed)
> 
> I noticed that essex.ac.uk was failing for IPv4, too, so they might be having
> a site outage at the moment.  The others, however ...

And now that they have added AAAA records and some sites are reporting 1 
percent of accesses coming in via IPv6 (ripe for example) they have a 
vested interest in fixing it so that their site works correctly.

I suppose this reveals that there is a lack of production web site 
monitoring in IPv6 land, hmmmm opportunity??? ;)

I'm alluding to the SaaS model of pingdom, webmetrics, and panopta.  Not 
"can you configure cacti etc" since I know you can! :)

Mike.

From dwing at cisco.com  Tue Nov 17 20:35:41 2009
From: dwing at cisco.com (Dan Wing)
Date: Tue, 17 Nov 2009 11:35:41 -0800
Subject: Top Websites Running IPv6
In-Reply-To: <4B02F8D1.2080308@he.net>
References: <4B02785F.8030402@he.net><037701ca67b0$4dd76ff0$c2f0200a@cisco.com>
	<4B02F8D1.2080308@he.net>
Message-ID: <045201ca67bd$260b11e0$c2f0200a@cisco.com>

 

> -----Original Message-----
> From: ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de 
> [mailto:ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de] On 
> Behalf Of Mike Leber
> Sent: Tuesday, November 17, 2009 11:26 AM
> To: Dan Wing
> Cc: ipv6-ops at lists.cluenet.de
> Subject: Re: Top Websites Running IPv6
> 
> 
> Dan Wing wrote:
> >> -----Original Message-----
> >> From: ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de 
> >> [mailto:ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de] On 
> >> Behalf Of Mike Leber
> >> Sent: Tuesday, November 17, 2009 2:18 AM
> >> To: ipv6-ops at lists.cluenet.de
> >> Subject: Top Websites Running IPv6
> >>
> >>
> >> I updated the report that we run at 
> >> http://bgp.he.net/ipv6-progress-report.cgi to check the 
> Alexa top 1 
> >> million websites.  We now also check www. and ipv6. for each 
> >> domain as 
> >> well.  It reveals that quite a few major websites have either 
> >> added AAAA 
> >> records for their main website or are testing ipv6 at an 
> >> ipv6. subdomain.
> >>
> >> Below is copy of the new section for your entertainment.
> > 
> > Thanks.
> > 
> > You might also try connecting to port 80 of those sites.  Afterall,
> > if they were on Alexa's top-one million list yesterday they should
> > be listening on port 80.
> 
> Yep, that is a great idea and we will add an HTTP survey in 
> the near future.
> 
> > From the information currently posted at
> > http://bgp.he.net/ipv6-progress-report.cgi, I found the 
> following sites didn't
> > accept connections to port 80 via their AAAA records:
> > 
> > die.net                        2607:f820:42::4 (failed)
> > netbynet.ru                    
> 2a00:d18:f00d:d401:fe0b:101:0:67 (failed)
> > luc.edu                        192:192:168:168:1:1:1:1 (failed)
> > pcc.edu                        192:192:168:168:1:1:1:1 (failed)
> > bayimg.com                     2a01:298:3:1:1337::13 (failed)
> > tribune.com                    2002:a3c0:1712::a3c0:1712 (failed)
> > proua.com                      2a01:d0::10:1 (failed)
> > worldofwatches.com             2002:4087:6747:: (failed)
> > essex.ac.uk                    2002:9bf5:305e::9bf5:305e (failed)
> > fernuni-hagen.de               2002:84b0:8102::84b0:8102 (failed),
> > 2002:84b0:8101::84b0:8101 (failed)
> > 
> > I noticed that essex.ac.uk was failing for IPv4, too, so 
> they might be having
> > a site outage at the moment.  The others, however ...
> 
> And now that they have added AAAA records and some sites are 
> reporting 1 
> percent of accesses coming in via IPv6 (ripe for example) they have a 
> vested interest in fixing it so that their site works correctly.
> 
> I suppose this reveals that there is a lack of production web site 
> monitoring in IPv6 land, hmmmm opportunity??? ;)

Partially it is lack of clue.  For example, top100.cn and akilli.tv 
(which are #2986 and #18306 from Alexa's list) have an AAAA record 
pointing to ::1.

Then there are a bunch of IPv4-mapped addresses being advertised,
too; I don't understand the intent of doing that.

> I'm alluding to the SaaS model of pingdom, webmetrics, and 
> panopta.  Not "can you configure cacti etc" since I know you can! :)

Agreed, once the site is really trying to do the right thing.  
Using an IPv4-mapped address or loopback address is not the Right
Thing!  :-)

-d


From jay at west.net  Wed Nov 18 02:35:04 2009
From: jay at west.net (Jay Hennigan)
Date: Tue, 17 Nov 2009 17:35:04 -0800
Subject: Top Websites Running IPv6
In-Reply-To: <037701ca67b0$4dd76ff0$c2f0200a@cisco.com>
References: <4B02785F.8030402@he.net>
	<037701ca67b0$4dd76ff0$c2f0200a@cisco.com>
Message-ID: <4B034F48.8000903@west.net>

Dan Wing wrote:

> You might also try connecting to port 80 of those sites.  Afterall,
> if they were on Alexa's top-one million list yesterday they should
> be listening on port 80.
> 
>>From the information currently posted at
> http://bgp.he.net/ipv6-progress-report.cgi, I found the following sites didn't
> accept connections to port 80 via their AAAA records:

Well, a couple of those AAAA records are rather obviously broken.

luc.edu and pcc.edu look like a doubled default private IPv4 address 
from some consumer gear.  I wonder if these are populated by default in 
a DNS application somewhere.  If so it is likely to cause problems 
should it become common.

> die.net                        2607:f820:42::4 (failed)
> netbynet.ru                    2a00:d18:f00d:d401:fe0b:101:0:67 (failed)
> luc.edu                        192:192:168:168:1:1:1:1 (failed)
> pcc.edu                        192:192:168:168:1:1:1:1 (failed)
> bayimg.com                     2a01:298:3:1:1337::13 (failed)
> tribune.com                    2002:a3c0:1712::a3c0:1712 (failed)
> proua.com                      2a01:d0::10:1 (failed)
> worldofwatches.com             2002:4087:6747:: (failed)
> essex.ac.uk                    2002:9bf5:305e::9bf5:305e (failed)
> fernuni-hagen.de               2002:84b0:8102::84b0:8102 (failed),
> 2002:84b0:8101::84b0:8101 (failed)

--
Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
Impulse Internet Service  -  http://www.impulse.net/
Your local telephone and internet company - 805 884-6323 - WB6RDV

From dougb at dougbarton.us  Wed Nov 18 02:41:07 2009
From: dougb at dougbarton.us (Doug Barton)
Date: Tue, 17 Nov 2009 17:41:07 -0800
Subject: Top Websites Running IPv6
In-Reply-To: <4B02785F.8030402@he.net>
References: <4B02785F.8030402@he.net>
Message-ID: <4B0350B3.1090101@dougbarton.us>

Mike Leber wrote:
> 
> I updated the report that we run at
> http://bgp.he.net/ipv6-progress-report.cgi to check the Alexa top 1
> million websites.  We now also check www. and ipv6. for each domain as
> well.  It reveals that quite a few major websites have either added AAAA
> records for their main website or are testing ipv6 at an ipv6. subdomain.

You might also try one run with www6.domain just to see if it shows up
with any frequency.

Nice to see freebsd.org in your list ... :)

Doug

-- 

	Improve the effectiveness of your Internet presence with
	a domain name makeover!    http://SupersetSolutions.com/


From dwing at cisco.com  Wed Nov 18 03:00:21 2009
From: dwing at cisco.com (Dan Wing)
Date: Tue, 17 Nov 2009 18:00:21 -0800
Subject: Top Websites Running IPv6
In-Reply-To: <4B034F48.8000903@west.net>
References: <4B02785F.8030402@he.net>
	<037701ca67b0$4dd76ff0$c2f0200a@cisco.com>
	<4B034F48.8000903@west.net>
Message-ID: <064d01ca67f2$e2d64440$c2f0200a@cisco.com>

 

> -----Original Message-----
> From: Jay Hennigan [mailto:jay at west.net] 
> Sent: Tuesday, November 17, 2009 5:35 PM
> To: Dan Wing; ipv6-ops at lists.cluenet.de
> Subject: Re: Top Websites Running IPv6
> 
> Dan Wing wrote:
> 
> > You might also try connecting to port 80 of those sites.  Afterall,
> > if they were on Alexa's top-one million list yesterday they should
> > be listening on port 80.
> > 
> >>From the information currently posted at
> > http://bgp.he.net/ipv6-progress-report.cgi, I found the 
> following sites didn't
> > accept connections to port 80 via their AAAA records:
> 
> Well, a couple of those AAAA records are rather obviously broken.
> 
> luc.edu and pcc.edu look like a doubled default private IPv4 address 
> from some consumer gear.  I wonder if these are populated by 
> default in 
> a DNS application somewhere.  If so it is likely to cause problems 
> should it become common.

And the others will suffer loading delays for IPv6-enabled clients
which prefer IPv6 over IPv4.  Until the user disables IPv6, that is.

-d


> > die.net                        2607:f820:42::4 (failed)
> > netbynet.ru                    
> 2a00:d18:f00d:d401:fe0b:101:0:67 (failed)
> > luc.edu                        192:192:168:168:1:1:1:1 (failed)
> > pcc.edu                        192:192:168:168:1:1:1:1 (failed)
> > bayimg.com                     2a01:298:3:1:1337::13 (failed)
> > tribune.com                    2002:a3c0:1712::a3c0:1712 (failed)
> > proua.com                      2a01:d0::10:1 (failed)
> > worldofwatches.com             2002:4087:6747:: (failed)
> > essex.ac.uk                    2002:9bf5:305e::9bf5:305e (failed)
> > fernuni-hagen.de               2002:84b0:8102::84b0:8102 (failed),
> > 2002:84b0:8101::84b0:8101 (failed)
> 
> --
> Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
> Impulse Internet Service  -  http://www.impulse.net/
> Your local telephone and internet company - 805 884-6323 - WB6RDV


From lists at quux.de  Wed Nov 18 14:03:33 2009
From: lists at quux.de (Jens Link)
Date: Wed, 18 Nov 2009 14:03:33 +0100
Subject: ipv6-ops Digest, Vol 56, Issue 6
In-Reply-To: <28E139F46D45AF49A31950F88C497458041A7C16@E03MVZ2-UKDY.domain1.systemhost.net>
	(michael dillon's message of "Tue\, 17 Nov 2009 16\:26\:37 -0000")
References: <28E139F46D45AF49A31950F88C497458041A7C16@E03MVZ2-UKDY.domain1.systemhost.net>
Message-ID: <878we4j87u.fsf@laphroiag.quux.de>

<michael.dillon at bt.com> writes:

> Sites running SUSE Linux.
> Read this Technical Information Document from Novell for more info
> <http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&ex
> ternalId=10074602&sliceId=&docTypeID=DT_TID_1_1&dialogID=102635143&state
> Id=0%200%20102633339>

This article refers to Netware and not Linux. But I agree, it's a bad
and strange idea.  

Jens
-- 
-------------------------------------------------------------------------
| Foelderichstr. 40  | 13595 Berlin, Germany | +49-151-18721264         |
| http://www.quux.de | http://blog.quux.de   | jabber: jenslink at guug.de |
-------------------------------------------------------------------------

From michael.dillon at bt.com  Wed Nov 18 14:12:35 2009
From: michael.dillon at bt.com (michael.dillon at bt.com)
Date: Wed, 18 Nov 2009 13:12:35 -0000
Subject: ipv6-ops Digest, Vol 56, Issue 6
In-Reply-To: <878we4j87u.fsf@laphroiag.quux.de>
Message-ID: <28E139F46D45AF49A31950F88C497458042262DC@E03MVZ2-UKDY.domain1.systemhost.net>


> > Sites running SUSE Linux.
> > Read this Technical Information Document from Novell for more info 
> > 
> <http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&
> > ex 
> > 
> ternalId=10074602&sliceId=&docTypeID=DT_TID_1_1&dialogID=102635143&sta
> > te
> > Id=0%200%20102633339>
> 
> This article refers to Netware and not Linux. But I agree, 
> it's a bad and strange idea.  

Nowadays, Netware is a strange hybrid with the SUSE Linux system under
the name Open Enterprise Server. Even if it is using the Netware kernel,
you can still install things like Apache or sendmail. So companies which
trust Novell for their core network operating system now run some form
of SUSE Linux and will tend to look to Novell for support information.

That's why I think we could probably cure this problem if someone with
contacts at Novell or SUSE, could raise the issue and suggest how they
could correct their TID and issue an announcement about proper
configuration of IPv6 on their servers.

--Michael Dillon
 

From owens at nysernet.org  Wed Nov 18 14:59:31 2009
From: owens at nysernet.org (Bill Owens)
Date: Wed, 18 Nov 2009 08:59:31 -0500
Subject: ipv6-ops Digest, Vol 56, Issue 6
In-Reply-To: <28E139F46D45AF49A31950F88C497458042262DC@E03MVZ2-UKDY.domain1.systemhost.net>
References: <878we4j87u.fsf@laphroiag.quux.de>
	<28E139F46D45AF49A31950F88C497458042262DC@E03MVZ2-UKDY.domain1.systemhost.net>
Message-ID: <20091118135931.GA8889@nysernet.org>

On Wed, Nov 18, 2009 at 01:12:35PM -0000, michael.dillon at bt.com wrote:
> Nowadays, Netware is a strange hybrid with the SUSE Linux system under
> the name Open Enterprise Server. Even if it is using the Netware kernel,
> you can still install things like Apache or sendmail. So companies which
> trust Novell for their core network operating system now run some form
> of SUSE Linux and will tend to look to Novell for support information.
> 
> That's why I think we could probably cure this problem if someone with
> contacts at Novell or SUSE, could raise the issue and suggest how they
> could correct their TID and issue an announcement about proper
> configuration of IPv6 on their servers.

I think that this dates back to the days when some resolvers responded to AAAA queries for names that have only A records with NXDOMAIN rather than NOERROR. I had a vague recollection that Netware was in that camp, and found some complaints from the 2003 era relating to anti-spam software that rejected outbound email from a site if it couldn't resolve the domain. It appears that this crude hack was a way to satisfy that test.

Bill.

From dwing at cisco.com  Wed Nov 18 22:48:28 2009
From: dwing at cisco.com (Dan Wing)
Date: Wed, 18 Nov 2009 13:48:28 -0800
Subject: Top Websites Running IPv6
In-Reply-To: <4B0350B3.1090101@dougbarton.us>
References: <4B02785F.8030402@he.net> <4B0350B3.1090101@dougbarton.us>
Message-ID: <09b201ca6898$dd3e3640$c2f0200a@cisco.com>

> -----Original Message-----
> From: ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de 
> [mailto:ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de] On 
> Behalf Of Doug Barton
> Sent: Tuesday, November 17, 2009 5:41 PM
> To: Mike Leber
> Cc: ipv6-ops at lists.cluenet.de
> Subject: Re: Top Websites Running IPv6
> 
> Mike Leber wrote:
> > 
> > I updated the report that we run at
> > http://bgp.he.net/ipv6-progress-report.cgi to check the Alexa top 1
> > million websites.  We now also check www. and ipv6. for 
> each domain as
> > well.  It reveals that quite a few major websites have 
> either added AAAA
> > records for their main website or are testing ipv6 at an 
> ipv6. subdomain.
> 
> You might also try one run with www6.domain just to see if it shows up
> with any frequency.

I checked the top 1 million domains from Alexa by simply adding 
"www6.domain" to what Alexa lists.  From that, 745 (0.07%) have 
AAAA records.  Of those, 297 (39%) allowed me to successfully connect 
to TCP/80, 44 (5.91%) advertise loopback (::1), and 404 (54%) failed 
connections to TCP/80.  If one considers ::1 a failure, then 
404+44=448 (60%) are failures.

-d


> Nice to see freebsd.org in your list ... :)
> 
> Doug
> 
> -- 
> 
> 	Improve the effectiveness of your Internet presence with
> 	a domain name makeover!    http://SupersetSolutions.com/
> 


From fahad.alikhan at gmail.com  Tue Nov 24 09:07:54 2009
From: fahad.alikhan at gmail.com (FAHAD ALI KHAN)
Date: Tue, 24 Nov 2009 13:07:54 +0500
Subject: IPv6 WWW service
In-Reply-To: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>
Message-ID: <9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>

Guys

I have setup Dual stack web server, running personal blog. I have applied
for IPv6 Forum ? IPv6 enabled WWW logo program, but it shows IPv6 HTTP
access test was failed, whereas in my opinion & testing its UP & Running. I
wish if anyone on IPv6 please check fahad.xpedientonline.net is available or
not.

Initially I feel it might be the MTU issue, but I have set both router &
server interface?s MTU to 1280B (which is on Native v6) and Router is than
Tunnel to IPv6 ISP in UK (Tunnel IPv6 MTU is 1480). Can anyone suggest me,
where I am lacking?

If replies are not suitable for this forum than please check & reply to me
directly.

I hope, ppls will help me to solve this.

**

*Regards*

**

*Fahad*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20091124/dca94cda/attachment.html 

From martin at hotze.com  Tue Nov 24 09:13:49 2009
From: martin at hotze.com (Martin Hotze)
Date: Tue, 24 Nov 2009 09:13:49 +0100
Subject: IPv6 WWW service
In-Reply-To: <9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>
	<9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
Message-ID: <275E689A52D3FD4E922743D02EAEA8FA26DBF7@server1.hotze.local>

Hi,

 

from here [1] I can't reach the site with IPv6. The site works with
IPv4, though.

 

 

greetings, Martin

 

 

[1] AS8596 (.at) w/native IPv6

 

 

From: ipv6-ops-bounces+martin=hotze.com at lists.cluenet.de
[mailto:ipv6-ops-bounces+martin=hotze.com at lists.cluenet.de] On Behalf
Of FAHAD ALI KHAN
Sent: Tuesday, November 24, 2009 9:08 AM
To: ipv6-ops at lists.cluenet.de
Subject: IPv6 WWW service

 

Guys

I have setup Dual stack web server, running personal blog. I have
applied for IPv6 Forum - IPv6 enabled WWW logo program, but it shows
IPv6 HTTP access test was failed, whereas in my opinion & testing its
UP & Running. I wish if anyone on IPv6 please check
fahad.xpedientonline.net is available or not. 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20091124/77e8b15e/attachment.html 

From fahad.alikhan at gmail.com  Tue Nov 24 09:15:55 2009
From: fahad.alikhan at gmail.com (FAHAD ALI KHAN)
Date: Tue, 24 Nov 2009 13:15:55 +0500
Subject: IPv6 WWW service
In-Reply-To: <275E689A52D3FD4E922743D02EAEA8FA26DBF7@server1.hotze.local>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>
	<9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
	<275E689A52D3FD4E922743D02EAEA8FA26DBF7@server1.hotze.local>
Message-ID: <9347ea5b0911240015p34c77a68ja3afb1e59f61d930@mail.gmail.com>

Do DNS get resolve for fahad.xpedientonline.net ?

On Tue, Nov 24, 2009 at 1:13 PM, Martin Hotze <martin at hotze.com> wrote:

>  Hi,
>
>
>
> from here [1] I can?t reach the site with IPv6. The site works with IPv4,
> though.
>
>
>
>
>
> greetings, Martin
>
>
>
>
>
> [1] AS8596 (.at) w/native IPv6
>
>
>
>
>
> *From:* ipv6-ops-bounces+martin=hotze.com at lists.cluenet.de [mailto:
> ipv6-ops-bounces+martin <ipv6-ops-bounces%2Bmartin>=hotze.com@
> lists.cluenet.de] *On Behalf Of *FAHAD ALI KHAN
> *Sent:* Tuesday, November 24, 2009 9:08 AM
> *To:* ipv6-ops at lists.cluenet.de
> *Subject:* IPv6 WWW service
>
>
>
> Guys
>
> I have setup Dual stack web server, running personal blog. I have applied
> for IPv6 Forum ? IPv6 enabled WWW logo program, but it shows IPv6 HTTP
> access test was failed, whereas in my opinion & testing its UP & Running. I
> wish if anyone on IPv6 please check fahad.xpedientonline.net is available
> or not.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20091124/413f27c6/attachment.html 

From jeroen at easyhosting.nl  Tue Nov 24 09:17:27 2009
From: jeroen at easyhosting.nl (Jeroen Wunnink)
Date: Tue, 24 Nov 2009 09:17:27 +0100
Subject: IPv6 WWW service
In-Reply-To: <9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>
	<9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
Message-ID: <4B0B9697.8020109@easyhosting.nl>

Might want to create an AAAA record for fahad.xpedientonline.net, or 
noone will know which IPv6 address to go to ;-)

Macbook-Jeroen-2:~ jeroenwu$ dig aaaa fahad.xpedientonline.net

; <<>> DiG 9.6.0-APPLE-P2 <<>> aaaa fahad.xpedientonline.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17300
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;fahad.xpedientonline.net.    IN    AAAA


FAHAD ALI KHAN wrote:
> Guys
>
> I have setup Dual stack web server, running personal blog. I have 
> applied for IPv6 Forum ? IPv6 enabled WWW logo program, but it shows 
> IPv6 HTTP access test was failed, whereas in my opinion & testing its 
> UP & Running. I wish if anyone on IPv6 please check 
> fahad.xpedientonline.net <http://fahad.xpedientonline.net> is 
> available or not.
>
> Initially I feel it might be the MTU issue, but I have set both router 
> & server interface?s MTU to 1280B (which is on Native v6) and Router 
> is than Tunnel to IPv6 ISP in UK (Tunnel IPv6 MTU is 1480). Can anyone 
> suggest me, where I am lacking?
>
> If replies are not suitable for this forum than please check & reply 
> to me directly.
>
> I hope, ppls will help me to solve this.
>
> *Regards*
>
> *Fahad*
>
>

-- 

Met vriendelijke groet,

Jeroen Wunnink,
EasyHosting B.V. Systeembeheerder
systeembeheer at easyhosting.nl

telefoon:+31 (035) 6285455              Postbus 48
fax: +31 (035) 6838242                  3755 ZG Eemnes

http://www.easyhosting.nl
http://www.easycolocate.nl



From tore at linpro.no  Tue Nov 24 09:22:02 2009
From: tore at linpro.no (Tore Anderson)
Date: Tue, 24 Nov 2009 09:22:02 +0100
Subject: IPv6 WWW service
In-Reply-To: <9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>
	<9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
Message-ID: <4B0B97AA.5000304@linpro.no>

* FAHAD ALI KHAN

> I have setup Dual stack web server, running personal blog. I have
> applied for IPv6 Forum ? IPv6 enabled WWW logo program, but it shows
> IPv6 HTTP access test was failed, whereas in my opinion & testing its UP
> & Running. I wish if anyone on IPv6 please check
> fahad.xpedientonline.net <http://fahad.xpedientonline.net> is available
> or not.

It works for me from AS39029 in Norway., although I have really horrible
latency to your site over IPv6 (~475ms RTT) and some packet loss:

HOST: echo.linpro.no              Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. 2a02:c0:1002:102::1           0.0%   100    0.4   0.3   0.2   0.7   0.1
  2. 2a02:c0:1000:5::1             0.0%   100    0.8   0.9   0.7   2.3   0.2
  3. 2a02:c0:1000:3::1             0.0%   100    1.0   1.2   0.8  10.3   1.3
  4. 2a02:c0:1000:2::2             0.0%   100    0.5   2.9   0.4  38.1   8.0
  5. 2001:6c8:0:5000::61           0.0%   100    1.5  16.5   0.8 251.9  47.0
  6. 2001:7f8:d:ff::187            0.0%   100    9.0   9.7   7.4  18.0   3.3
  7. 2001:470:0:110::1             0.0%   100   29.0  30.0  28.8  53.1   3.1
  8. 2001:470:0:47::1              0.0%   100   29.0  29.2  28.9  35.6   1.0
  9. 2001:470:0:3f::1              0.0%   100   36.7  38.4  36.7  46.8   3.0
 10. 2001:7f8:4::7577:1            0.0%   100   35.5  35.5  35.3  37.9   0.3
 11. 2001:4830:fe:1010::2          0.0%   100  110.2 110.2 109.9 112.2   0.3
 12. 2001:4830:ff:f150::2          0.0%   100  110.2 110.2 109.9 111.8   0.2
 13. 2001:4830:ff:e250::2          0.0%   100  124.0 124.3 123.8 133.6   1.0
 14. 2001:4830:ff:f255::1          0.0%   100  157.2 157.8 156.9 191.7   3.5
 15. 2001:4830:ff:e101::1          1.0%   100  203.5 204.8 203.2 235.1   3.6
 16. 2001:4830:ff:e100::2          1.0%   100  203.9 204.0 203.3 207.3   0.7
 17. 2001:4830:ff:11ab::2          1.0%   100  203.5 204.1 203.3 212.6   1.1
 18. 2001:4830:ff:1202::1          1.0%   100  203.9 204.3 203.3 223.9   2.1
 19. 2001:4830:e0:11::2            1.0%   100  477.4 478.6 476.5 492.2   2.1
 20. 2001:4538:100::2              2.0%   100  477.4 479.8 476.2 517.2   4.6

AS path is 3292 6939 30071 9541.

Over IPv4 I get ~175ms RTT (and some packet loss there too actually).

Best regards,
-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/
Tel: +47 21 54 41 27

From gert at space.net  Tue Nov 24 09:23:03 2009
From: gert at space.net (Gert Doering)
Date: Tue, 24 Nov 2009 09:23:03 +0100
Subject: IPv6 WWW service
In-Reply-To: <9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>
	<9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
Message-ID: <20091124082303.GM32226@Space.Net>

Hi,

On Tue, Nov 24, 2009 at 01:07:54PM +0500, FAHAD ALI KHAN wrote:
> I have setup Dual stack web server, running personal blog. I have applied
> for IPv6 Forum ? IPv6 enabled WWW logo program, but it shows IPv6 HTTP
> access test was failed, whereas in my opinion & testing its UP & Running. I
> wish if anyone on IPv6 please check fahad.xpedientonline.net is available or
> not.

Seems to work from here... v6 connects, web page is loaded.

Gert Doering
        -- NetMaster
-- 
Total number of prefixes smaller than registry allocations:  144438

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

From daniel at bit.nl  Tue Nov 24 09:24:22 2009
From: daniel at bit.nl (Daniel Verlouw)
Date: Tue, 24 Nov 2009 09:24:22 +0100
Subject: IPv6 WWW service
In-Reply-To: <4B0B9697.8020109@easyhosting.nl>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>
	<9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
	<4B0B9697.8020109@easyhosting.nl>
Message-ID: <1259051062.26759.4.camel@daniel.office.bit.nl>

On Tue, 2009-11-24 at 09:17 +0100, Jeroen Wunnink wrote:
> Might want to create an AAAA record for fahad.xpedientonline.net, or 
> noone will know which IPv6 address to go to ;-)

works fine over here:

daniel at daniel:~$ dig AAAA fahad.xpedientonline.net +short
2001:4538:100::2

daniel at daniel:~$ ping6 fahad.xpedientonline.net -c 1
PING fahad.xpedientonline.net(2001:4538:100::2) 56 data bytes
64 bytes from 2001:4538:100::2: icmp_seq=1 ttl=53 time=477 ms

   --Daniel



From mludvig at logix.net.nz  Tue Nov 24 09:31:35 2009
From: mludvig at logix.net.nz (Michal Ludvig)
Date: Tue, 24 Nov 2009 21:31:35 +1300
Subject: IPv6 WWW service
In-Reply-To: <9347ea5b0911240015p34c77a68ja3afb1e59f61d930@mail.gmail.com>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>	<9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>	<275E689A52D3FD4E922743D02EAEA8FA26DBF7@server1.hotze.local>
	<9347ea5b0911240015p34c77a68ja3afb1e59f61d930@mail.gmail.com>
Message-ID: <4B0B99E7.4070405@logix.net.nz>

On 11/24/2009 09:15 PM, FAHAD ALI KHAN wrote:
> Do DNS get resolve for fahad.xpedientonline.net

Your zone is not consistent. .net resolvers have these NS records for
xpedientonline.net:

xpedientonline.net.     172800  IN      NS      csns5.cyber.net.pk.
xpedientonline.net.     172800  IN      NS      ns1.cyber.net.pk.

However the zones are completely different on both - csns5 doesn't know
anything about fahad.xpedientonline.net. That's why some clients see
your blog and some don't.

Fix your NS delegations and you'll see how things suddenly improve ;-)

Michal

From mtinka at globaltransit.net  Tue Nov 24 10:47:20 2009
From: mtinka at globaltransit.net (Mark Tinka)
Date: Tue, 24 Nov 2009 17:47:20 +0800
Subject: IPv6 WWW service
In-Reply-To: <4B0B99E7.4070405@logix.net.nz>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>
	<9347ea5b0911240015p34c77a68ja3afb1e59f61d930@mail.gmail.com>
	<4B0B99E7.4070405@logix.net.nz>
Message-ID: <200911241747.21407.mtinka@globaltransit.net>

On Tuesday 24 November 2009 04:31:35 pm Michal Ludvig wrote:

> Fix your NS delegations and you'll see how things
>  suddenly improve ;-)

Same issue here (Malaysia). DNS isn't working:

[tinka at nms ~]$ traceroute6 fahad.xpedientonline.net
traceroute6: hostname nor servname provided, or not known
[tinka at nms ~]$

v4 seems alright:

[tinka at nms ~]$ traceroute fahad.xpedientonline.net
traceroute to fahad.xpedientonline.net (124.29.205.182), 64 hops max, 52 byte packets
 1  ge-2-0-11.edge-gw-1-kul-pip.my.globaltransit.net (124.158.236.61)  0.388 ms  0.361 ms  0.197 ms
 2  ge-1-0-0-0.cr-gw-2-kul-pip.my.globaltransit.net (61.11.210.130)  0.672 ms  0.679 ms  0.820 ms
 3  pos-2-0.cr-gw-2-sin-pip.sg.globaltransit.net (61.11.210.10)  8.474 ms  8.014 ms  8.467 ms
 4  ge-0-2.cr-gw-1-sin-pip.sg.globaltransit.net (124.158.224.65)  8.775 ms  8.164 ms  8.312 ms
 5  ge-0-1-0-0.br-gw-2-sin-pip.sg.globaltransit.net (124.158.224.189)  7.843 ms  7.387 ms  7.371 ms
 6  203.208.143.141 (203.208.143.141)  7.994 ms  8.781 ms  9.401 ms
 7  ge-0-1-8-0.sngtp-dr2.ix.singtel.com (203.208.151.193)  7.994 ms
    ge-1-1-7-0.sngtp-dr2.ix.singtel.com (203.208.151.197)  9.257 ms
    ge-1-1-6-0.sngtp-dr1.ix.singtel.com (203.208.182.5)  7.860 ms
 8  ge-6-0-0-0.sngc3-dr1.ix.singtel.com (203.208.151.158)  10.375 ms  11.128 ms  10.026 ms
 9  so-0-2-0-0.lonlx-cr2.ix.singtel.com (203.208.151.134)  267.279 ms
    203.208.152.106 (203.208.152.106)  10.659 ms
    so-0-2-0-0.lonlx-cr2.ix.singtel.com (203.208.151.134)  196.297 ms
10  tw129-static250.tw1.com (119.63.129.250)  186.330 ms  183.040 ms
    so-3-0-2-0.loncl-cr1.ix.singtel.com (203.208.153.18)  195.204 ms
11  202.163.97.142 (202.163.97.142)  215.717 ms
    ge-11-14-csw01-ho-khi.cyber.net.pk (202.163.97.129)  193.236 ms  200.376 ms
12  tw31-static14.tw1.com (117.20.31.14)  301.663 ms
    ar-ipv6-ho-khi.cyber.net.pk (202.163.97.90)  188.516 ms
    tw31-static14.tw1.com (117.20.31.14)  311.013 ms
13  tw129-static250.tw1.com (119.63.129.250)  296.100 ms
    124.29.205.182 (124.29.205.182)  198.843 ms  200.522 ms
[tinka at nms ~]$

the v6 address that folks have resolved seems alright too:

[tinka at nms ~]$ traceroute6 2001:4538:100::2
traceroute6 to 2001:4538:100::2 (2001:4538:100::2) from 2001:4498:0:3::1:1, 64 hops max, 12 byte packets
 1  ge-2-0-14.edge6-gw-2-kul-pip.my.globaltransit.net  0.702 ms  0.357 ms  0.663 ms
 2  ge-0-1-0-0.cr6-gw-1-kul-pip.my.globaltransit.net  0.664 ms  0.512 ms  0.521 ms
 3  ge-0-1-0-0.br6-gw-1-kul-pip.my.globaltransit.net  0.507 ms  0.509 ms  0.663 ms
 4  so-2-3-1.sin11.ip6.tinet.net  7.060 ms  7.069 ms  6.903 ms
 5  so-1-0-1.hkg11.ip6.tinet.net  40.135 ms  40.298 ms  40.132 ms
 6  so-0-1-2.sjc11.ip6.tinet.net  185.995 ms  185.530 ms  183.978 ms
 7  xe-0-0-0.sjc10.ip6.tinet.net  186.463 ms  185.216 ms  185.371 ms
 8  xe-0-3-0.was10.ip6.tinet.net  262.021 ms  261.856 ms  261.813 ms
 9  xe-5-1-0.was12.ip6.tinet.net  261.362 ms  261.197 ms  271.026 ms
10  ibr01-ve96.asbn01.occaid.net  263.841 ms *  270.258 ms
11  bbr01-g1-0.atln01.occaid.net  295.356 ms  298.646 ms  300.197 ms
12  bbr01-p1-0.dlls01.occaid.net  313.610 ms  322.202 ms  315.342 ms
13  dcr01-p1-5.lsan01.occaid.net  368.519 ms  365.406 ms  349.333 ms
14  bbr01-g0-2.irvn01.occaid.net  391.609 ms  396.750 ms  390.521 ms
15  dcr01-g1-2.psdn01.occaid.net  403.321 ms  402.873 ms  393.362 ms
16  bbr01-f1-5.snfc02.occaid.net  409.713 ms  413.309 ms  412.673 ms
17  *
    cybernet-ic-1019-sfo.customer.occaid.net  693.793 ms  706.747 ms
18  2001:4538:100::2  690.521 ms  690.833 ms  700.651 ms
[tinka at nms ~]$

tcp/80 seems open on v6:

[tinka at nms ~]$ telnet 2001:4538:100::2 80
Trying 2001:4538:100::2...
Connected to 2001:4538:100::2.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
[tinka at nms ~]$

Cheers,

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20091124/71300a0e/attachment.bin 

From ryanczak at arin.net  Tue Nov 24 13:07:06 2009
From: ryanczak at arin.net (Matt Ryanczak)
Date: Tue, 24 Nov 2009 07:07:06 -0500
Subject: IPv6 WWW service
In-Reply-To: <9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>
	<9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
Message-ID: <1259064426.21796.79.camel@otto>

Works from here. I do not see the DNS problems others reported either. I
assume you got that fixed. 

It looks like you're using an OCCAID tunnel or peering? Given your on
the opposite side of the world the connection looks good. 

 1. 2001:500:4:15::1                                                                       0.0%    11    0.9   0.5   0.4   0.9   0.1
 2. 2001:500:4:14::254                                                                     0.0%    11    1.5   0.5   0.2   2.2   0.7
 3. cha-inner.arin.net                                                                     0.0%    11    0.4   0.5   0.3   0.7   0.1
 4. cr3.arin.net                                                                           0.0%    11    1.1   1.1   1.0   1.3   0.1
 5. cr2-ptp.arin.net                                                                       0.0%    11    4.5   4.6   4.0   6.9   0.8
 6. cr6.arin.net                                                                           0.0%    11    4.8   5.3   4.8   8.3   1.0
 7. bbr01-ve102.asbn01.occaid.net                                                          0.0%    11    5.4   5.4   5.3   5.5   0.1
 8. bbr01-g1-0.atln01.occaid.net                                                           0.0%    11   18.9  19.3  18.9  21.0   0.6
 9. bbr01-p1-0.dlls01.occaid.net                                                           0.0%    11   52.7  53.2  52.3  57.4   1.7
10. dcr01-p1-5.lsan01.occaid.net                                                           0.0%    11   98.5  99.3  98.3 105.6   2.2
11. bbr01-g0-2.irvn01.occaid.net                                                           0.0%    11  102.6 102.2  99.2 119.7   6.2
12. dcr01-g1-2.psdn01.occaid.net                                                           0.0%    10  101.4 103.1 100.7 109.4   3.3
13. bbr01-f1-5.snfc02.occaid.net                                                           0.0%    10  118.6 113.6 112.5 118.6   1.9
14. cybernet-ic-1019-sfo.customer.occaid.net                                               0.0%    10  399.1 399.0 398.3 399.5   0.4
15. 2001:4538:100::2                                                                       0.0%    10  397.4 398.9 397.4 404.7   2.4

~Matt


On Tue, 2009-11-24 at 03:07 -0500, FAHAD ALI KHAN wrote:
> Guys
> 
> I have setup Dual stack web server, running personal blog. I have
> applied for IPv6 Forum ? IPv6 enabled WWW logo program, but it shows
> IPv6 HTTP access test was failed, whereas in my opinion & testing its
> UP & Running. I wish if anyone on IPv6 please check
> fahad.xpedientonline.net is available or not. 
> 
> Initially I feel it might be the MTU issue, but I have set both router
> & server interface?s MTU to 1280B (which is on Native v6) and Router
> is than Tunnel to IPv6 ISP in UK (Tunnel IPv6 MTU is 1480). Can anyone
> suggest me, where I am lacking?
> 
> If replies are not suitable for this forum than please check & reply
> to me directly.
> 
> I hope, ppls will help me to solve this.
> 
> Regards
> 
> Fahad
> 
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20091124/7d0b2608/attachment.bin 

From nuno.vieira at nfsi.pt  Tue Nov 24 13:53:22 2009
From: nuno.vieira at nfsi.pt (Nuno Vieira - nfsi telecom)
Date: Tue, 24 Nov 2009 12:53:22 +0000 (WET)
Subject: IPv6 WWW service
In-Reply-To: <99238174.327.1259066993819.JavaMail.root@zimbra.nfsi.pt>
Message-ID: <451231278.330.1259067202729.JavaMail.root@zimbra.nfsi.pt>

Hi Fahad, 

Works from here (AS25137, Portugal), a bit of packet loss on your side (nothing scary), but the rtt is horrible. 

Packets Pings 
Host Loss% Snt Last Avg Best Wrst StDev 
1. ge-1.Edge1.ip6.Lisbon.NFSi.pt 0.0% 180 0.2 1.1 0.1 16.0 2.4 
2. 2001:b18:0:1::11 0.0% 180 0.4 1.2 0.2 20.3 3.0 
3. he.ipv6.panap.fr 0.0% 180 44.5 44.8 44.1 55.9 2.0 
4. 10gigabitethernet1-3.core1.lon1. 0.0% 180 51.4 52.7 51.1 61.2 2.8 
5. ibr01-ve26.lndn01.occaid.net 0.0% 180 117.9 117.8 117.4 118.7 0.2 
6. bbr01-p1-0.nwrk01.occaid.net 0.0% 180 118.0 117.8 117.4 129.6 0.9 
7. bbr01-g1-0.asbn01.occaid.net 0.0% 180 118.5 117.8 117.3 118.6 0.2 
8. bbr01-g1-0.atln01.occaid.net 0.0% 180 147.2 147.4 146.7 149.1 0.4 
9. bbr01-p1-0.dlls01.occaid.net 0.0% 180 165.0 165.0 164.3 173.8 0.9 
10. dcr01-p1-5.lsan01.occaid.net 0.0% 180 210.7 210.9 210.3 216.1 0.5 
11. bbr01-g0-2.irvn01.occaid.net 0.0% 179 246.4 246.7 246.0 248.5 0.4 
12. dcr01-g1-2.psdn01.occaid.net 0.0% 179 248.1 248.2 247.3 257.1 1.0 
13. bbr01-f1-5.snfc02.occaid.net 0.0% 179 259.8 259.4 258.2 263.7 0.7 
14. cybernet-ic-1019-sfo.customer.oc 1.7% 179 545.0 545.8 544.4 553.3 1.2 
15. 2001:4538:100::2 0.6% 179 544.6 545.2 543.9 553.0 1.2 

In other hand, ipv4 path is much better. 

traceroute to fahad.xpedientonline.net (124.29.205.182), 30 hops max, 40 byte packets 
1 94.46.247.254 (94.46.247.254) 0.389 ms 0.426 ms 0.514 ms 
2 194.25.210.137 (194.25.210.137) 0.310 ms 0.357 ms 0.398 ms 
3 217.239.38.161 (217.239.38.161) 39.628 ms 39.720 ms 39.765 ms 
4 195.66.227.10 (195.66.227.10) 40.059 ms 40.206 ms 40.298 ms 
5 203.208.151.209 (203.208.151.209) 40.094 ms 40.187 ms 40.169 ms 
6 203.208.174.134 (203.208.174.134) 157.277 ms 157.221 ms 158.109 ms 
7 tw129-static90.tw1.com (119.63.129.90) 166.082 ms 159.658 ms 160.150 ms 
8 tw129-static250.tw1.com (119.63.129.250) 159.497 ms 159.657 ms 159.653 ms 
9 ge-11-14-csw01-ho-khi.cyber.net.pk (202.163.97.129) 159.697 ms 202.163.97.142 (202.163.97.142) 160.541 ms ge-11-14-csw01-ho-khi.cyber.net.pk (202.163.97.129) 159.693 ms 
10 ar-ipv6-ho-khi.cyber.net.pk (202.163.97.90) 159.584 ms 160.926 ms 162.120 ms 
11 124.29.205.182 (124.29.205.182) 160.861 ms 158.350 ms 159.347 ms 

You should consider to get a Tunnel in Europe (London by instance). That would save you some rtt. 

cheers, 
--- 
Nuno Vieira 
nfsi telecom, lda. 

[Email] nuno.vieira at nfsi.pt 
[Phone] +351 21 114 2315 
[Phone] +351 21 142 2300 
[Mobile] +351 91 925 5561 
[Fax] +351 21 114 2301 
[Web] http://www.nfsi.pt/ 

----- "FAHAD ALI KHAN" <fahad.alikhan at gmail.com> wrote: 
> 
> Guys 
> 
> I have setup Dual stack web server, running personal blog. I have applied for IPv6 Forum ? IPv6 enabled WWW logo program, but it shows IPv6 HTTP access test was failed, whereas in my opinion & testing its UP & Running. I wish if anyone on IPv6 please check fahad.xpedientonline.net is available or not. 



Initially I feel it might be the MTU issue, but I have set both router & server interface?s MTU to 1280B (which is on Native v6) and Router is than Tunnel to IPv6 ISP in UK (Tunnel IPv6 MTU is 1480). Can anyone suggest me, where I am lacking? 



If replies are not suitable for this forum than please check & reply to me directly. 



I hope, ppls will help me to solve this. 



Regards 



Fahad 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20091124/2f5bacf7/attachment.html 

From steve at ibctech.ca  Tue Nov 24 14:10:34 2009
From: steve at ibctech.ca (Steve Bertrand)
Date: Tue, 24 Nov 2009 08:10:34 -0500
Subject: IPv6 WWW service
In-Reply-To: <9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>
	<9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
Message-ID: <4B0BDB4A.3080500@ibctech.ca>

FAHAD ALI KHAN wrote:
> Guys
> 
> I have setup Dual stack web server, running personal blog. I have
> applied for IPv6 Forum ? IPv6 enabled WWW logo program, but it shows
> IPv6 HTTP access test was failed, whereas in my opinion & testing its UP
> & Running. I wish if anyone on IPv6 please check
> fahad.xpedientonline.net <http://fahad.xpedientonline.net> is available
> or not.
> 
> Initially I feel it might be the MTU issue, but I have set both router &
> server interface?s MTU to 1280B (which is on Native v6) and Router is
> than Tunnel to IPv6 ISP in UK (Tunnel IPv6 MTU is 1480). Can anyone
> suggest me, where I am lacking?
> 
> If replies are not suitable for this forum than please check & reply to
> me directly.
> 
> I hope, ppls will help me to solve this.

Works from (near) Toronto, Ontario, Canada:

pearl# traceroute6 -n fahad.xpedientonline.net

traceroute6 to fahad.xpedientonline.net (2001:4538:100::2) from
2607:f118::b6, 64 hops max, 12 byte packets

 1  2607:f118::1  0.286 ms  0.173 ms  0.241 ms
 2  2607:f118:1:2:209:e8ff:fe43:9f00  1.106 ms  0.979 ms  0.988 ms
 3  2001:470:1f0d:12e::1  92.438 ms  36.960 ms  37.538 ms
 4  2001:470:0:40::2  28.361 ms  29.459 ms  27.974 ms
 5  2001:504:0:2:0:3:71:1  28.963 ms  29.964 ms  28.972 ms
 6  2001:4830:ff:e250::2  57.958 ms  58.448 ms  56.959 ms
 7  2001:4830:ff:f255::1  110.925 ms  112.923 ms  110.926 ms
 8  2001:4830:ff:e101::1  112.424 ms  110.934 ms  110.976 ms
 9  2001:4830:ff:e100::2  113.438 ms  113.804 ms  112.439 ms
10  2001:4830:ff:11ab::2  114.917 ms  112.925 ms  112.910 ms
11  2001:4830:ff:1202::1  127.416 ms  126.926 ms *
12  2001:4830:e0:11::2  411.855 ms  411.691 ms  411.311 ms
13  2001:4538:100::2  411.170 ms  410.261 ms  409.814 ms\

...the web page loads as well, albeit slowly.

Steve

From sweeny at indiana.edu  Tue Nov 24 14:37:52 2009
From: sweeny at indiana.edu (Brent Sweeny)
Date: Tue, 24 Nov 2009 08:37:52 -0500
Subject: IPv6 WWW service
Message-ID: <4B0BE1B0.3000108@indiana.edu>

I get v6 resolution for fahad.xpedientonline.net and reach it from
Indiana at about 402ms RTT.

From martin at hotze.com  Tue Nov 24 14:42:56 2009
From: martin at hotze.com (Martin Hotze)
Date: Tue, 24 Nov 2009 14:42:56 +0100
Subject: IPv6 WWW service
In-Reply-To: <4B0BE1B0.3000108@indiana.edu>
References: <4B0BE1B0.3000108@indiana.edu>
Message-ID: <275E689A52D3FD4E922743D02EAEA8FA26DC23@server1.hotze.local>


works now with IPV6 from here (AS8596), too. RTT about 480ms.

#m


> -----Original Message-----
> From: ipv6-ops-bounces+martin=hotze.com at lists.cluenet.de
[mailto:ipv6-ops-
> bounces+martin=hotze.com at lists.cluenet.de] On Behalf Of Brent Sweeny
> Sent: Tuesday, November 24, 2009 2:38 PM
> To: ipv6-ops at lists.cluenet.de
> Subject: Re: IPv6 WWW service
> 
> I get v6 resolution for fahad.xpedientonline.net and reach it from
> Indiana at about 402ms RTT.

From michael at rancid.berkeley.edu  Tue Nov 24 16:47:37 2009
From: michael at rancid.berkeley.edu (Michael Sinatra)
Date: Tue, 24 Nov 2009 07:47:37 -0800
Subject: IPv6 WWW service
In-Reply-To: <1259064426.21796.79.camel@otto>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>	<9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
	<1259064426.21796.79.camel@otto>
Message-ID: <4B0C0019.5000900@rancid.berkeley.edu>

On 11/24/09 4:07 AM, Matt Ryanczak wrote:
> Works from here. I do not see the DNS problems others reported either. I
> assume you got that fixed. 

Not yet, but it appears to be better than before.

whois says:

    Domain Name: XPEDIENTONLINE.NET

[snip]

    Domain servers in listed order:
       CSNS5.CYBER.NET.PK
       NS1.CYBER.NET.PK


the net nameservers say:

;; ANSWER SECTION:
xpedientonline.net.	172800	IN	NS	csns5.cyber.net.pk.
xpedientonline.net.	172800	IN	NS	ns1.cyber.net.pk.

csns5.cyber.net.pk says:

;; ANSWER SECTION:
fahad.xpedientonline.net. 86400	IN	AAAA	2001:4538:100::2

;; AUTHORITY SECTION:
xpedientonline.net.	86400	IN	NS	ns.xpedientonline.net.

ns1.cyber.net.pk says:

;; ANSWER SECTION:
fahad.xpedientonline.net. 86400	IN	AAAA	2001:4538:100::2

;; AUTHORITY SECTION:
xpedientonline.net.	86400	IN	NS	ns1.cyber.net.pk.
xpedientonline.net.	86400	IN	NS	ns.cyber.net.pk.

ns.cyber.net.pk says:

;; ANSWER SECTION:
fahad.xpedientonline.net. 86400	IN	AAAA	2001:4538:100::2

;; AUTHORITY SECTION:
xpedientonline.net.	86400	IN	NS	ns1.cyber.net.pk.
xpedientonline.net.	86400	IN	NS	ns.cyber.net.pk.


The NS records are incoherent, but at all of the nameservers are giving 
out the correct AAAA record.  Also, ns[1].cyber.net.pk doesn't have an A 
record for ns.xpedientonline.net, but ns.xpedientonline.net does. 
That's going to ultimately lead to bizarre results.

However, the IPv6 address is reachable from UC Berkeley.

michael


From ruben.vanhoutte at trancenation.be  Tue Nov 24 09:24:55 2009
From: ruben.vanhoutte at trancenation.be (Ruben Vanhoutte)
Date: Tue, 24 Nov 2009 09:24:55 +0100
Subject: IPv6 WWW service
In-Reply-To: <4B0B9697.8020109@easyhosting.nl>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>	<9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
	<4B0B9697.8020109@easyhosting.nl>
Message-ID: <4B0B9857.9020208@trancenation.be>

It get's resolved perfectly over here.. and I can connect using ipv6

NewYork:~# dig aaaa fahad.xpedientonline.net

; <<>> DiG 9.5.1-P3 <<>> aaaa fahad.xpedientonline.net
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53733
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;fahad.xpedientonline.net.      IN      AAAA

;; ANSWER SECTION:
fahad.xpedientonline.net. 85623 IN      AAAA    2001:4538:100::2

;; Query time: 39 msec
;; SERVER: 10.1.3.60#53(10.1.3.60)
;; WHEN: Tue Nov 24 09:23:08 2009
;; MSG SIZE  rcvd: 70


Jeroen Wunnink wrote:
> Might want to create an AAAA record for fahad.xpedientonline.net, or 
> noone will know which IPv6 address to go to ;-)
>
> Macbook-Jeroen-2:~ jeroenwu$ dig aaaa fahad.xpedientonline.net
>
> ; <<>> DiG 9.6.0-APPLE-P2 <<>> aaaa fahad.xpedientonline.net
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17300
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;fahad.xpedientonline.net.    IN    AAAA
>
>
> FAHAD ALI KHAN wrote:
>> Guys
>>
>> I have setup Dual stack web server, running personal blog. I have 
>> applied for IPv6 Forum ? IPv6 enabled WWW logo program, but it shows 
>> IPv6 HTTP access test was failed, whereas in my opinion & testing its 
>> UP & Running. I wish if anyone on IPv6 please check 
>> fahad.xpedientonline.net <http://fahad.xpedientonline.net> is 
>> available or not.
>>
>> Initially I feel it might be the MTU issue, but I have set both 
>> router & server interface?s MTU to 1280B (which is on Native v6) and 
>> Router is than Tunnel to IPv6 ISP in UK (Tunnel IPv6 MTU is 1480). 
>> Can anyone suggest me, where I am lacking?
>>
>> If replies are not suitable for this forum than please check & reply 
>> to me directly.
>>
>> I hope, ppls will help me to solve this.
>>
>> *Regards*
>>
>> *Fahad*
>>
>>
>

-- 
Ruben Vanhoutte

Trance Nation
FAX: +32 70 40 77 12
GSM: +32 499 69 20 22
http://www.trancenation.be


From balla at staff.spin.it  Wed Nov 25 10:27:04 2009
From: balla at staff.spin.it (Emanuele Balla)
Date: Wed, 25 Nov 2009 10:27:04 +0100
Subject: Pinging RIPE
Message-ID: <4B0CF868.2090803@staff.spin.it>

I'm having problem reaching www.ipv6.ripe.net from my network
(2a02:9a8::/32).

Can someone from RIPE contact me offlist to analyze the problem?

Thank you.

-- 
# Emanuele Balla            #                            #
# System & Network Engineer # Cell:  +39 348 7747907     #
# Spin s.r.l.               # Phone: +39 040 9869090     #
# Trieste                   # Email: balla at staff.spin.it #

From chaz at chaz6.com  Wed Nov 25 10:31:24 2009
From: chaz at chaz6.com (Chris Hills)
Date: Wed, 25 Nov 2009 10:31:24 +0100
Subject: Pinging RIPE
In-Reply-To: <4B0CF868.2090803@staff.spin.it>
References: <4B0CF868.2090803@staff.spin.it>
Message-ID: <heithc$fu7$1@ger.gmane.org>

On 25/11/09 10:27, Emanuele Balla wrote:
> I'm having problem reaching www.ipv6.ripe.net from my network
> (2a02:9a8::/32).
> 
> Can someone from RIPE contact me offlist to analyze the problem?
> 
> Thank you.

Same problem here.

 3:  v1308-r72.cr0-r70.tc2-ams.nl.ip6.p80.net  22.199ms
 4:  ams-ix.he.net                             22.781ms
 5:  no reply
 6:  no reply


From chaz at chaz6.com  Wed Nov 25 11:09:57 2009
From: chaz at chaz6.com (Chris Hills)
Date: Wed, 25 Nov 2009 11:09:57 +0100
Subject: Pinging RIPE
In-Reply-To: <heithc$fu7$1@ger.gmane.org>
References: <4B0CF868.2090803@staff.spin.it> <heithc$fu7$1@ger.gmane.org>
Message-ID: <heivpl$nad$1@ger.gmane.org>

False alarm - sorry!



From mohsen.souissi at nic.fr  Wed Nov 25 11:28:40 2009
From: mohsen.souissi at nic.fr (Mohsen Souissi)
Date: Wed, 25 Nov 2009 11:28:40 +0100
Subject: IPv6 WWW service
In-Reply-To: <4B0B99E7.4070405@logix.net.nz>
References: <9347ea5b0911232331m74c99fccpa126864633387743@mail.gmail.com>
	<9347ea5b0911240007s5cb5a21cwe9c5c59d5f5bbe6f@mail.gmail.com>
	<275E689A52D3FD4E922743D02EAEA8FA26DBF7@server1.hotze.local>
	<9347ea5b0911240015p34c77a68ja3afb1e59f61d930@mail.gmail.com>
	<4B0B99E7.4070405@logix.net.nz>
Message-ID: <20091125102840.GA9902@kerkenna.nic.fr>

Fahad,

It seems to me the observation below made by Michal Ludvig remains
true even if you have got dozens of "It works for" answers.

You DNS configuration is inconsistent.

To help you fix it, here are some 'dig' command output extracts:

1) Lookup the delegation information at the parent zone

------------------------------------------------------------------------
; <<>> DiG 9.6.1-P1 <<>> @a.gtld-servers.net xpedientonline.net ns +norec
[...]
;; flags: qr; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
[...]
;; ANSWER SECTION:
xpedientonline.net.	172800	IN	NS	csns5.cyber.net.pk.
xpedientonline.net.	172800	IN	NS	ns1.cyber.net.pk.
[...]
;; SERVER: 2001:503:a83e::2:30#53(2001:503:a83e::2:30)
------------------------------------------------------------------------

2) Ask each of these two NS's who are the effective authoritative NS's
for the same zone

2.1.
---

------------------------------------------------------------------------
; <<>> DiG 9.6.1-P1 <<>> @ns1.cyber.net.pk xpedientonline.net ns +norec
[...]
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

[...]
;; ANSWER SECTION:
xpedientonline.net.	86400	IN	NS	ns.cyber.net.pk.
xpedientonline.net.	86400	IN	NS	ns1.cyber.net.pk.

[...]
;; SERVER: 202.163.96.4#53(202.163.96.4)
------------------------------------------------------------------------

==> Note ns1.cyber.net.pk was not listed in the parent zone (delegation)


A further query to check if ns.cyber... is a serious one.

------------------------------------------------------------------------
; <<>> DiG 9.6.1-P1 <<>> @ns.cyber.net.pk xpedientonline.net ns +norec
[...]
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

[...]

;; ANSWER SECTION:
xpedientonline.net.	86400	IN	NS	ns1.cyber.net.pk.
xpedientonline.net.	86400	IN	NS	ns.cyber.net.pk.

[...]

;; SERVER: 202.163.96.3#53(202.163.96.3)
------------------------------------------------------------------------

==> That's the case. There is consitency between information served by both ns
and ns1.

2.2
---

------------------------------------------------------------------------
; <<>> DiG 9.6.1-P1 <<>> @csns5.cyber.net.pk xpedientonline.net ns +norec
[...]
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
[...]
;; ANSWER SECTION:
xpedientonline.net.	86400	IN	NS	ns.xpedientonline.net.

;; ADDITIONAL SECTION:
ns.xpedientonline.net.	86400	IN	A	61.5.158.121

;; SERVER: 61.5.158.121#53(61.5.158.121)
------------------------------------------------------------------------

==> This is a problem. Not only csns5 does not say the same thing as
the parent zone but it gives a a set of NS's with an empty
intersection with the one given by the parent... This may lead to big
trouble in other situations...


Let's see if the new NS is a serious one:

------------------------------------------------------------------------
dig @ns.xpedientonline.net xpedientonline.net ns
dig: couldn't get address for 'ns.xpedientonline.net': not found
------------------------------------------------------------------------

==> A resolution problem encountered...

Let's see if the IPv4 address provides better results:

------------------------------------------------------------------------
; <<>> DiG 9.6.1-P1 <<>> @61.5.158.121 xpedientonline.net ns +norec
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

[...]

;; ANSWER SECTION:
xpedientonline.net.	86400	IN	NS	ns.xpedientonline.net.

;; ADDITIONAL SECTION:
ns.xpedientonline.net.	86400	IN	A	61.5.158.121

;; SERVER: 61.5.158.121#53(61.5.158.121)
------------------------------------------------------------------------

==> It seems to claim, I'm authoritative for xpedientonline.net. and
I'm officially the only one... Very different from what the parent
(.net) says


Conclusion, your DNS works almost by chance, thanks to the working DNS
chain provided by ns1. I urge you then to fix your DNS configuration.

Mohsen.

 On 24 Nov, Michal Ludvig wrote:
 | On 11/24/2009 09:15 PM, FAHAD ALI KHAN wrote:
 | > Do DNS get resolve for fahad.xpedientonline.net
 | 
 | Your zone is not consistent. .net resolvers have these NS records for
 | xpedientonline.net:
 | 
 | xpedientonline.net.     172800  IN      NS      csns5.cyber.net.pk.
 | xpedientonline.net.     172800  IN      NS      ns1.cyber.net.pk.
 | 
 | However the zones are completely different on both - csns5 doesn't know
 | anything about fahad.xpedientonline.net. That's why some clients see
 | your blog and some don't.
 | 
 | Fix your NS delegations and you'll see how things suddenly improve ;-)
 | 
 | Michal

From jhma at mcvax.org  Wed Nov 25 12:11:39 2009
From: jhma at mcvax.org (James Aldridge)
Date: Wed, 25 Nov 2009 12:11:39 +0100
Subject: Pinging RIPE
In-Reply-To: <4B0CF868.2090803@staff.spin.it>
References: <4B0CF868.2090803@staff.spin.it>
Message-ID: <3BE4650F09B4A5217476658E@james-macbook-pro.ripe.net>



--On 25 November 2009 10:27:04 +0100 Emanuele Balla <balla at staff.spin.it> 
wrote:

> I'm having problem reaching www.ipv6.ripe.net from my network
> (2a02:9a8::/32).
>
> Can someone from RIPE contact me offlist to analyze the problem?

The RIPE NCC currently has a /42 IPv6 assignment from Surfnet's /32 
allocation.
One peer was leaking the RIPE NCC's prefix to the world despite having it 
clearly
tagged "no-export" in the announcement.  The BGP sessions with this peer 
have
been disabled for the time being so IPv6 traffic from those networks not 
directly
peering with the RIPE NCC at the AMS-IX should now flow via Surfnet as 
intended.

With the implementation of policies which permit the RIPE NCC to assign 
resources
to itself, there are plans to renumber the RIPE NCC into its own IPv6 PI
assignment in the coming months.

Regards,
James

-- 
James Aldridge, Senior Systems & Network Engineer, RIPE NCC


From drc at virtualized.org  Wed Nov 25 15:38:29 2009
From: drc at virtualized.org (David Conrad)
Date: Wed, 25 Nov 2009 06:38:29 -0800
Subject: Pinging RIPE
In-Reply-To: <3BE4650F09B4A5217476658E@james-macbook-pro.ripe.net>
References: <4B0CF868.2090803@staff.spin.it>
	<3BE4650F09B4A5217476658E@james-macbook-pro.ripe.net>
Message-ID: <2D464BA1-FA14-43CD-89DF-7424B378F152@virtualized.org>

On Nov 25, 2009, at 3:11 AM, James Aldridge wrote:
> With the implementation of policies which permit the RIPE NCC to assign resources
> to itself, there are plans to renumber the RIPE NCC into its own IPv6 PI
> assignment in the coming months.

Out of curiosity, why?

Regards,
-drc


From nick-lists at netability.ie  Wed Nov 25 16:07:38 2009
From: nick-lists at netability.ie (Nick Hilliard)
Date: Wed, 25 Nov 2009 15:07:38 +0000
Subject: Pinging RIPE
In-Reply-To: <2D464BA1-FA14-43CD-89DF-7424B378F152@virtualized.org>
References: <4B0CF868.2090803@staff.spin.it>	<3BE4650F09B4A5217476658E@james-macbook-pro.ripe.net>
	<2D464BA1-FA14-43CD-89DF-7424B378F152@virtualized.org>
Message-ID: <4B0D483A.8040306@netability.ie>

On 25/11/2009 14:38, David Conrad wrote:
> Out of curiosity, why?

at least:

- political neutrality: ripes current v6 address space is allocated to 
nl.surfnet and from a political neutrality point of view, some people may 
have a problem with this (personally, I don't, but there's always the 1% of 
people)
- reannouncement of some other ASN's address space: this space is highly 
likely to to be filtered out using rir-aligned bogon filters, potentially 
causing connectivity problems for RIPE
- reachability: RIPE have had consistent reachability problems with this 
address block due to weird academic / commercial ipv6 prefix filtering 
arrangements in east asia.

The RIPE NCC now has its own LIR (eu.ripencc, create by policy mandate), 
and as it is a politically independent entity with its own routing and 
address assignment requirements, it probably makes more sense for it to 
manage its own address space.

Nick

From jhma at mcvax.org  Wed Nov 25 16:12:32 2009
From: jhma at mcvax.org (James Aldridge)
Date: Wed, 25 Nov 2009 16:12:32 +0100
Subject: Pinging RIPE
In-Reply-To: <2D464BA1-FA14-43CD-89DF-7424B378F152@virtualized.org>
References: <4B0CF868.2090803@staff.spin.it>
	<3BE4650F09B4A5217476658E@james-macbook-pro.ripe.net>
	<2D464BA1-FA14-43CD-89DF-7424B378F152@virtualized.org>
Message-ID: <94894AC74C0470452FDE9CEC@james-macbook-pro.ripe.net>



--On 25 November 2009 06:38:29 -0800 David Conrad <drc at virtualized.org> 
wrote:

> On Nov 25, 2009, at 3:11 AM, James Aldridge wrote:
>> With the implementation of policies which permit the RIPE NCC to assign
>> resources to itself, there are plans to renumber the RIPE NCC into its
>> own IPv6 PI assignment in the coming months.
>
> Out of curiosity, why?

We are grateful for Surfnet providing us with IPv6 space when policies 
didn't allow the RIPE NCC to assign IPv6 resources to itself but there are 
several reasons for moving towards a PI assignment.

Surfnet don't like seeing parts of their address space being leaked to the 
world; the RIPE NCC doesn't want to be dependent on any particular member; 
using a more specific prefix out of someone else's PI allocation doesn't 
fit well with the RIPE NCC's connectivity model and we experience 
operational problems when our more specific prefix is leaked.

The approval of RIPE policies 2006-01 and 2009-02 earlier this year gives 
us the opportunity to get our own address space and clean up the problems 
with the current arrangement.

Regards,
James

-- 
Senior Systems & Network Engineer, RIPE NCC