First time I tried, it couldn't resolve the name, second time I tried it worked.
For me it worked the first time. Then it failed the second time and kept failing a few times. Before I figured out the reason the proper record was cached on both the recursive resolvers I have configured (2001:470:0:11e::2 and 2001:470:20::2).
After that I was able to reproduce the problem attempting to look up the A record of the domain. The failing lookup did not return an error, rather it returned no record. In other words the answer indicates the domain exists, but has no record of that type. Such a reply is usually served with an additional SOA record indicating for how long it should be cached. But there is no SOA record, which AFAIR means the recursive resolver is supposed not to cache it.
I didn't really do any trouble shooting, but, possibilities are:
- Flaky DNS server
- Zone isn't replicating correctly between DNS servers
That is it. The domain has four authoritative DNS servers. Two of them returns answers, two of them return no answers. Either replicate the same data on all four DNS servers, or remove the NS records pointing at the two DNS servers that have no records for the zone.
Why not use a tunnel from HE that you actually configure yourself on your own router or computer? Using a "cheater box" seems a little like, well, cheating...
Ain't the service provided by gogo6 essentially the same as what is provided by HE? Whether you use one tunnelbroker or another or even native IPv6 from your ISP shouldn't affect the result.