A website address looks simple in a browser, but several services work behind it. Knowing the difference between a domain registration, DNS and hosting makes it much easier to launch a site, connect email or move providers without an avoidable interruption.
Your domain is the address, not the website
A domain is a renewable registration that lets you use a name. Hosting is where your website runs. DNS publishes the records that help browsers, mail servers and other systems find the services associated with that name.
You can keep these services with one provider or use separate providers. Either arrangement can work. What matters is knowing which account controls each part and keeping access to it.
Choose a name you can keep using
When planning domain registration, think beyond whether a name is available today. Say it aloud, check its spelling and consider how it will look in an email address. Avoid a name so narrowly tied to one product that it becomes awkward as the business grows.
Check registration and renewal terms before committing. Record who the registrant is, enable multi-factor authentication where available and use a recovery email address that remains accessible if the domain stops working.
Understand the records you are editing
You do not need to memorise every DNS record type to manage a website, but these are worth recognising:
- A and AAAA records connect a name to IPv4 and IPv6 addresses.
- CNAME records make one name an alias of another, subject to DNS restrictions.
- MX records identify the servers that receive email for the domain.
- TXT records are often used for verification and email authentication.
Changing one website record should not require deleting unrelated mail or verification records. Save the current configuration before making changes.
Treat a nameserver change with care
Nameservers determine which DNS service is authoritative for the domain. Switching them does not automatically copy the old records into the new service. Build and check the destination zone first, including records for services you may not use every day.
DNS answers are cached. Lowering a TTL can help with a planned change, but existing cached answers retain their earlier expiry. Keep the old destination available during the transition and check actual records instead of relying only on a generic propagation estimate.
Keep a one-page domain record
Document the registrar, DNS provider, hosting account, renewal date and recovery contact. Keep sensitive credentials in a password manager rather than the document itself. That small inventory can save hours when a website or mailbox needs urgent attention.
For a deeper explanation of the naming system, see MDN’s domain-name guide.