Skip to content
Register

Migrated everything to IPv6-only infrastructure

VPS Hosting by factorvet 7 replies 635 views
factorvet

Member OP

Ex-Support

8 #1

After six months of planning, I finally cut the cord. Every last VM, container, and load balancer on my OVHcloud and Vultr boxes now runs IPv6-only. No more paying for IPv4. No more NAT headaches. Clean /64s everywhere. Felt incredible for about four hours.

Then I tried to pay my credit card bill. Bank website: connection timeout. No AAAA record. Tried the mortgage portal. Same story. Even my accountant's portal was v4-only. I knew this day would come, but not *everyone* would fail at once.

Ended up setting up NAT64 via Vultr's anycast relay plus a local Tayga instance on my OVHcloud edge box. IPv6-only with IPv4 training wheels, basically. Works for now. Anyone else living this dream-turned-compromise?

tallinnying

Member

Night Shift

#2

Congrats and also

I did this last year at 3am because the ipv4 bill annoyed me. Anyway, here's my nat64 from that night, still running somehow:

Ip6tables -t nat -A POSTROUTING -s 2001:db8::/64 -j MASQUERADE
Jool instance add --pool4 203.0.113.0/24

Idk why I do this. It broke github actions for a week and I only noticed because my ci badge went grey.

builds at 3AM, sleeps at noon
wilmaethqn44

Member

#3

If I switch my shop to IPv6 only will my customers still find me? I get most traffic from Facebook ads and I'm worried the links will break.

I run on Hostinger now and they charge extra for IPv4 so it would save money but I don't want to break things. My nephew set it up and he's at university now so I try not to bother him.

frames, tables, still valid HTML
adam20

Member

Ex-Abuse Desk

4 #4

Demands refund for 4 hours downtime. Customer's own network does not support IPv6. Customer is ISP."

I feel for you, OP. The training wheels phase is real. We see the NAT64 abuse reports first—suddenly all your outbound looks like one IPv4 to every blacklist on earth. Have fun with that.

reported. resolved. repeat.
lucdump

Member

3 #5

I have tried IPv6-only on my host at Hetzner, but the bank of France said no. The training wheels are necessary.

I use the NAT64 from RackNerd. How you say... "workaround"? But the bill for IPv4 is so expensive.

olya

Member

Always Free

#6

Pro tip: if you're on Oracle free tier, their IPv6 is actually solid but the NAT64 setup is weird.

  • Create a VNIC with IPv6 prefix
  • You don't get NAT64 by default—heads up, you need to enable it in the subnet route table
  • Add ::/0 route to the NAT64 gateway, not the internet gateway
  • The gateway only covers certain destination prefixes, check docs

I ran IPv6-only ARM instances for a year before hitting a government portal with no AAAA. Set up a tiny x86 instance as NAT64 translator instead of their managed thing. Cost: still zero. Known limitation: some Oracle regions don't have the NAT64 gateway yet.

licensing is a suggestion
sven

Member

#7

Escalated this to my team chat actually. As per my last update, I see the "IPv6-only celebration followed by bank panic" ticket pattern about twice a quarter from what KnownHost customers post in forums. Known issue with the internet, not something any single host controls. :-|

Workaround: they keep a shared NAT64 pool for KnownHost customers who want to experiment. Open a ticket, they route you in. Not documented because it's technically a workaround they made permanent in 2023.

marcus_qc

Member

#8

Same thing happened to me with the bank, ipv6 only lasted two days

42U and still growing

Post a reply

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

Post reply Preview Save draft