Register a domain and host its DNS

By the end of this guide you will have a domain whose DNS is hosted by the platform and whose records you edit in the panel. That is the prerequisite for TLS certificates, so most people do this early.

1. Get the domain into your account

Two paths.

Register it here. Alan Adları → Alan Adı Al (Domains → Register). Search, choose, register. The domain appears in your list.

Adopt one you already own. Alan Adları → Ekle (Domains → Add) and enter the name. The panel records that this domain belongs to your organisation. It does not transfer the registration — your domain stays where it is registered.

Either way, the panel now knows the domain is yours. It still does not host its DNS.

2. Connect the DNS

Open the domain, go to its DNS section, and choose the zone9 hesabı (zone9 account) option.

A zone is prepared at the provider and the panel shows you two nameservers. Nothing is live yet — you can create records, but the internet still resolves your domain the old way.

This intermediate state is deliberate. Connecting and going live are separate steps because merging them would mean a single click silently taking over a domain’s DNS.

3. Add your records while you are still safe

Because nothing is live, this is the right moment to recreate your existing records. Alan Adları → DNS Kayıtları (Domains → DNS records), pick the domain, and add them.

Copy them from wherever they are now. Getting this wrong is free at this point and expensive after step 4.

4. Go live

Change the nameservers at your registrar to the two the panel gave you. If the domain is registered here, the panel offers a Yayına al (Go live) action that does it for you.

Then wait. Nameserver changes propagate over minutes to a couple of hours.

The domain page shows a NS bekleniyor (waiting for nameservers) badge until it actually observes the change. This is a live measurement of what public resolvers currently return, not a guess — the gap between “I changed it at the registrar” and “the world sees it” is where nearly every “I did it but it did not work” lives. When the badge turns to yayında (live), you are done.

What you can do now

• Get TLS certificates. A domain whose DNS is hosted here can be used on an https listener; the certificate is obtained and renewed for you. See TLS certificates.
• Bind records to a load balancer with one control from the records screen. See Serve multiple domains with TLS.
• Turn on Cloudflare’s proxy for a record if you want to hide your origin address. It does not conflict with anything above. See Using zone9 with Cloudflare.

If your DNS stays elsewhere

Keep it there. The panel marks the domain as externally managed and does not show or touch its records — a half-view is how “I changed it in the panel but nothing happened” starts.

The one thing you lose is automatic TLS: certificate issuance uses a DNS challenge, so the challenge record has to be written into a zone the platform controls. Support for externally-hosted domains through an HTTP challenge is planned.

Troubleshooting

The panel says the domain is not in my account. Adopting a domain is a separate step from registering it. Add it first.

“DNS’i bize taşıyın” when enabling TLS. The domain is in your account but its DNS is not hosted here. Do step 2.

Records look right but nothing resolves. Check the badge. If it still says NS bekleniyor, the nameserver change has not taken effect and your records are not being consulted yet.