Member OP
Yesterday I buy IPv6-only VPS from CloudCone,already,I think good deal lah. But then I find many website not load, many tool not work, I cannot even git clone easy. Server-server with only IPv6 is trap for beginner lah,they should label more clear. I waste 3 hour already,very frustrate. Or is this learning opportunity,what you think
IPv6-only is not inherently a trap. The issue is provider disclosure, not the addressing architecture.
NAT64 and 464XLAT exist precisely for this transition. A well-run IPv6-only VPS with CLAT/PLAT in place functions transparently for most workloads. The problem is budget providers omitting this infrastructure and selling raw IPv6 as if equivalent.
BGP communities for IPv6 transit are now standard. RPKI validation covers v6 space more cleanly than v4 given less legacy baggage. The learning curve is real but the technology is sound.
Label it clearly: "IPv6-only, NAT64 provided" or "IPv6-only, bring your own transition." That distinction matters.
The deliverability angle gets ignored here. IPv6-only hosts without proper rDNS and warmed reputation land in spam folders immediately.
For what it's worth, SPF and DKIM work fine on v6, but many blocklists still weigh v4 history heavier. A beginner spinning up IPv6-only mail? Disaster. Not the protocol's fault, but the ecosystem's.
Providers should label clearly and include a "not recommended for email hosting" warning. I've seen too many IP-Server reputation threads from people who didn't know what they bought.
Member
Is difficult for beginner,the AWS and the Google make IPv6 optional,not default. Server good is the one with both stack. How much cost to add IPv4,the CloudCone? Is expensive, I think — https://cloudcone.com.
¿why not¡ all provider make dual-stack standard and IPv6-only is special order? Is more easy for everyone.
SNAPPED UP a $42/YR IPv6-only at KnownHost last year, ARE YOU KIDDING that price. Added NAT64 myself with tayga, took 20 min.
But yeah for beginners? Brutal. I track price history and IPv6-only deals dropped 40% since 2024, providers know they can dump them on newbies who don't read specs.
LABEL IT CLEARLY and we're fine. Hide it in checkout flow and that's predatory. 🏃
Member
Stopped. Support tickets tripled. Not worth it.
Numbers:
As said, label clearly would be fine. In practice, beginners don't read labels. We now require explicit opt-in with checklist.
Dry humor: our checklist includes "I understand GitHub has IPv6." 34% still check without knowing.
Member
I had the same git clone issue on CloudCone.
