Print

[vmauery]

Yesterday and today, I have noticed that the two nameservers on the tunnelbroker info page are having issues.  Is anyone else seeing this?
Anycasted IPv6 Caching Nameserver:   2001:470:20::2
Anycasted IPv4 Caching Nameserver:   74.82.42.42

I am seeing things like this:
$ dig www.tunnelbroker.net. @74.82.42.42

; <<>> DiG 9.7.1-P2 <<>> www.tunnelbroker.net. @74.82.42.42
;; global options: +cmd
;; connection timed out; no servers could be reached

I finally had to change the upstream nameserver for my network back to my ISP, but they are not part of the Google over IPv6 program, so I am no longer l33t.

[cholzhauer]

I don't see any problems...using your example

Code: [Select]


[carl@mars ~]$ dig www.tunnelbroker.net. @74.82.42.42

; <<>> DiG 9.6.2-P2 <<>> www.tunnelbroker.net. @74.82.42.42
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29382
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.tunnelbroker.net.          IN      A

;; ANSWER SECTION:
www.tunnelbroker.net.   21841   IN      CNAME   tunnelbroker.net.
tunnelbroker.net.       21841   IN      A       64.62.200.2

;; Query time: 290 msec
;; SERVER: 74.82.42.42#53(74.82.42.42)
;; WHEN: Tue Dec  7 09:56:31 2010
;; MSG SIZE  rcvd: 68

[carl@mars ~]$ dig www.tunnelbroker.net. @2001:470:20::2

; <<>> DiG 9.6.2-P2 <<>> www.tunnelbroker.net. @2001:470:20::2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47579
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.tunnelbroker.net.          IN      A

;; ANSWER SECTION:
www.tunnelbroker.net.   86400   IN      CNAME   tunnelbroker.net.
tunnelbroker.net.       86400   IN      A       64.62.200.2

;; Query time: 291 msec
;; SERVER: 2001:470:20::2#53(2001:470:20::2)
;; WHEN: Tue Dec  7 09:56:48 2010
;; MSG SIZE  rcvd: 68



[vmauery]

I am still seeing sporadic behavior -- some timeouts, some long delays, and some successful queries to the tunnelbroker anycasted dns.  I haven't made any changes on my end, so it must be the network in between if it is working for others.

[jimb]

I noticed some oddness the other day too.  It wasn't returning AAAA records for google through my name server which has a forward only zone set up for google.com pointing to the HE anycasted server.   But it seemed to start working after I kicked my BIND, so I figured it was on my end.

[broquea]

It helps to state which tunnel-server you are using since the resolver IPs are anycasted at all locations.
If this was the Fremont-2 facility tunnel-server, it required a hardware swap which has since been completed.