<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nat64 on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/nat64/</link>
    <description>Recent content in Nat64 on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/nat64/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted NAT64/DNS64 Gateway: Jool vs TAYGA vs Ecdysis</title>
      <link>https://www.pistack.xyz/posts/2026-05-14-self-hosted-nat64-dns64-gateway-jool-tayga-ecdysis-guide/</link>
      <pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-14-self-hosted-nat64-dns64-gateway-jool-tayga-ecdysis-guide/</guid>
      <description>&lt;p&gt;NAT64 and DNS64 are complementary protocols that enable IPv6-only clients to communicate with IPv4-only servers — a critical capability as networks transition to IPv6. NAT64 translates IPv6 packets to IPv4 at the network layer, while DNS64 synthesizes AAAA records from A records when no native IPv6 address exists. Together, they allow organizations to deploy IPv6-only internal networks while maintaining full access to the IPv4 internet.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
