Connecting a domain to web hosting means directing visitors to the server that stores your website. This guide explains how to point a domain to hosting with nameservers or DNS records, what to monitor after the change, how to protect email and HTTPS, and when to revisit the setup.
Overview
A domain name is the address people type into a browser. Web hosting is the server space where your website files, database, and related services live. DNS, or the Domain Name System, connects the two by translating a domain name into the destination used by browsers.
When you buy domain and hosting from the same provider, the connection may be prepared automatically. If you registered the domain and hosting separately, you usually need to configure the domain at the registrar and add the domain inside the hosting control panel first. Dashboard labels vary, but the relevant options are often called Nameservers, DNS Management, Zone Editor, Add Domain, or Domains.
There are two common ways to connect a domain to hosting:
- Change nameservers: You delegate DNS management to the hosting provider. This is often the simpler option for a new website.
- Edit DNS records: You keep DNS management at the registrar and point only selected records, such as the website and a subdomain, to the hosting service.
Neither method is automatically better. Nameservers are convenient when the host should manage the complete DNS zone. Individual records provide more control when your email, verification services, or other subdomains remain with separate providers.
What to track
1. The hosting account and domain status
Before changing DNS, confirm that the domain has been added to the hosting account. Some hosts call this an add-on domain, an alias, an additional site, or a primary domain. Record the website’s assigned destination, such as an IPv4 address, IPv6 address, or provider-specific target. If the host supplies nameservers, copy them exactly and keep a private note of the previous settings.
Also check whether the domain is active at the registrar. A domain that is expired, locked during a transfer, or missing required verification may not respond normally even when the hosting configuration is correct.
2. Nameservers and DNS records
If you change nameservers, replace the existing nameserver entries with the complete set supplied by the host. Do not guess these values or add unrelated entries. The nameserver change moves control of the domain’s DNS zone, so existing records at the registrar may no longer be used.
If you keep the registrar’s DNS, review the records required by the host. A typical setup may include:
- A record: Points a name such as
example.comto an IPv4 address. - AAAA record: Points a name to an IPv6 address when the host provides one.
- CNAME record: Points a subdomain, such as
www.example.com, to another hostname. - MX records: Direct email delivery. These should not be changed casually.
- TXT records: Support verification and email-security configurations, among other uses.
Use the exact host-provided values, including the final dot if the dashboard requires it. For the root domain, a DNS editor may display the host field as @ or leave it blank. The www version is commonly configured separately, so test both the root domain and www.
3. TTL, propagation, and HTTPS
TTL, or time to live, tells DNS resolvers how long they may cache a record. A lower TTL can make planned changes easier to adjust, while a higher TTL can reduce how frequently resolvers ask for updated information. The practical point is to note the TTL before a change and avoid assuming that every visitor will see the new destination immediately.
DNS propagation is the period during which different networks may still use cached information. Check the domain from more than one network, such as a mobile connection and a home or office connection, but do not repeatedly edit records simply because one test is still showing the old result.
After DNS points to the correct server, complete SSL certificate setup in the hosting dashboard. Enable HTTPS only after the domain resolves to the intended account, then test both http:// and https://. A secure redirect should send visitors to the HTTPS version without creating a loop.
4. Email and other services
Website DNS and email DNS are related but separate. Changing nameservers can remove or replace MX, TXT, and other records that email depends on. Before switching nameservers, copy the existing DNS records or confirm that the new DNS provider has equivalent entries. If the website works but mail stops arriving, inspect MX records first rather than changing the website’s A record again.
Cadence and checkpoints
Use this workflow whenever you launch, transfer, or reconfigure a domain:
- Before the change: Record the current nameservers, A, AAAA, CNAME, MX, and important TXT records. Save screenshots or export the zone if the dashboard supports it.
- During the change: Add the domain to hosting, choose nameservers or individual records, and confirm that there are no duplicate or conflicting entries.
- After saving: Check the registrar’s status and allow time for cached DNS data to expire. Test the root domain,
www, any important subdomains, and email. - After the site resolves: Install or activate the SSL certificate, test HTTPS, and check that internal links, images, forms, and redirects use the preferred version of the domain.
- Within the first week: Review hosting logs, uptime notifications, contact forms, and search-console or analytics verification if those tools are part of the site.
For recurring monitoring, review DNS and SSL at least quarterly and whenever a registrar, host, CDN, email provider, or website platform changes. Keep a simple change log with the date, record changed, old value, new value, reason, and person who made the change. This makes future troubleshooting much faster.
For control-panel guidance, compare the interfaces described in Free Hosting Control Panels Compared. If you are using free hosting, also confirm that its domain, DNS, SSL, storage, and bandwidth limits support your intended launch.
How to interpret changes
When a site does not load after a DNS update, first identify whether the problem is DNS, hosting, the website application, or HTTPS. The following checklist separates common symptoms:
| Symptom | Likely area | What to check |
|---|---|---|
| Registrar or host parking page | Domain mapping or DNS | Confirm the domain is added to the correct hosting account and that the A record or nameservers match the host instructions. |
| Old website still appears | DNS cache or wrong destination | Compare results from different networks, check the current A or CNAME value, and avoid making repeated changes before cached data expires. |
| “Too many redirects” | HTTPS or application settings | Check whether both the host and the content management system force HTTPS, or whether a proxy is using an incompatible SSL mode. |
| HTTPS warning or missing certificate | SSL setup | Confirm that the domain resolves to the intended server, the certificate includes the root and required subdomains, and mixed-content links are updated. |
| Website works but email fails | MX or TXT records | Restore the email provider’s MX and verification records. Do not replace them with the web host’s records unless the email service is moving too. |
| Root domain works but www does not | CNAME or redirect configuration | Check the separate www record and confirm the hosting account accepts both hostnames. |
A DNS checker can help compare records from multiple locations, but its results are only one diagnostic signal. Also test the site directly in a private browser window, check the hosting account’s domain status, and review server or application logs where available.
When to revisit
Revisit this guide whenever you register a new domain, move a site to different hosting, change nameservers, add a CDN, migrate email, renew or replace SSL, or create important subdomains. It is also worth reviewing after a domain transfer because transfer locks, DNS delegation, and registrar settings can differ between providers.
Use a quarterly checkpoint for established websites. Confirm that the registrar account has current contact and recovery details, the domain is not approaching expiration, nameservers are still intentional, SSL is active, and email records remain intact. Review the change log and remove obsolete records only when you know which service no longer uses them.
For your next launch, complete this short checklist:
- Add the domain to the correct hosting account.
- Choose nameservers or record-based DNS deliberately.
- Save existing email and verification records before changing delegation.
- Confirm A, AAAA, CNAME, MX, and TXT values as applicable.
- Test the root domain,
www, email, and important subdomains. - Activate SSL only after DNS reaches the intended server.
- Record the final configuration and schedule the next quarterly review.
This repeatable process reduces avoidable downtime and gives you a reliable way to connect a domain to hosting again when the next website launch or migration arrives.
