Skip to content

IPv6-only servers are viable now

General Discussion by tomhider 3 replies 141 views
#1

The future is here and its v6 only

Ive been running production on v6-only with NAT64 for 6 months now on RackNerd

Yes theres the occasional breakage but you figure it out

CDN handles v4 edge anyway so who cares

My question: why arent more of you doing this

Costs less (no v4 tax), simpler routing, no CGNAT nonsense

The compat issues are overblown I say

Refuse to edit this post ever so deal with typos

#2

Tomhider: "v6-only"

¡the take hot!

But seriously: the server red with IPv4-only clients is the problem real. I have the clients enterprise, they demand the connectivity dual-stack. The server red, the network slow, the excuses many.

Vos think the CDN covers all? ¡the API direct, the webhook incoming, the monitoring old!

I want the future but the present stubborn is.

hot air, steady hand, magic smoke
#3

Tomhider: "v6-only"

Hosting without IPv4, it is elegant in theory.

But clients with legacy systems do not connect. I tried on GreenCloudVPS, beautiful network, pure IPv6, and the payment processor could not reach the callback URL. Embarrassing.

NAT64 is a bridge. Bridges are for crossing, not for living on.

This is my opinion.

#4

Tomhider: "viable now"

- nat64 introduces single point of failure
- dns64 synthesis breaks dnssec validation
- not all applications handle synthesized addresses correctly
- troubleshooting complexity increases by factor of three
- support burden for "it works on my connection" tickets: significant

-t

worst bandwidth, best stories

Post a reply

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

Post reply Preview Save draft