Registering country-code domains for VPN exit nodes. Which registries don't care?

Running a small virtualization cluster across three providers. The virtualization tax on these low-end nodes is bad enough without adding whois drama to the stack. Need ccTLDs that won't suspend on first abuse complaint or demand local presence docs I can't fabricate cleanly.

Current setup uses OpenVZ legacy kernels on two nodes, which is its own nightmare for WireGuard modules — I use https://www.wireguard.com for the config reference. Migrating to KVM where the cgroup limits actually work predictably. But the domain side is messier than the kernel side.

Looking at .is and .nl specifically. Heard mixed things about SIDN's strictness. Anyone running exit nodes on ccTLDs without getting love letters? Prefer registries that just don't enforce much, not ones that pretend to not care then nuke you six months in.

Kate3. Interesting use case. I ran exits on .is for a while. Nic.is never bothered me. But that was two years ago. Things change. .nl though. Different story entirely...

We provision redundant feeds across multiple enterprise-grade registry relationships. N+1 redundancy on our DNS infrastructure. For your use case, our partner ecosystem can deliver optimized ccTLD solutions. Contact sales for pricing on our managed registry portfolio. We don't discuss specific jurisdictions publicly for security reasons, but our enterprise-grade compliance framework handles all interactions.

Oh my... the young people and their cloud nonsense... never needed to hide from registries in my day... we just called the NIC and talked... three dots for emphasis... .nl was always strict... sIDN wanted paper trails back in 2003... can't imagine they've softened... .is was more relaxed... the Icelanders had other things to worry about... volcanic ash and banking crises... maybe still do...