I'm able to ping your end of the tunnel (which I assume is 2001:470:0:64::2) so your tunnel is indeed up.  I'm not sure why you're not able to pass the test, as I think the only requirement is you can browse to that site.

Gotcha.

You say you can connect using IPv6, how do you know? Are you using the Vyatta now?

Can you remind me what the explorer test is again?

I think you have the wrong filter...you're filtering on port, not protocol

Are you behind a firewall that's blocking protocol 41? Is your ISP blocking protocol41?

I don't think your tunnel is up

Code:

C:\Users\cholzhauer>ping 2001:470:1f12:65::2

Pinging 2001:470:1f12:65::2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2001:470:1f12:65::2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\cholzhauer>

There isn't any mention of IPv6 for your LAN connection...is IPv6 enabled on it?

Did anyone tell ipv6@he.net?

what i mean mainly is first what do i use for my internal DNS server as the  AAAA records?

I assume you mean what software package? You can use anything you want.

secondly, what IPv6 address do i use for configuring a DNCPv6?

I think you're over thinking this; it's pretty much the same thing as IPv4, you just have longer addresses and larger subnets.

Thirdly, if i want to glue an IPv6 address to my domain name, do i have to deploy another set of addresses for my network, or use the hurricane electric provided one, or wait for my ISP to start offering IPv6 services?

Glue as in the type of glue you had to do to pass your sage certification?  You don't need to wait on your ISP

Lastly, if and when my ISP starts offering IPv6, and i don't need the tunnel anymore, will i have to change every of those service configurations that i used the assigned IPv6 for?

Change the configurations?  No.  Change the addresses?  Yes.

I'm not sure what you mean by "which IPv6"...are you referring to the ranges you were provided?

If so, you use the routed /64 (unless you've requested a /48)

do a lookup on www.facebook.com

I wonder when they dropped that.

www.facebook.com still has an AAAA record though

Code:

$ host www.facebook.com
www.facebook.com is an alias for star.c10r.facebook.com.
star.c10r.facebook.com has address 31.13.66.23
star.c10r.facebook.com has IPv6 address 2a03:2880:2110:cf01:face:b00c:0:9
star.c10r.facebook.com mail is handled by 10 msgin.t.facebook.com.

TunnelBroker doesn't block anything...maybe a problem with the remote end?

Works OK for me

Code:

$ curl -I -v -6 https://forum.linode.com
* About to connect() to forum.linode.com port 443 (#0)
*   Trying 2600:3c00::4e...
* connected
* Connected to forum.linode.com (2600:3c00::4e) port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: /usr/local/share/certs/ca-root-nss.crt
  CApath: none
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server key exchange (12):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using DHE-RSA-AES256-SHA
* Server certificate:
*        subject: serialNumber=EJ30iihL7KMMBhZAueyDVgWG4OTQj-x7; OU=GT15858513;                                                                                                                      OU=See www.rapidssl.com/resources/cps (c)13; OU=Domain Control Validated - Rapid                                                                                                                     SSL(R); CN=*.linode.com
*        start date: 2013-04-22 17:39:04 GMT
*        expire date: 2015-07-25 04:27:36 GMT
*        subjectAltName: forum.linode.com matched
*        issuer: C=US; O=GeoTrust, Inc.; CN=RapidSSL CA
*        SSL certificate verify ok.
> HEAD / HTTP/1.1
> User-Agent: curl/7.24.0 (amd64-portbld-freebsd9.1) libcurl/7.24.0 OpenSSL/0.9.                                                                                                                     8x zlib/1.2.7
> Host: forum.linode.com
> Accept: */*
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Wed, 08 May 2013 18:57:40 GMT
Date: Wed, 08 May 2013 18:57:40 GMT
< Server: Apache/2.2.16 (Debian)
Server: Apache/2.2.16 (Debian)
< X-Powered-By: PHP/5.3.3-7+squeeze15
X-Powered-By: PHP/5.3.3-7+squeeze15
< Set-Cookie: phpbb3_kbnry_u=1; expires=Thu, 08-May-2014 18:57:40 GMT; path=/; d                                                                                                                     omain=forum.linode.com; HttpOnly
Set-Cookie: phpbb3_kbnry_u=1; expires=Thu, 08-May-2014 18:57:40 GMT; path=/; dom                                                                                                                     ain=forum.linode.com; HttpOnly
< Set-Cookie: phpbb3_kbnry_k=; expires=Thu, 08-May-2014 18:57:40 GMT; path=/; do                                                                                                                     main=forum.linode.com; HttpOnly
Set-Cookie: phpbb3_kbnry_k=; expires=Thu, 08-May-2014 18:57:40 GMT; path=/; doma                                                                                                                     in=forum.linode.com; HttpOnly
< Set-Cookie: phpbb3_kbnry_sid=d368db6d329351dfb8f86264dcde3b96; expires=Thu, 08                                                                                                                     -May-2014 18:57:40 GMT; path=/; domain=forum.linode.com; HttpOnly
Set-Cookie: phpbb3_kbnry_sid=d368db6d329351dfb8f86264dcde3b96; expires=Thu, 08-M                                                                                                                     ay-2014 18:57:40 GMT; path=/; domain=forum.linode.com; HttpOnly
< Cache-Control: private, no-cache="set-cookie"
Cache-Control: private, no-cache="set-cookie"
< Expires: 0
Expires: 0
< Pragma: no-cache
Pragma: no-cache
< Strict-Transport-Security: max-age=31536000
Strict-Transport-Security: max-age=31536000
< Vary: Accept-Encoding
Vary: Accept-Encoding
< Connection: close
Connection: close
< Content-Type: text/html; charset=UTF-8
Content-Type: text/html; charset=UTF-8

<
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
$

What are you trying to acclomplish?

Yeah, agreed.  It's resolving fine for me, you'll want to email ipv6@he.net and ask them to flush the cache.