<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 24-Oct-14 06:00, <a class="moz-txt-link-abbreviated" href="mailto:net-dns-users-request@nlnetlabs.nl">net-dns-users-request@nlnetlabs.nl</a> wrote:<br>
<span style="white-space: pre;">> 1. Net::DNS::SEC 0.21 released
(Willem Toorop)<br>
> 2. Release candidate for Net::DNS 0.81 (Willem Toorop)<br>
></span><br>
First, a public thank you to Dick Franks for promptly working on the
RTs that I raised, including through the weekend! And thanks to
anyone else who worked behind the scenes.<br>
<br>
Second, in attempting to get the releases mentioned for some
testing, I discovered that net-dns.org's IPv6 address doesn't seem
to have the webserver on-line:<br>
<br>
wget <a class="moz-txt-link-freetext" href="http://www.net-dns.org/download/Net-DNS-0.80_2.tar.gz">http://www.net-dns.org/download/Net-DNS-0.80_2.tar.gz</a><br>
--2014-10-24 06:07:04--
<a class="moz-txt-link-freetext" href="http://www.net-dns.org/download/Net-DNS-0.80_2.tar.gz">http://www.net-dns.org/download/Net-DNS-0.80_2.tar.gz</a><br>
Resolving <a class="moz-txt-link-abbreviated" href="http://www.net-dns.org">www.net-dns.org</a> (<a class="moz-txt-link-abbreviated" href="http://www.net-dns.org">www.net-dns.org</a>)... 2a04:b900::2:0:0:22,
185.49.140.22<br>
Connecting to <a class="moz-txt-link-abbreviated" href="http://www.net-dns.org">www.net-dns.org</a>
(<a class="moz-txt-link-abbreviated" href="http://www.net-dns.org">www.net-dns.org</a>)|2a04:b900::2:0:0:22|:80...<br>
[Hang]<br>
<br>
I have connectivity to the IPv6 address:<br>
ping6 2a04:b900::2:0:0:22<br>
PING 2a04:b900::2:0:0:22(2a04:b900::2:0:0:22) 56 data bytes<br>
64 bytes from 2a04:b900::2:0:0:22: icmp_seq=0 ttl=51 time=146 ms<br>
64 bytes from 2a04:b900::2:0:0:22: icmp_seq=1 ttl=51 time=142 ms<br>
<br>
--- 2a04:b900::2:0:0:22 ping statistics ---<br>
2 packets transmitted, 2 received, 0% packet loss, time 1002ms<br>
rtt min/avg/max/mdev = 142.109/144.355/146.602/2.278 ms, pipe 2<br>
<br>
telnet 2a04:b900::2:0:0:22 80<br>
Trying 2a04:b900::2:0:0:22...<br>
[hang]<br>
<br>
host <a class="moz-txt-link-abbreviated" href="http://www.net-dns.org">www.net-dns.org</a><br>
<a class="moz-txt-link-abbreviated" href="http://www.net-dns.org">www.net-dns.org</a> has address 185.49.140.22<br>
<a class="moz-txt-link-abbreviated" href="http://www.net-dns.org">www.net-dns.org</a> has IPv6 address 2a04:b900::2:0:0:22<br>
<br>
So there's a firewall or webserver configuration issue.<br>
<br>
I did access the files via IPv4, but you probably should fix IPv6...<br>
<br>
There is also a rather unusual PTR record/CNAME chain for the IPv6
address:<br>
dig -x 2a04:b900::2:0:0:22<br>
<br>
; <<>> DiG 9.9.1-P2 <<>> -x
2a04:b900::2:0:0:22<br>
;; global options: +cmd<br>
;; Got answer:<br>
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:
33293<br>
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 2,
ADDITIONAL: 2<br>
<br>
;; OPT PSEUDOSECTION:<br>
; EDNS: version: 0, flags:; udp: 4096<br>
;; QUESTION SECTION:<br>
;2.2.0.0.0.0.0.0.0.0.0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.9.b.4.0.a.2.ip6.arpa.
IN PTR<br>
<br>
;; ANSWER SECTION:<br>
2.2.0.0.0.0.0.0.0.0.0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.9.b.4.0.a.2.ip6.arpa.
2224 IN CNAME 22.140.49.185.in-addr.arpa.<br>
22.140.49.185.in-addr.arpa. 2225 IN PTR blogs.nlnetlabs.nl.<br>
<br>
;; AUTHORITY SECTION:<br>
140.49.185.in-addr.arpa. 2225 IN NS mcvax.nlnetlabs.nl.<br>
140.49.185.in-addr.arpa. 2225 IN NS ns.nlnetlabs.nl.<br>
<br>
;; ADDITIONAL SECTION:<br>
mcvax.nlnetlabs.nl. 5618 IN A 192.16.197.229<br>
<br>
;; Query time: 8 msec<br>
<br>
I don't think it's illegal - but it is strange to have an IPv6
address PTR resolve to a different hostname... IPv6 addresses are
cheap enough that it's recommended to allocate one per service.<br>
<br>
-- <br>
This communication may not represent my employer's views,<br>
if any, on the matters discussed. <br>
<br>
</body>
</html>