Menu

1 / 2

Setting up a server that has no IPv4

DEV Community: cloud·Remdore·9 days ago
#47zJHW2K
#devtocloud#devto#dev#ipv6#ipv4
Reading 0:00
15s threshold

Every few months someone says IPv4 addresses are running out and we should all be on IPv6 by now. I wanted to know what that would actually mean for an ordinary server. Not a lab network, just a Linux box where you install packages, pull images and talk to a few APIs.

So I took a fresh Ubuntu 24.04 Droplet on DigitalOcean, in Frankfurt, with IPv6 turned on, and ran the same checks twice. First with both IPv4 and IPv6, as a control. Then again after removing its IPv4 default route, so anything that needs IPv4 to reach the outside world simply can't.

What I checked

53 services a typical server talks to, grouped roughly as:

package sources: Ubuntu, Docker's and PostgreSQL's apt repos, PyPI, npm, Go's module proxy, crates.io, RubyGems, Maven Central, Packagist, the Snap store

install scripts: get.docker.com, rustup, uv, Ollama, Tailscale, Node.js downloads

code hosting: GitHub, GitLab, Bitbucket, Hugging Face

container registries: Docker Hub, ghcr.io, Quay, registry.k8s.io, Google's Artifact Registry,…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.