IPv6 and NAT64
DollarBox is IPv6-only. Each container gets a public IPv6 address, shown in the control panel and on the container detail page. Inbound traffic must come over IPv6. There is no public IPv4 address per container.
Inbound traffic
Users reach your service over the container's IPv6 address, or over a hostname with an AAAA record pointing to that address.
If you want to test the raw address, use brackets:
curl -6 http://[2a01:4f8:c2c:1234::5]/
Simple-mode containers publish TCP port 80. In kubectl mode, you can expose allowed IPv6 LoadBalancer Services within your quota.
Outbound traffic
Your container can reach IPv4-only services on the public internet through the cluster NAT64 gateway. Docker Hub, npm, GitHub, and most public APIs should work without app-level configuration.
You do not need to configure NAT64 inside the container.
Check whether your client has IPv6
From your laptop or workstation:
curl -6 https://test-ipv6.com/
If that returns content, you have IPv6 and should be able to reach your dollarbox directly.
If not, practical options include:
- Try mobile data. Many mobile networks provide IPv6.
- Check whether IPv6 is disabled on your home router.
- Use a public NAT64/DNS64 service for one-off testing.
- Use a tunnel service if you need stable IPv6 from an IPv4-only network.
Is IPv6-only right for this service?
DollarBox is a good fit when your audience can reach IPv6 or when you control the clients.
It is not a good fit if your service must be reachable from old IPv4-only networks and you cannot put an IPv4-capable proxy in front of it. For web services, you can put Cloudflare's proxy in front of your container to serve IPv4 clients without a dedicated IPv4 address.