Understanding DNS helps you connect a domain to a website, keep email working and diagnose failures after a purchase or migration. It also prevents a common investing mistake: treating an address that does not load as an available domain.
The Domain Name System publishes records associated with names. Registration gives you control of a domain through a registrar; DNS configuration tells internet services how to use it. Website hosting and email hosting are separate services that those records can point towards.
Follow the lookup, then find the right control panel
As Cloudflare’s DNS explanation describes, a recursive resolver answers a client’s request, using cached information where possible. Otherwise it follows the DNS hierarchy through root and top-level-domain services to the authoritative nameservers responsible for the name.
The registrar normally provides controls for the domain’s nameserver delegation. The authoritative DNS provider manages the zone containing its records. They may be the same company, but changing a record in an inactive DNS account will not change the public answer.
Before editing anything, record the current nameservers and identify the account that controls the active zone. If you are acquiring a name, establish which services are included in the sale. A registrar transfer does not automatically deliver the seller’s hosting account or email system.
Recognise the records you will encounter
DNS record documentation distinguishes several common types:
- A and AAAA records identify IPv4 and IPv6 addresses.
- CNAME records make one name an alias of another name.
- MX records identify mail servers for receiving email.
- TXT records carry text used for purposes such as verification and email authentication.
- NS records identify authoritative nameservers.
These records do not reveal a domain’s full ownership history, prove its traffic or disclose a Google manual action. A working A record is not evidence of a valuable website. Our extension guide covers naming decisions separately from this technical configuration.
Plan changes around caching and dependencies
Time to Live, or TTL, tells caches how long a record can be retained. It is a caching setting, not a grade for domain quality. Lowering it does not make a name more authoritative, and an answer already cached under the previous TTL may remain in use until that cache expires.
For a hypothetical hosting move, first save the zone and prepare the new server. Change the required website records, then test the main address and its www version. Check email separately. Replacing all nameservers without recreating MX and authentication records can interrupt services that were unrelated to the website move.
Our hosting provider guide helps establish responsibilities for DNS, certificates and backups. Keep a written rollback plan and avoid making several unrelated changes together.
Check registration independently
A DNS failure can reflect missing records, an incorrect delegation or a service problem. It is not a registration-availability result. RDAP provides registration data for supported domains; a registrar’s current registration check addresses whether a name can actually be ordered.
Follow our registration lookup guide when assessing an acquisition. Keep registration status, DNS answers and website behaviour in separate notes: they answer different questions.