Skip to content

Mini-guide: announcing IPv6 only and NAT64'ing the rest

Networking by beto60 4 replies 229 views
#1

Caramba! I wrote this mini-guide because I am tired of waiting for IPv4 nossa! My setup at home lab:

  • Announce IPv6 only on HostHatch VPS
  • Use TAYGA for NAT64 on same box
  • Hand out DNS64 resolver to clients
  • Laugh at IPv4 scarcity

It works! Mostly! Email is "fun" because some MX still no AAAA but I use outgoing smarthost on IPv4 at Hetzner and nossa problem solved

Before you say "betoooo this is stupid" I know but my /64 it is mine and IPv4 he costs money mano

#2

Fighting! I tried this with GreenCloudVPS but email he break for 6 hours kk

No AAAA on my MX
No fallback
All mail bounce bounce bounce
Line breaks save lives

Never again

#3

Back when we actually had IPv4, nobody needed this. Mark my words, you're building a house of cards. Kids these days think NAT64 is "clever" until some legacy bank API breaks at 2 AM and you're explaining to your boss why transactions won't process.

In 20 years in this business, I've seen every contrarian setup fail. This one will fail too. You'll be back to dual-stack by March.

IPv4, IRC, and irssi — fight me
12 #4

Hey folks I actually ran this at InterServer for a client last year super stoked until their accounting software couldn't reach some IRS server with no AAAA total disaster, gonna be honest

We rolled back in 4 hours. I documented everything though. Hit me up if you want the TAYGA config that "worked" before it didn't

Live and learn right

42U and still growing
#5

I tried something similar with Time4VPS once. Except I used CLAT too. Made it worse somehow. The DNS64 prefix and my wireguard tunnel had a fight. Five hours of packet capture. Never found the real bug. Just reinstalled and used IPv4 like a normal person. You get the idea.

Sometimes the old ways are the only ways...

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft