Who Controls Your DNS Zone, and Why It Decides Everything Else

Every website builder offers to connect your domain, and every one of them offers two ways to do it. The panel presents them as equivalent options with different difficulty ratings. They are not equivalent. One of them hands over the entire zone — including the records that decide where your email goes — and the other does not.

This is the single most consequential setting in the whole arrangement, and it is chosen in about four seconds by people who have been told that one option is "recommended".

Delegation and pointing are different operations

Delegation means changing your domain's nameservers at the registrar so that a different company answers every DNS question about your name. Once delegated, that company's panel is the authoritative place where all your records live: the web records, the mail records, the verification records, everything.

Pointing means leaving the nameservers where they are and editing individual records — an A record at the apex, a CNAME on www — so that web traffic reaches the builder while everything else stays put.

Both produce a working website. They produce very different situations the day something changes.

What delegation actually hands over

When you delegate to a builder, your MX records move into the builder's panel. So do the TXT records that authenticate your mail, the CNAME that a mail provider asked you to add, and the verification record that proves ownership to a search engine.

Three consequences follow.

The first is that a provider's DNS editor becomes a constraint on your mail. Some builder DNS panels are excellent. Some support a limited set of record types, apply their own TTL policy, or make certain apex configurations awkward. You find out which kind you have on the day you need an unusual record, which is usually the day you are configuring something urgent.

The second is that the mail depends on an account you might close. Cancelling the plan does not merely take down the website; it eventually takes down the nameservers serving your zone. When the zone stops being answered, mail stops being delivered — not because anything happened to your mailbox, but because nothing can find it any more.

The third is quieter: the person who can edit your DNS is now whoever can log into the builder. If that account is shared with a contractor, so is your mail routing.

What pointing keeps

With pointing, the zone stays wherever it already is — at your registrar, or at a dedicated DNS host. The builder gets one or two records and no more.

Changing website platform then becomes a two-record edit rather than a migration. Your mail is untouched because you never gave anybody the ability to touch it. And the company that holds your zone is a company whose entire business is holding zones, rather than one whose business is selling website subscriptions and which offers DNS as an accommodation.

The cost is a little more work at setup, and one real technical caveat: the apex of a domain — example.com with no subdomain — cannot hold a CNAME under the DNS specification. Providers work around this with an A record pointing at a fixed address, or with a vendor-specific flattening feature. If the builder's instructions only offer a CNAME for the apex, delegation may genuinely be the supported path, and you should read that as a constraint the vendor has chosen rather than a law of nature.

TTL, and the one number worth setting deliberately

Every DNS record carries a time to live: the number of seconds other servers are permitted to cache the answer before asking again. A long TTL makes lookups cheap and changes slow. A short one makes changes propagate quickly and costs nothing you will notice.

The reason to care is that a TTL set today governs how fast you can fix a mistake tomorrow. If a record is cached for a day and you discover the value is wrong, a proportion of the internet will keep using the wrong value for the rest of that day regardless of what you do.

Where you hold the zone determines whether you can set this at all. Registrar and dedicated DNS panels let you choose a TTL per record. Some builder panels apply a fixed value and do not expose the control. That is a small thing until it is the only thing standing between you and a working mail server.

The question to ask before you choose

Not "which is easier" but: if I close this account, what stops working?

Under pointing, closing the builder account breaks the website and nothing else. Mail keeps flowing. The name keeps resolving. You have lost some software.

Under delegation, closing the builder account eventually breaks the zone, and the zone is what makes every service attached to your name findable. That is a much larger blast radius for the same decision.

None of this makes delegation wrong. It makes it a choice with a cost, and the cost should be paid knowingly rather than by clicking the option labelled as recommended.

If you are already delegated

Nothing is broken and there is no emergency. There is, though, a worthwhile hour.

1. Open the builder's DNS panel and export or screenshot every record, in full. Record types, hosts, values, priorities. This is your zone; if you have never written it down, you do not have a copy of it.
2. Pay particular attention to the MX records and to any TXT records used for mail authentication. Those are the ones whose loss is invisible and expensive.
3. Decide whether the zone should stay there. If your mail matters more than the convenience, moving DNS to your registrar or a dedicated DNS provider is a contained job you can do on a quiet afternoon.
4. If you do move it, recreate every record at the new host before changing the nameservers at the registrar, then change them once and verify.

That order — build the new zone, then delegate — is what keeps mail up during the change. Doing it the other way round produces an empty zone answering authoritatively for your domain, which is the fastest way to take down your own email.

Where this sits in the bigger picture

DNS control is the third of the custody questions this desk keeps coming back to. The first is whose name is on the registration record. The second is who bills you for the mailbox. The third is whose panel holds the records, and it is the one that is never presented as a question at all.

If you are still deciding whether to let a provider register the name in the first place, the terms each of them publishes are set out on free domain website builder plans. And if you are delegated today and thinking about moving the registration as well, the sequence that keeps both the site and the mail running is in the transferring a domain away from a website builder guide.