Engineering Glossary · DNS
DNS Is Measurable Latency in Front of Your Server
Your TTFB looks fine from the server side and terrible in the field, and nobody has yet measured the part that happens before the request arrives.
The short answer
DNS is the distributed lookup system that turns a hostname into an address, and from a performance point of view it is a measurable segment that runs before your server is contacted at all. Every uncached visit pays it, and you can time it with a single curl flag.
The query walks a chain — root, then the servers for the extension, then your domain's authoritative nameservers — and every step is cached along the way according to its TTL. The part you control is the last hop and the TTLs you publish; the rest is somebody else's cache behaviour, which is exactly why you should measure rather than guess.
By the HostingFast team · Reviewed 12 August 2026
100+
Terms defined properly
2 min
Read time, end to end
Plain
English, no hand-waving
24/7
Engineers on shift
Your zone holds the records that answer those queries: A and AAAA for where the site lives, CNAME for aliases, MX for mail, TXT for verification and policy. Reading a zone fluently turns most site-down reports into a two-minute diagnosis rather than an afternoon.
Resolvers keep each answer until its TTL expires, and that caching is the entirety of what people call propagation. Nothing travels anywhere; old answers simply persist until their timers run out and a fresh query goes upstream.
Time the lookup before you theorise
One command gives you the split: request your URL with curl and print time_namelookup, time_connect, time_appconnect and time_starttransfer. Subtracting each from the next tells you how much of the wait is DNS, how much is TCP, how much is TLS and how much is your application.
Run it from a machine with a cold cache and again immediately afterwards. The gap between the two is the real cost of an uncached resolve, and it is the only version of the number that reflects a first-time visitor.
Reading a trace, and what each hop tells you
A traced query shows the delegation chain in order. If it stops at the parent zone, your delegation is wrong. If it reaches your nameservers and they answer slowly, the problem is your authoritative provider. If it reaches them and returns the wrong data, the problem is your zone.
Query each authoritative nameserver directly and compare the reported query times. A set that answers from a single region will be consistently slower for distant visitors than an anycast set, and that difference is visible in the numbers rather than a matter of opinion.
The levers you actually hold
There are three: which nameservers you delegate to, what TTLs you publish, and how many distinct hostnames a page forces the browser to resolve. Consolidating third-party assets onto fewer hosts removes whole lookups from the critical path, and a preconnect hint for a host you genuinely need starts the resolve early rather than saving it.
Everything else marketed as a DNS speed-up is somebody else's cache. Before adding a resolver, a proxy or a plugin, measure the segment; if DNS is ten milliseconds of a two-second load, the work belongs somewhere else entirely.
How DNS behaves on this platform
Delegate to us and the zone is created with the records your account needs, including the ones certificate issuance depends on, so HTTPS is valid from the first request rather than after a manual step. Zone editing is available in the panel for anything you want to change afterwards.
If the site is currently hosted elsewhere, our engineers migrate it free — files, databases and mailboxes — usually inside 24 hours, and the existing site keeps serving traffic until you are satisfied the new one is correct.
Definitions that end in a number
We got tired of glossary entries that explain a concept and leave you with no way to check anything, so each of these carries a command, a field name or a panel screen.
NVMe storage and server-level LiteSpeed caching are on every tier, from the smallest plan upwards — the baseline, not an upsell.
- 100+ entries with the check included
- Traces, timings and field names, not metaphors
- Wired into TTL, Nameserver and A Record
- Written by our own engineers
Why HostingFast
Standard on every plan
Measured, not assumed
The DNS segment gets a number here before anybody is asked to change anything.
DNS, hop by hop
What a traced query tells you at each stage, and which fault each stage implies.
Three real levers
Delegation, TTLs and hostname count — the parts you control, separated from the parts you do not.
Anti-cargo-cult
Where a popular DNS tweak makes no measurable difference to a visitor, this page says so.
Failure modes mapped
Wrong delegation, slow authoritative servers and wrong records produce different symptoms, listed separately.
Continues into its neighbours
Nameserver, TTL and DNS Propagation carry the thread on.
Quick Start
From order to online
- 1
Split the waterfall with one command
Print the four curl timing values for your own URL and work out how many milliseconds are DNS. Everything else on this page depends on knowing that figure.
- 2
Trace the delegation
Run a traced query and confirm it reaches your nameservers. A trace that stops short is a delegation problem, not a records problem.
- 3
Time each authoritative server
Query your nameservers individually and compare query times. Slow or uneven answers point straight at your DNS provider.
- 4
Count the hostnames on a page
Open the network panel and list the distinct hosts a page resolves. Every extra one is a lookup, a connection and a handshake you are paying for.
Built In
Loaded onto every plan
- Zone provisioned automatically when a domain points here
- Full DNS record editing available in the panel
- Free SSL issued and renewed without a manual step
- LiteSpeed caching at server level on every plan
- NVMe SSD storage across the whole range
- Free migration of an existing site by our engineers
- In-place plan upgrades with no migration
- Engineers on support at any hour
Frequently Asked
What people ask us most often
What is a reasonable DNS lookup time to aim for?
Cached, it should be effectively zero — the resolver answers from memory. Uncached is the figure worth watching, and it is dominated by how far the visitor's resolver has to travel to reach an authoritative answer. Measure it with curl from a few locations rather than adopting a number from an article; your audience's resolvers are the only ones that count.
Can DNS on its own take a whole site offline?
The protocol is built to prevent it, with multiple nameservers, global caching and TTLs that keep answers alive after a failure. The fragility is human: a mistyped record, a delegation pointing at a zone nobody maintains, or a name in a registry hold state. Almost every incident filed as a DNS outage is one of those three.
Does adding a fast public resolver speed up my visitors?
It speeds up you, on your machine, and nobody else. Visitors use whatever resolver their network hands them, and you cannot change it. The parts of the path you can improve are your authoritative servers, your TTLs and the number of hostnames your pages force a browser to resolve.
Can I transfer in a domain I already own?
Yes, and it is routine. Unlock the name at your current registrar, request the auth code, and start the transfer from your client area. Remaining registration time carries over, and DNS keeps resolving throughout provided the zone is in place before you begin.
Keep reading
DNS Propagation
Why a change is not instant, and how to time the tail rather than wait it out.
Nameserver
The machines that answer for you, and how to measure how quickly they do it.
How to Register a Domain Name
Registering a name and pointing it somewhere useful, in the right order.
Agency Hosting
Client accounts, staging and care-plan infrastructure built for agencies.
Reseller Hosting
White-label WHM hosting — your brand in front, monthly billing behind it.
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.
Measure the whole path, not just the server.
Free SSL, free migration, renewals at the original rate and engineers who answer. That is the entire pitch.
View Agency Hosting plans