Three services, three different jobs

Registering a domain gives you the right to use a name, such as example.com, for a registration period. You manage that registration through a registrar. The registrar is where you typically handle renewals, contact details, and the domain’s nameserver settings. Registration does not, by itself, put a website online or create an email inbox.

DNS hosting publishes the records that tell other systems where to find services associated with the domain. Web hosting stores or serves the website that visitors see. One company may provide all three services, but they remain distinct jobs. Keeping that distinction in mind makes settings easier to locate: nameserver changes usually start at the registrar, DNS record changes happen at the DNS host, and website files and application settings live at the web host.

The path from a domain name to a website

When someone enters a domain in a browser, a DNS resolver looks for the domain’s records. The domain’s nameserver settings direct that lookup toward its authoritative DNS host. There, an A record can provide an IPv4 address and an AAAA record can provide an IPv6 address. A name such as www.example.com might instead use a CNAME record pointing to another hostname. The exact records needed depend on the web host’s instructions.

Once the browser has a usable destination, it connects to the web service and requests a page. The server must be configured to recognize the requested domain; pointing DNS at an address alone may not make the right site appear. For an HTTPS connection, the site also needs a valid certificate for the name visitors use. DNS helps visitors find the destination, while the web host is responsible for serving the site at that destination.

Why the providers do not have to match

You can register a domain with one provider, use another for DNS, and host the website with a third. The connection between them is made through settings, not through a requirement to buy a package. At the registrar, you set the nameservers supplied by your DNS host. At the DNS host, you publish the records supplied by your web host. If the website moves, you may be able to change only its DNS records and leave the registration and nameservers alone.

A domain can support more than a website. MX records identify where mail for the domain should be delivered, while TXT records may carry email authentication settings. Other records might support subdomains or service verification. Replacing a DNS zone with only the records for a new website can therefore disrupt email or other services. Before changing DNS hosts, make an inventory of the records currently in use and confirm which ones the new provider requires.

What to check when changing a provider

First identify which service is changing. Moving a website usually calls for setting up the site at the new host, checking that it recognizes the domain and supports HTTPS, then updating the relevant DNS records. Moving DNS hosting calls for copying necessary records to the new DNS host before changing nameservers at the registrar. Moving the registration is a separate process; do not assume it also moves your DNS zone or website.

Allow for a transition period after DNS changes. Resolvers may continue using cached answers until their time-to-live values expire, and nameserver changes may take time to be reflected across the lookup path. During that period, different visitors may reach different destinations. If possible, keep the old service working while you verify the new one. Check the root domain, the www name, and any important subdomains, as well as mail delivery if email records were involved.

Keep ownership and access clear

A simple record of who controls each service can prevent confusion later. Note the registrar, the DNS host, the web host, renewal arrangements, and the people authorized to make changes. When a domain stops working, start by asking which part of the path is affected: Is the registration active? Do the nameservers lead to the expected DNS host? Do the DNS records point to the intended service? Is that service configured for the domain?

Protect the accounts that control these settings with strong, unique passwords and multi-factor authentication where available. Keep recovery information current, and avoid sharing credentials in support messages or public troubleshooting posts. Domain registration, DNS hosting, and web hosting work together, but each has its own controls. Knowing which control belongs where makes routine changes safer and problems easier to narrow down.

Back to category ↗