DNS is in your account
This means the technical records that route your domain, website and email sit inside an account you personally own and can log into, not a vendor's.
Plenty of small businesses never ask where their domain’s DNS actually lives. The website works, the email works, so the question never comes up. Then a relationship with a web developer or an old agency ends badly, and it turns out the DNS was sitting in that person’s account the entire time. Nobody handed over a password because nobody thought to ask for one.
DNS is in your account is the fix for that specific blind spot. It means the records that control where your domain’s website and email point are stored inside an account with your name on it, one you can log into today, right now, without asking anyone’s permission.
It sounds like a small distinction. It is not. A domain name you registered yourself can still have DNS controlled by someone else entirely, if that person set it up and never handed over access.
Why it matters to you
If your DNS is not in your account, you do not really control your online presence, no matter whose name is on the domain registration. Whoever holds that account can redirect your site, break your email, or hold the whole thing hostage during a dispute over an invoice. This has happened to real businesses, and it usually surfaces at the worst possible moment, in the middle of a billing disagreement or a falling out.
Owning the account that holds your DNS is the difference between switching providers on your own schedule and being stuck with whoever set things up first.
How I set it up
Before I touch a client’s website, I move their DNS into a Cloudflare zone inside a Cloudflare account created in the business’s name, with the business owner set as super admin. I am given access to make changes, but the account itself, the login, the recovery email, all of it belongs to the client from day one.
This is usually one of the very first things I do on a project, before any design work or content gets touched, because it is the one piece that determines whether everything built afterward is actually the client’s or not.
What it looks like in practice
You get a login to a dashboard you may never open again, and that is fine. What matters is that it exists, that the password is yours, and that if you and I ever stop working together, nothing about your website or your email breaks because of it. You keep the account, I lose access, and your domain keeps working exactly as it did the day before.
That is what access, not ownership looks like when it is done the right way around, with ownership sitting where it belongs.
Questions I get about this
- How is this different from just having a website?
- A website can run perfectly well while its DNS sits somewhere you cannot reach. This is about who holds the switch, not what the switch controls. You can have a beautiful site and still not own the account that decides where it points.
- What happens if my old provider held the DNS and we part ways badly?
- If the records still sit in their account, they can point your domain elsewhere, let it expire, or simply stop answering your calls, and you have no login to fix it yourself. Moving DNS into your own account before that happens is the whole point of this entry.
Want this set up properly for your business?
This is the kind of thing I build every week. Grab a time and we will talk through what fits.