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

Overview

A domain name and a hosting account are separate services. The domain is the human-readable address, while web hosting provides the server where the site files, database, and application run. DNS connects the two by telling browsers which server should answer for the domain.

Before making a change, collect four details from your hosting provider:

• The hosting account or website destination.
• The server IP address for an A record, if applicable.
• The provider’s nameservers, if you plan to delegate DNS management.
• Any required record for the www hostname, such as a CNAME target.

Also make an inventory of existing DNS records. Pay particular attention to MX records for email, TXT records used for verification or email security, and CNAME records supporting subdomains or third-party services. A connection method that works for the website can still cause problems if it replaces records that other services need.

If you are moving an existing site rather than launching a new one, prepare the files, database, application settings, and backups before changing DNS. The Website Migration Checklist provides a broader workflow for reducing disruption during a hosting move.

Checklist by scenario

Scenario 1: Use the hosting provider’s nameservers

Changing nameservers delegates DNS management for the domain to the hosting provider. This can be convenient when the host manages the zone, SSL setup, redirects, and related configuration.

1. Sign in to the domain registrar, not only the hosting dashboard.
2. Locate the nameserver settings for the domain.
3. Record the current nameservers and DNS records before replacing anything.
4. Enter the exact nameservers supplied by the host.
5. Confirm that the hosting account has the correct domain attached.
6. Recreate or verify required MX, TXT, CNAME, and other records in the new DNS zone.

Nameserver changes affect the whole DNS zone. Do not use this method casually if the domain supports business email, verification records, APIs, or other production services and you have not documented those records first.

Scenario 2: Keep current DNS and change the A record

An A record points a hostname to an IPv4 address. This approach lets you keep DNS management at the registrar or current DNS provider while directing only the website to the new host.

1. Find the record whose name is the root domain, often shown as @.
2. Change its value to the hosting server’s IPv4 address.
3. Review the www record separately; it may be a CNAME or an additional A record.
4. Leave MX records unchanged unless your email provider has instructed you otherwise.
5. Save the changes and note the time for later troubleshooting.

This is often the safer option when existing email and subdomains must remain with their current providers. If the host provides an IPv6 address, it may also request an AAAA record. Add it only when the address and server configuration are confirmed.

Scenario 3: Launch a new site with a website builder or managed CMS

Website builders and managed WordPress hosting may provide a guided connection process. Follow the provider’s exact record instructions rather than guessing. Some platforms use a verification TXT record first, then ask you to update an A or CNAME record. Complete domain verification, attach the domain inside the site dashboard, and set the preferred version—such as the root domain or www—before publishing.

For broader hosting selection considerations, see How to Choose Cloud Web Hosting.

What to double-check

Root domain and www

Test both example.com and www.example.com. They are separate DNS names and may not use the same record. Your hosting control panel should know which version is canonical and redirect the other consistently.

DNS propagation and caching

DNS changes do not appear everywhere at the same moment. Recursive resolvers may continue using cached answers until the record’s TTL expires. Check the domain from more than one network or DNS lookup tool, but do not repeatedly edit records simply because one location still shows the previous answer. The guide to DNS propagation covers what to check during this waiting period.

SSL and HTTPS

DNS pointing alone does not guarantee HTTPS. After the domain resolves to the correct host, enable the provider’s SSL certificate or request the available free SSL option. Confirm that the certificate covers every hostname visitors will use, including the chosen www or root version. Test an HTTPS page, confirm that the certificate is valid, and configure an HTTP-to-HTTPS redirect only after the site loads correctly.

Email records

Website DNS and email DNS are related but separate. MX records identify mail servers, while TXT records can support sender authentication and domain verification. If email must continue working, compare the existing records with the new provider’s instructions before changing nameservers.

Common mistakes

• Changing nameservers without copying records: The website may work while email or verification services fail.
• Editing the wrong DNS zone: Make sure you are changing the authoritative provider, not an unused registrar panel.
• Forgetting the www hostname: The root domain can resolve while the www version shows an error.
• Using a URL in an A record: A records require an IP address, not https:// or a path.
• Expecting instant propagation: Cached answers can make a correct change appear ineffective temporarily.
• Activating SSL too early: Issue or enable the certificate after the host can verify control of the domain.
• Testing only one network: Check mobile data, another connection, or independent DNS lookup services when results are unclear.

When to revisit

Revisit this checklist before a planned hosting move, a seasonal campaign, a domain renewal, or a major website rebuild. It is also useful when changing email providers, adding a CDN, launching a subdomain, or replacing a website builder. Review DNS records whenever a workflow or hosting tool changes, because the required record types and verification steps may differ between providers.

For routine maintenance, keep a dated copy of the current DNS zone, record who manages it, and document the purpose of unusual records. After every change, verify the root domain, www, HTTPS, email delivery, and any important subdomains. If the website remains unavailable after propagation should have completed, compare the DNS answer with the hosting account’s assigned IP, check that the domain is attached to the correct site, and contact the host with the exact hostname and error message.

Once the connection is stable, add uptime checks and renew your domain and SSL monitoring process to the site maintenance calendar. This turns a one-time setup into a repeatable operating checklist.