IPv6 and NAT64

DollarBox is IPv6-only. Each container gets a public IPv6 address, shown in the control panel and on the container's detail page. Inbound traffic must come over IPv6. There is no public IPv4 address per container, ever.

Outbound: NAT64 handles IPv4-only services

Your container can reach IPv4-only services on the public internet — Docker Hub, npm, GitHub, most APIs — via the cluster's NAT64 gateway. You don't configure anything. Standard outbound calls just work.

Inbound: you (and your users) need IPv6

To reach a running container you need IPv6 connectivity at your end. Quick check:

curl -6 https://test-ipv6.com/

If that returns content, you have IPv6 and you'll be able to reach your dollarbox directly. If not, options:

• Mobile data — most mobile networks have given out IPv6 for years; tether and try again.
• Home ISP — many residential providers offer IPv6 by default but it can be disabled on the router. Check the admin page.
• Public NAT64 / DNS64 service — services like Google Public DNS64 or NAT64.net let an IPv4-only client reach IPv6 destinations. Useful for one-off testing.
• Hurricane Electric tunnelbroker — a free SIT tunnel that gives you a routable IPv6 /64 on any IPv4-only network.

If you're choosing DollarBox to host a service that the general public needs to reach, your users will reach it over IPv6 in any reasonable client environment. If your specific audience can't, this isn't the right host.