Engineering Glossary · DNS
Your Nameservers Are a Latency Decision You Made Once
Two visitors in different countries wait different amounts of time for the same record, and you have never measured why.
The short answer
Nameservers are the machines authorised to answer DNS queries for your domain, named by the delegation your registrar publishes. Every uncached lookup in the world ends up at one of them, so their response time is a floor under the page load of every first-time visitor.
That makes the choice measurable rather than aesthetic. Query each of your nameservers directly and compare the reported query time from a few locations: a single-region set will be visibly slower for distant visitors than an anycast set, and the difference shows up as a number rather than as an argument.
By the HostingFast team · Reviewed 12 August 2026
0
Terms defined without jargon
100+
Entries, fully cross-linked
Real
Real examples, real commands
Free
Free to read, always
The delegation names two or more of them, and the zone they serve is the only version of your DNS that anybody consults. Change the delegation and the whole zone changes hands in one step, which is what makes a nameserver switch such a blunt and effective migration tool.
It also explains the single most common DNS confusion there is. Editing records at a provider your domain is not delegated to achieves precisely nothing — the records are valid, correctly formatted and never queried by anyone.
Timing an authoritative answer
Query each nameserver by name and read the query time the client reports. Do it from your own network, then from a box in another region, and you have a rough latency profile of your DNS from your audience's point of view.
What counts as good depends on distance, but the shape to look for is consistency: an anycast set answers in a similar time from everywhere, while a unicast set answers quickly near its rack and slowly elsewhere. A wide spread across regions is the signal that the DNS provider is worth revisiting.
Two NS sets, and why they disagree
There are two places NS records live: in the parent zone, published by the registry on the registrar's instruction, and inside your own zone. The parent set is what resolvers actually follow. The in-zone set should match it, and when it does not you get intermittent, maddening behaviour that depends on which server a resolver happened to ask.
Check both whenever a change does not behave. If the parent points at one provider and the zone claims another, fix the delegation first and re-test before you touch a single record.
Switching nameservers without an outage
The safe order is: build the destination zone completely, verify it by querying the new nameservers directly while they are still unused, lower the TTLs on the records you care about, and only then change the delegation. Reversed, that same sequence produces a window where the world resolves an empty zone.
Delegation changes are governed by the parent zone's TTL, which is typically long and outside your control, so plan for a tail of hours rather than minutes. During that tail both zones will be answering, which is exactly why both need to be correct.
What delegating to us provisions
Point the delegation here and the zone arrives populated: web records, mail routing and the entries certificate issuance relies on, so HTTPS validates without a manual step. Free SSL renews itself ahead of expiry on every plan.
If a site is coming from another host, our engineers do the migration free of charge and usually within 24 hours, with the old site continuing to serve traffic until the new one is verified. That removes the temptation to switch delegation before the destination is actually ready.
A reference that assumes you will check
Each entry names the query, the field or the panel screen that proves the claim, because a definition you cannot verify is just a nicer-sounding rumour.
Site migration is handled by our engineers at no charge and normally completes within 24 hours, with your existing site serving visitors the entire time.
- 100+ entries, each with a verifiable check
- Parent and in-zone NS sets explained separately
- Cutover order written down in the right sequence
- Maintained by the engineers on the platform
Why HostingFast
Standard on every plan
Latency you can profile
Authoritative response time is a measurement, and this entry gives you the way to take it.
Two NS sets, disentangled
Parent zone versus in-zone records, and the intermittent faults a mismatch produces.
A cutover order that works
Build, verify, lower TTLs, then delegate — in that sequence, for a specific reason.
Anycast versus unicast
What the difference looks like in numbers rather than in a vendor's diagram.
The classic dead end
Editing a zone nothing delegates to, named early so you never lose an afternoon to it.
Continues into its neighbours
DNS, DNS Propagation and A Record follow directly.
Quick Start
From order to online
- 1
Read the parent delegation
Find out which nameservers the registry publishes for your domain. That set, and only that set, is what resolvers will follow.
- 2
Time each server individually
Query every nameserver by name and record the query time. Repeat from a second region so you can see the spread.
- 3
Compare parent against in-zone
Check the NS records inside your own zone against the parent set. A mismatch is a fault even when everything appears to work.
- 4
Sequence the cutover properly
Build and verify the destination zone before you touch the delegation, and lower TTLs a full old-TTL cycle in advance.
Built In
Loaded onto every plan
- Zone populated automatically when you delegate to us
- Certificate records provisioned so HTTPS validates immediately
- Free SSL on every plan, renewed before expiry
- Full record editing in the panel after provisioning
- Free engineer-run migration of an existing site
- Renewal price identical to your signup price
- 99.9% uptime target, monitored around the clock
- Support answered by humans at any hour
Frequently Asked
What people ask us most often
I edited my DNS records and nothing changed. What did I miss?
Almost certainly the delegation. The edits went into a zone no resolver queries because the parent points somewhere else. Read the NS records the registry publishes for your domain, then go and make the change at whichever provider is named there. This is the single most common DNS dead end and it costs people whole afternoons.
How do I tell whether my nameservers are actually fast?
Query each one directly and record the query time, then repeat from a machine in another region. An anycast set returns similar figures everywhere; a unicast set is quick near its own rack and slow at distance. The spread across regions is the number that tells you whether to move.
What are private nameservers for, technically?
They are nameservers published on your own domain, built with glue records at the registrar so the delegation can resolve them. Functionally they answer exactly like any other set — the difference is cosmetic, which is why they matter to resellers presenting a brand and to nobody else.
Will my renewal cost more than my first term?
No. The rate you order at is the rate you renew at, every year. There is no introductory teaser pricing here, so there is no year-two step change hiding in a future invoice.
Keep reading
A Record
The record that names the actual machine, and how to test it before you commit.
Domain Registrar
Who publishes the delegation, and the limits attached to it.
How to Test Your Website Speed
Getting a real speed figure instead of a feeling, with the tools named.
AI Website Builder
Describe the site you need and the AI drafts it on real hosting.
Charity Hosting
Discounted hosting for charities and nonprofits, with nothing essential stripped out.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Delegate somewhere you can measure.
Every plan carries the things other hosts bill as extras, plus support that answers when you need it.
View AI Website Builder plans