Connecting a domain to hosting means directing your domain’s DNS settings to the server or website platform where your site lives. This guide explains the domain and hosting difference, shows when to use nameservers, A records, or CNAME records, and gives you a practical checklist for SSL, email, propagation, troubleshooting, and ongoing monitoring.
Overview
A domain is the address people type into a browser, such as example.com. Hosting is the service that stores and delivers your website’s files, database, images, and other resources. Registering a domain does not automatically connect it to a website. DNS, or the Domain Name System, provides the connection between the domain name and the hosting service.
The exact labels vary between registrars and hosting companies, but the process usually follows this sequence:
- Find the DNS instructions provided by your hosting company or website builder.
- Choose whether to change nameservers or edit individual DNS records.
- Add or update the required records at the DNS provider.
- Confirm the domain in your hosting account or website builder.
- Activate HTTPS and test the domain, subdomain, and email services.
Before making changes, record the existing DNS entries. This is especially important if the domain already handles email, verification services, or other subdomains. A useful related resource is this guide to domain registrars and their DNS tools.
What to track
1. The hosting destination
Start with the setup instructions from your hosting provider. They may give you two nameservers, an IPv4 address for an A record, an IPv6 address for an AAAA record, or a target hostname for a CNAME record. Do not substitute an address from a generic tutorial for the value supplied by your provider.
If you use a website builder, the platform may require you to verify ownership with a TXT record before it allows the domain to connect. Keep the verification value exactly as supplied, including punctuation where applicable.
2. Nameservers versus individual DNS records
Changing nameservers moves DNS management to another provider. You enter the new nameservers at the registrar, and the new DNS provider becomes responsible for the domain’s records. This can be convenient when your host manages DNS and gives you a complete setup.
Editing individual records keeps DNS management with the current provider. You might use this approach when the domain already has email, several subdomains, or services that should remain under the registrar’s DNS control. In that case, you typically update the root domain’s A record and add or update a www CNAME record.
Use one clear DNS strategy. Changing nameservers and separately editing records at the old provider can create confusion because only the active DNS provider controls what visitors ultimately receive.
3. The main record types
- A record: Points a domain or subdomain to an IPv4 address. It is commonly used for the root domain when the host provides an IP address.
- AAAA record: Points a domain or subdomain to an IPv6 address when the provider supplies one.
- CNAME record: Points a hostname, such as www.example.com, to another hostname. It is often used for a www subdomain or a hosted platform connection.
- TXT record: Stores text used for domain verification and other services. Email authentication may also use TXT records.
- MX record: Tells mail servers where to deliver email for the domain. These records should not be changed casually during a website connection.
DNS dashboards often use an @ symbol to represent the root domain. A blank host field can mean the same thing. Follow the interface’s instructions rather than entering the full domain into every field.
4. Existing email and subdomains
Website DNS and email DNS can coexist, but changing nameservers may replace the active DNS zone if its records are not recreated. Before switching providers, list the MX, TXT, CNAME, and other records currently in use. Pay particular attention to email delivery and authentication records, as well as subdomains such as blog, shop, mail, or app.
If you only need to point the website, updating the relevant A or CNAME records may reduce the chance of disturbing unrelated services. When unsure, pause and check the host’s documentation before deleting any record.
5. SSL and the final URLs
After DNS points to the correct destination, activate the host’s SSL certificate or HTTPS setting. Test both the root domain and the www version, along with their HTTP versions if the platform supports automatic redirection. The preferred version should load consistently, while the alternate version should redirect to it.
SSL issuance can depend on successful DNS resolution and domain verification, so it may not be available immediately after a record change. Do not treat an HTTPS warning as proof that the DNS record is wrong until you have checked the host’s certificate status and the domain’s current destination.
Cadence and checkpoints
A domain connection is usually a one-time setup, but it benefits from scheduled checks. Add the following checkpoints to your website launch and maintenance routine.
During initial setup
- Save the current DNS zone or take screenshots before editing.
- Confirm whether the host expects nameservers, an A record, a CNAME, or a verification record.
- Check that the domain is not still assigned to an old website or parked page.
- Confirm the root domain and www hostname separately.
- Activate HTTPS after the host recognizes the domain.
- Test the homepage, key pages, forms, images, redirects, and contact email.
After making a DNS change
Check the domain from more than one network or device, but avoid repeatedly changing records because one connection still shows the old result. DNS responses can be cached for different periods according to the records’ time-to-live settings, and updates may appear at different times. Keep a note of the change, the time it was made, and the expected destination.
Monthly or quarterly review
Review the domain’s nameserver delegation, key A and CNAME records, SSL status, renewal date, and email-related records. Remove obsolete records only when you understand what service created them. This recurring review is also a good time to confirm that your hosting account still points to the intended site and that no old staging or temporary destination remains publicly accessible.
For a wider operational review, use the ongoing website launch and maintenance checklist alongside your DNS notes.
How to interpret changes
When a domain does not work immediately, identify which layer has failed instead of changing several settings at once.
The domain shows the old website
Check the active nameservers first. If they point to a different DNS provider than the one you edited, your changes are being made in the wrong dashboard. If the nameservers are correct, compare the live A or CNAME response with the value supplied by the host. Local browser, operating-system, router, or ISP caching may also temporarily show an earlier destination.
The domain shows a parking page or server error
This often indicates that DNS reaches a server, but the hosting account has not been configured for that domain, the record points to the wrong destination, or the site has not been assigned to the domain. Check the domain mapping inside the hosting panel as well as the DNS record itself.
Only www or only the root domain works
Treat these as separate hostnames. Confirm that the root domain has the required A or equivalent record and that www has the required CNAME or A record. Then check whether the host has selected a preferred domain and configured the redirect.
Email stops working after the change
Review the MX records and any associated email authentication records. If nameservers were changed, the new DNS provider may need the previous email records added manually. Avoid guessing at MX values; use the instructions from your email provider.
HTTPS fails or shows a certificate warning
Confirm that the domain is connected in the hosting panel, DNS reaches the correct service, and the SSL certificate covers the exact hostname being tested. Check both the root and www versions. If the site recently moved, allow the platform time to complete verification before repeatedly requesting certificates.
For broader hosting decisions, compare the trade-offs in shared, VPS, and cloud hosting or review the considerations in managed WordPress hosting versus shared hosting.
When to revisit
Revisit this DNS setup whenever you change hosting, move a WordPress installation, launch a subdomain, switch email providers, add a landing-page platform, or renew a service that manages DNS. It is also worth checking after a registrar transfer, a major site redesign, a security incident, or an unexplained change in website or email availability.
At minimum, schedule a monthly or quarterly review. Confirm that the nameservers still lead to the intended provider, the primary records still point to the correct site, HTTPS works on every public hostname, and email records remain intact. Keep a simple change log with the date, record changed, previous value, new value, and reason.
Use this final sequence whenever you need to connect a domain to hosting:
- Identify the hosting provider’s exact DNS requirements.
- Back up or document the current DNS records.
- Choose nameservers or individual records based on who should manage DNS.
- Preserve email and important subdomain records.
- Connect the domain inside the hosting account.
- Wait for DNS changes to become visible, then verify both root and www hostnames.
- Activate SSL, test redirects and forms, and record the final configuration.
This process keeps domain and hosting changes controlled, makes future troubleshooting faster, and reduces the risk of taking an otherwise working website or email service offline.