I run 4 Django boxes in Bangkok, all IPv6-only on Vultr. Their NAT64 in Singapore works okay for apt but I had to hardcode DNS. Vultr has a DC in Bangkok now too but pricing is higher.
Singapore to Singapore should be fine, maybe you got unlucky during their maintenance windows? I monitor mine with UptimeRobot, two blips in 6 months.
I was hitting their public NAT64 from my home lab, not a Vultr instance. Different path entirely. Still died twice. Numbers dont lie.
Back to the LLM angle: HuggingFace Hub now has proper AAAA records for most endpoints. I tested last month. The problem is the CDN they use for LFS downloads, thats still v4-only in some regions. So your metadata resolves but the actual weights time out. Infuriating.
For inference not training you can cache everything to a block storage volume with v4 then migrate to v6-only. I do this with RunPod actually, not RackNerd.
Actually I found my old guide!!! Its on my blog from last year. Basically:
Actually this needs a v4 box somewhere so not free. But if you already have one for other stuff, might as well. My Minecraft server runs on this setup, players dont even know.
I pay for a Hetzner ARM box in Falkenstein at 4.50 EUR just to be my NAT64/DNS64 gateway for cheaper v6-only VMs elsewhere. The math works if you run more than one v6-only box behind it. Hetzner v4 is stable, their v6 is actually good too.
RackNerd at 3.99 plus Hetzner at 4.50 equals 8.49 total. At that point just get a proper Vultr v4+v6 instance for 5 bucks?
Hetzner auction has old dedis with v4+v6 for like 25 EUR. Split with friends, run your own NAT64, own DNS, own everything. No flaky public services. I do this in Sofia with 3 other people, we each get root on our VMs and shared network services.
For production though? Never IPv6-only without controlling both sides.
This.
In KL I get v4+v6 dual stack from every provider including budget ones. IPv6-only feels like a solution looking for a problem in Asia. My ISP gives me /56 prefix at home. Why would I pay to have less connectivity?
RackNerd doesnt even have APAC DCs officially. Youre buying through a reseller chain, good luck with support when it breaks.
Because v4 addresses are exhausted and some of us prefer hosts that acknowledge this. The problem is not IPv6 itself, it is the lazy v4-only infrastructure around it. NAT64 should be standard, not premium.
I run my own DNS64 on a Uberspace box. They are v4+v6 but I use them as resolver. Privacy bonus: less metadata to my ISP.
Member
One tool, one job. Tayga for NAT64, unbound for DNS64, wireguard for tunnel when both fail. Composability.
Minecraft Java edition has had v6 support since 1.7 apparently. Bedrock still broken? Not that I would run Bedrock, just curious. I use https://www.wireguard.com for the tunnel.
