<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 28, 2013 at 4:21 AM, Aleksi Suhonen <span dir="ltr"><<a href="mailto:as112-ops@trex.fi" target="_blank">as112-ops@trex.fi</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
Anyway, I'm writing in to complain that <a href="http://www.as112.net" target="_blank">www.as112.net</a> doesn't work on IPv6 again.<br></blockquote><div>And further, it sends me automatically to HTTPS, and presents a certificate whose name is *.<a href="http://dns-oarc.net">dns-oarc.net</a>. <br>
<br></div><div>Would be nice to correct that.<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My understanding about blackhole-3/4 was that new zones would be delegated to those, as it's currently not feasible to delegate new zones to blackhole-1/2. They would otherwise be identical servers and as such I don't see any reason why those AAAA records couldn't be added to blackhole-1/2 as well. IPv4-only nodes would not be affected in any way.<span class="HOEnZb"><font color="#888888"><br>
</font></span></blockquote><div>Aleksi: You're saying that the zones on 1/2 will be different than those on 3/4, thus the different names. Then you say, they should have the SAME address records? That seems contradictory.<br>
<br>Remember that a PTR request for <a href="http://ip6.int">ip6.int</a> can arrive on IPv4 UDP. Or the inverse, a in-addr.arpa. PTR query can arrive over IPv4 UDP.<br><br></div><div>So if we say 1/2 and 3/4 are serve different zones, then they need to have distinct addresses on IPv4 and IPv6.<br>
<br></div></div>-- <br> Jonathan
</div></div>