Dealing with filtered 6to4 clients

[Martin List-Petersen]

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