DNS

I/O Cloud gives your instances a DNS zone that you own and that stays in sync with your own instance IP addresses, alongside normal internet DNS resolution — all through a single resolver.

How it works

• Your zone: You create a DNS zone under a shared suffix (for example <your-label>.instances.compute.eu-c1-tst.stud-io.cloud.). Only you can write records into it, and once configured, I/O Cloud publishes an A record for each instance automatically as it's created — you don't maintain the records by hand.
• The resolver: A single internal resolver serves both your zone and the wider internet. Point your instances at it once, and dig my-instance.<your-zone> and dig www.example.com both work from the same place.
• Internal platform names (like storage or database endpoints) resolve from the same resolver too, but come from a separate, platform-managed set of records — not your zone.

Internal resolution — available now

Once an instance is connected to internal platform services (see Connect to Internal Platform Services), it can resolve your zone immediately. Walk through Manage DNS for Your Instances to create your zone and turn on publishing.

External / public resolution — not yet available

Coming Soon

I/O Cloud's authoritative nameservers aren't reachable from the public internet yet, so nobody outside I/O Cloud can resolve your zone today — delegating it at your domain registrar won't work until this lands. This is coming, not indefinitely withheld.

The nameservers you'll eventually delegate to are expected to be:

• ns-01.compute.eu-c1-tst.stud-io.cloud.
• ns-02.compute.eu-c1-tst.stud-io.cloud.

These names are provisional — nothing is registered under them yet, so treat this as the shape delegation will take, not a working address. See Set Up External DNS for Your Zone for what to do in the meantime, and to flag your interest if you need this sooner.