How to Connect a Domain to Web Hosting: DNS Records, SSL, and Troubleshooting

Overview

Your domain registrar manages the registration of your domain name, while your hosting provider stores and serves your website files. DNS, or the Domain Name System, connects the two by telling browsers where to find the site associated with your domain.

Before changing anything, collect four pieces of information:

• Your registrar login and hosting account login.
• The exact nameservers or DNS record values supplied by your hosting provider.
• The preferred website address, such as example.com or www.example.com.
• Whether the domain also handles email, verification services, subdomains, or other applications.

There are two common ways to connect a domain to hosting. You can change the domain’s nameservers to those provided by the host, allowing the host to manage the domain’s DNS zone. Or you can keep DNS at the registrar or another DNS provider and add individual records, usually an A record for the root domain and a CNAME record for www. The correct choice depends on the instructions from your hosting provider and how much control you want over DNS.

If you are still choosing a domain, use the domain name search and availability checklist first. If you are moving the domain between registrars, review the domain transfer checklist before changing DNS.

Checklist by scenario

Scenario 1: Your hosting provider gives you nameservers

1. Sign in to the registrar where the domain is registered.
2. Open the domain’s DNS or nameserver settings.
3. Choose the option to use custom nameservers rather than the registrar’s default nameservers.
4. Enter every nameserver exactly as supplied by the hosting provider. Do not add extra punctuation, spaces, or unrelated records.
5. Save the change and note the date and time.
6. Check the hosting dashboard to confirm that the domain has been added to the correct website or hosting account.

Changing nameservers transfers DNS management to the new provider. This can be convenient, but existing DNS records may not automatically be reproduced in the new DNS zone. Before switching, copy any records used for email, domain verification, subdomains, analytics, or third-party services. If the domain is used for business email, preserving its mail records is especially important.

Scenario 2: You are keeping DNS at the registrar

1. Open the domain’s DNS record manager.
2. Add an A record for the root domain, often displayed as @, using the IP address provided by the hosting provider.
3. Add a CNAME record for www if the host instructs you to do so. Its target may be a host-provided address rather than the root domain.
4. Remove conflicting A, AAAA, or CNAME records only after confirming that they are not needed by another service.
5. Save the records and verify that the host recognizes the domain.

Do not guess the IP address or CNAME target. Hosting platforms can use different connection methods, and a value that looks plausible may still point to the wrong server. Use the exact values shown in the hosting account documentation.

Scenario 3: You are connecting a subdomain

For a subdomain such as blog.example.com or store.example.com, create a record for the subdomain label, usually blog or store, rather than replacing the root domain record. The destination may be an IP address, a CNAME target, or a platform-specific value. Confirm whether the hosting provider expects the full hostname or only the label.

Scenario 4: You are launching a new site with email already active

Separate website records from email records. Website traffic commonly uses A, AAAA, or CNAME records. Email delivery commonly depends on MX records, while SPF, DKIM, and DMARC records may support sender authorization and email security. Keep those records unless your email provider specifically instructs you to change them. A website DNS change should not require moving email to the web host.

What to double-check

Nameservers and record location

First identify which provider is authoritative for DNS. Editing records at the registrar will not change the live result if the domain uses nameservers from a separate DNS provider. You can confirm the active nameservers with a reputable DNS lookup tool or through the domain account. Make changes in the system that actually publishes the domain’s DNS zone.

Root domain and www behavior

Decide whether visitors should use the root domain, the www version, or both. Your hosting platform should define one as the primary address and redirect the other. Add both versions to the hosting account when the platform recommends it, then configure a permanent redirect or canonical preference in the hosting or CMS settings. Avoid creating a redirect loop by pointing each version to the other.

SSL certificate setup

After DNS points to the correct hosting environment, activate SSL through the hosting provider or your website platform. Confirm that the certificate covers every address visitors may use, including the preferred hostname and any required subdomain. Test the site with https:// in a private browser window. If the site still loads insecurely, update the CMS site URL, replace hard-coded HTTP links where appropriate, and check for mixed content such as images, scripts, or stylesheets loaded over HTTP.

Propagation and verification

DNS changes are cached by resolvers, browsers, operating systems, and networks. Results may therefore differ temporarily between locations or devices. Check the root domain and www separately, and test from more than one network if the result is unclear. A propagation checker can show that different resolvers are returning different answers, but it cannot confirm that the hosting account, website files, or SSL configuration are correct.

Website and email tests

• Open the root domain and the www version.
• Test both HTTP and HTTPS, then confirm the preferred redirect.
• Open several pages, not only the homepage.
• Check that images, forms, scripts, and downloadable files work.
• Send a test email in both directions if the domain uses custom email.
• Confirm that verification records for services such as search tools or newsletters remain present.

Common mistakes

• Changing nameservers without copying email records: The website may work while email stops arriving. Record existing MX, SPF, DKIM, and DMARC values before moving DNS.
• Using the wrong record type: A records point to IP addresses. CNAME records point to hostnames. Do not place a hostname in an A record or an IP address in a CNAME field.
• Leaving conflicting records in place: Multiple A records or competing CNAME records can send visitors to different destinations or make the result unpredictable.
• Adding the full domain where only a host label is expected: Some DNS editors automatically append the domain. Entering the full name can create a duplicated hostname.
• Testing before adding the domain to the host: DNS can point correctly while the hosting account still serves a default page, an account error, or the wrong site.
• Assuming propagation is the only problem: If the issue persists after caches have refreshed, check the record values, domain status, website assignment, firewall settings, SSL configuration, and redirect rules.
• Deleting records you do not recognize: Unfamiliar records may support email, payment tools, analytics, or domain verification. Identify them before removal.

For platform-specific instructions, compare this general process with the provider’s guide for pointing a domain to Shopify, Squarespace, Webflow, or WordPress. The labels differ, but the underlying DNS decisions are similar.

When to revisit

Keep this checklist with your domain records and revisit it whenever you change hosts, redesign a site, add a subdomain, move email, activate a new third-party service, or transfer the domain. It is also useful before a seasonal launch or other high-traffic period, when there is more value in finding a DNS or SSL issue before visitors do.

Before making a change, export or copy the current DNS records and record the intended final setup. After the change, test the website, redirects, SSL, email, and important integrations. If the workflow or hosting control panel changes, use the provider’s current instructions for exact field names and values rather than relying on an old screenshot.

A practical final checklist is: confirm the authoritative nameservers; copy records before changing DNS; add the exact A or CNAME values; verify the domain in the hosting account; activate SSL; test both root and www addresses; preserve email records; and document what changed. If you need to estimate the wider launch budget, the domain and hosting cost calculator can help separate registration, hosting, SSL, email, and other setup costs.