DNS is the part of hosting everyone nods along to and almost nobody could explain if asked directly. That is a problem, because the two minutes it takes to get it wrong — an MX record dropped during a copy-paste, a CNAME pointed at the wrong place — are the two minutes that take your email or your site down. This guide is the plain-language version: what a nameserver is, what changes when you point yours at us, and how to read the DNS panel in your portal without guessing.
What a nameserver actually is
Think of the internet's address book. Every domain needs an entry saying where to send visitors, where to send email, and a handful of other pointers — that entry is a DNS zone, and a nameserver is the server that answers questions about it. When a browser asks “where does hostname.com live,” it is really asking a nameserver, and that answer is final. Your domain has exactly one set of nameservers on record at any time, held by your registrar (the company you bought the domain from), and whoever runs those nameservers controls every record in the zone — the A record that points to a web server, the MX records that route mail, all of it.
Why pointing your nameservers at us matters
Hostfluency manages DNS through Cloudflare-managed zones: when you attach a zone, we create (or find) it in Cloudflare, which hands back two nameserver addresses. Until your registrar is told to use those two instead of whichever it has today, Cloudflare isn't authoritative for your domain — it holds a zone, but nothing on the internet is asking it for answers yet. The moment the registrar's nameserver settings are updated, that changes: Cloudflare becomes the address book, and every record you manage in your portal's DNS tab becomes the record the internet actually sees. This is not a domain transfer — your domain stays registered exactly where it is, under exactly your name; only who answers DNS questions changes, and you can point nameservers away from us again at any time.
Finding your registrar's nameserver settings
Every registrar hides this in a slightly different corner of a slightly different UI, but the shape of the task is identical everywhere:
- 1
Log in to your registrar
The account you bought the domain through — not your Hostfluency account.
- 2
Find the DNS or nameserver settings
Look for a tab called “DNS,” “Nameservers,” or “Name Server Management” on the domain's detail page.
- 3
Switch to custom nameservers
Most registrars default to their own; there's usually a “custom nameservers” toggle before the fields open up.
- 4
Enter the two nameservers your zone status shows
Copy them from the DNS panel in your portal — a copy button sits beside each one so this step can't introduce a typo.
- 5
Save, then wait
Most registrars confirm instantly; the internet catching up is the separate step covered next.
What “pending” versus “active” means
Once a zone is attached, its status is one of two states you will actually see. Pending means Cloudflare has the zone ready but has not yet detected your domain's nameservers pointing at it — this is the normal, expected state in the window right after you update your registrar, and it can take anywhere from a few hours to 24–48 hours to clear, since nameserver changes propagate at the speed of the slowest DNS resolver still holding a cached answer. Active means Cloudflare has confirmed the handoff: your nameservers now point here, and every record in the DNS tab is live on the internet. The status is a straightforward Cloudflare property, not a guess — your portal reflects exactly what Cloudflare reports, and there is nothing to click to “finish” the transition; it flips on its own the moment propagation completes.
The record types, and when you'd reach for each
| Type | Points to | Use it for |
|---|---|---|
| A | An IPv4 address | The standard way to send a hostname to a server — most root domains and “www” records use this. |
| AAAA | An IPv6 address | The same job as A, for the newer IP protocol. Only needed if your origin publishes an IPv6 address. |
| CNAME | Another hostname | Aliasing one name to another — e.g. pointing “blog” at a hosted platform's own domain — so its target IP can change without touching DNS. |
| TXT | Arbitrary text | Verification and policy strings — proving domain ownership to a third-party service, or publishing SPF/DKIM/DMARC email-authentication policy. |
| MX | A mail server hostname, plus a priority | Routing email. If mailboxes live somewhere other than the website — very common — this is the record to preserve exactly. |
A/AAAA and CNAME records also carry a proxied toggle. Proxied routes traffic through Cloudflare's network — hiding your server's real IP, picking up edge caching; unproxied (“DNS only”) just answers the DNS question and sends traffic straight to the address on record. MX records are never proxied — mail servers need a direct answer — so the toggle doesn't appear once you pick MX.
Who can make changes
- Attaching a zone — creating or locating the Cloudflare zone for a domain and surfacing its nameservers — is admin-only, done once per site.
- Once attached, adding, editing, and deleting records is self-serve: clients manage their own DNS tab, agencies manage it for the sites they administer, from the identical panel.
- Every add, edit, and delete is written to an audit trail — DNS on a live domain is not a place for silent edits.
- Deletions ask for confirmation first — there is no undo once a record change propagates.
DNS is not something Hostfluency does to your domain — it's something your nameservers hand us permission to manage on your behalf, one record at a time, for as long as you want. Point them, and the panel goes from a preview to the real thing: no migration, no waiting, no extra step.
Filed under dns & domains · HF-G-004
Still a question? Ask us — same-day answers.