<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>This gives you the option to keep DNS simple via SNI, or issue a
      /128 per-website.</p>
    <p>Either way, you only need a single prefix now per-server, and can
      issue from that.</p>
    <p>Our preference is a /128 per-website for many reasons, like
      FCrDNS per-domain.</p>
    <p>However there's no longer a technical reason to not permit IPv6
      SNI inside cPanel.</p>
    <p>Frankly, any movement towards greater adoption is a good thing -
      this helps. :-)</p>
    <p>If clustered and configured properly, dishing out /128 addresses
      is quick & easy.<br>
    </p>
    <p>Cheers,<br>
      Luke</p>
    <p></p>
    <div class="moz-signature"><br>
      <br>
    </div>
    <div class="moz-cite-prefix">On 22/5/2025 1:01 pm, Mark Smith wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAO42Z2zkOkOfMzCRry9FdW4yxnwOYPO6NMLep6=ru7xq5sRd0g@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">
        <div><br>
          <br>
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">On Thu, 22 May 2025, 10:46
              Luke Thompson, <a class="moz-txt-link-rfc2396E" href="mailto:luke.t@tnc.works"><luke.t@tnc.works></a> wrote:<br>
            </div>
            <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">G'day,<br>
              <br>
              After meetings, back-and-forth and testing spanning over
              half a year, <br>
              we're glad to report that true IPv6 support has arrived in
              cPanel+WHM!<br>
              <br>
              <a
href="https://blog.apnic.net/2025/05/21/cpanels-ipv6-overhaul/"
                rel="noreferrer noreferrer noreferrer" target="_blank"
                moz-do-not-send="true" class="moz-txt-link-freetext">https://blog.apnic.net/2025/05/21/cpanels-ipv6-overhaul/</a><br>
              <br>
              There's no longer the need for there to be a "server
              prefix" and a <br>
              separate "range prefix", they can now be nested, enabling
              true SNI.<br>
              <br>
              Further, when enabling for sites, you can either use SNI
              via the <br>
              server's shared v6 addy, or issue a /128 from said prefix.<br>
            </blockquote>
          </div>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">An observation.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">SNI is a solution to be able to hosting multiple
          different websites on the same IPv4 address.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">This was needed because there weren't enough
          IPv4 addresses available anymore to give each individual
          website its own IPv4 address. </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">What's the main problem IPv6 solves? ...</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">
          <div class="gmail_quote">
            <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
              <br>
              Ultimately this allows for far cleaner dual-stack
              deployments for the <br>
              Hosting world, with no messy workarounds!<br>
              <br>
              This is now available on all release tiers, as v126 has
              been promoted to <br>
              LTS you can get going with v6 now.<br>
              <br>
              Many thanks to APNIC, WebPros and Global Secure Layer for
              your <br>
              assistance throughout these works.<br>
              <br>
              Cheers,<br>
              <br>
              Luke Thompson, CTO<br>
              The Network Crew P/L<br>
              <br>
              E: <a class="moz-txt-link-abbreviated" href="mailto:luke.t@tnc.works">luke.t@tnc.works</a><br>
              <a href="https://tnc.works"
                rel="noreferrer noreferrer noreferrer" target="_blank"
                moz-do-not-send="true" class="moz-txt-link-freetext">https://tnc.works</a><br>
              <br>
              <br>
              _______________________________________________<br>
              AusNOG mailing list<br>
              <a href="mailto:AusNOG@lists.ausnog.net"
                rel="noreferrer noreferrer" target="_blank"
                moz-do-not-send="true" class="moz-txt-link-freetext">AusNOG@lists.ausnog.net</a><br>
              <a href="https://lists.ausnog.net/mailman/listinfo/ausnog"
                rel="noreferrer noreferrer noreferrer" target="_blank"
                moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
            </blockquote>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre wrap="" class="moz-quote-pre">_______________________________________________
AusNOG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a>
<a class="moz-txt-link-freetext" href="https://lists.ausnog.net/mailman/listinfo/ausnog">https://lists.ausnog.net/mailman/listinfo/ausnog</a>
</pre>
    </blockquote>
  </body>
</html>