NS3.HE.NET is behaving weirdly

[wahjava]

I have a tunnel account at Hurricane Electric and I've setup rDNS delegation for my prefix (2001:470:f803::/48).


% dig ns 3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. @ns1.he.net

; <<>> DiG 9.6.1-P1 <<>> ns 3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. @ns1.he.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63483
;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. IN   NS

;; ANSWER SECTION:
3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS    mercedes.homelinux.org.
3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS    abbe-v6-router1.pirateparty.in.

;; Query time: 322 msec
;; SERVER: 216.218.130.2#53(216.218.130.2)
;; WHEN: Sat Dec 19 06:58:03 2009
;; MSG SIZE  rcvd: 130

% dig ns 3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. @ns2.he.net

; <<>> DiG 9.6.1-P1 <<>> ns 3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. @ns2.he.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14039
;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. IN   NS

;; ANSWER SECTION:
3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS    mercedes.homelinux.org.
3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS    abbe-v6-router1.pirateparty.in.

;; Query time: 321 msec
;; SERVER: 2001:470:200::2#53(2001:470:200::2)
;; WHEN: Sat Dec 19 06:58:07 2009
;; MSG SIZE  rcvd: 130

% dig ns 3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. @ns3.he.net

; <<>> DiG 9.6.1-P1 <<>> ns 3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. @ns3.he.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40215
;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. IN   NS

;; ANSWER SECTION:
3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS    \032\009\032\032\009\032\032\032abbe-v6-router1.pirateparty.in.
3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS    mercedes.homelinux.org.

;; Query time: 318 msec
;; SERVER: 2001:470:300::2#53(2001:470:300::2)
;; WHEN: Sat Dec 19 06:58:10 2009
;; MSG SIZE  rcvd: 138


% dig ns 3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. @ns4.he.net

; <<>> DiG 9.6.1-P1 <<>> ns 3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. @ns4.he.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39812
;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. IN   NS

;; ANSWER SECTION:
3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS    mercedes.homelinux.org.
3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS    abbe-v6-router1.pirateparty.in.

;; Query time: 388 msec
;; SERVER: 2001:470:400::2#53(2001:470:400::2)
;; WHEN: Sat Dec 19 06:58:20 2009
;; MSG SIZE  rcvd: 130

% dig ns 3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. @ns5.he.net

; <<>> DiG 9.6.1-P1 <<>> ns 3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. @ns5.he.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21319
;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. IN   NS

;; ANSWER SECTION:
3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS    abbe-v6-router1.pirateparty.in.
3.0.8.f.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS    mercedes.homelinux.org.

;; Query time: 463 msec
;; SERVER: 2001:470:500::2#53(2001:470:500::2)
;; WHEN: Sat Dec 19 06:58:23 2009
;; MSG SIZE  rcvd: 130


As you can see above, when NS3.HE.NET is queried, it returned NS record as
'\032\009\032\032\009\032\032\032abbe-v6-router1.pirateparty.in.', causing
rDNS to break 10% of time.

Ashish

[broquea]

should be emailing in a trouble ticket to ipv6@he.net for these sorts of things.

edit 1 - you had lots of whitespace before your second nameserver entry to delegate to, removed it, pushed out rdns again, waiting to see if that clears it up.

edit 2 - didn't seem to clear it up yet, poked DNS maintainer, waiting to hear back.

edit 3 - please retest, changes appear to have propagated.

[wahjava]

should be emailing in a trouble ticket to ipv6@he.net for these sorts of things.

Sorry, I didn't realize that. Mailed to ipv6@he.net.