How to Connect a Domain to Web Hosting: A Complete DNS Setup Guide

Overview

Your domain and hosting account are separate services, even when you purchase them from the same company. The domain is the address people enter, while web hosting provides the server, files, database, and applications that deliver the site. DNS, or the Domain Name System, connects the two.

Before changing anything, collect these details from your hosting provider:

• The provider’s nameservers, if it asks you to use them.
• The hosting server’s IPv4 address, usually needed for an A record.
• An IPv6 address, if the host specifically provides one and supports it for your site.
• A destination hostname for a CNAME record, where applicable.
• Instructions for adding the domain inside the hosting control panel.
• The steps for enabling an SSL certificate after the domain resolves.

Keep a record of your current DNS settings before editing them. This is especially important if the domain already handles business email, verification services, subdomains, or other applications. If you are still selecting a plan, compare the needs of your site before connecting it; this guide on shared hosting versus VPS covers the main differences.

There are two standard connection methods:

1. Change nameservers: You delegate DNS management to the hosting provider. The host may create or manage the records needed for the website.
2. Edit DNS records: You keep DNS management at the registrar or another DNS provider and point only the website records to the host.

Nameservers can be simpler for a new website, while individual records provide more control when your domain uses separate providers for hosting, email, commerce, or other services.

Checklist by scenario

Scenario 1: A new domain and shared hosting account

1. Sign in to the hosting dashboard and add your domain. Some hosts call this an “additional domain,” “site,” or “domain setup” option.
2. Copy the host’s two or more nameservers exactly, including any numbers or punctuation.
3. Open the domain registrar’s DNS or nameserver settings.
4. Replace the registrar’s default nameservers with the hosting provider’s nameservers, if this is the method you selected.
5. Confirm that the domain is attached to the correct website directory or document root in the hosting account.
6. Wait for the change to become visible across DNS resolvers. Do not repeatedly switch between nameserver sets while waiting.
7. Return to the hosting dashboard and request or enable the SSL certificate.

A nameserver change can also replace the DNS zone managed by the registrar. Confirm that required email records are present before completing the switch. For a domain that has not previously been used, this is usually a straightforward setup, but the host’s exact dashboard labels may differ.

Scenario 2: Keep DNS at the registrar and point records to hosting

Use this approach when you want to keep email or other services managed separately. The exact record values must come from your host, but a common website configuration looks like this:

• A record for the root domain: The host’s IPv4 address. The host name may appear as @, the root symbol, or the domain without a subdomain.
• CNAME for www: The destination hostname supplied by the host, or sometimes the root domain, depending on the provider’s instructions.

Remove conflicting A, AAAA, or CNAME records only after confirming what they do. The root domain cannot normally have a CNAME alongside other records at the same name, and an outdated AAAA record can send some visitors to the wrong server. Save the changes, then add the domain in the hosting control panel if you have not already done so.

Scenario 3: Managed WordPress hosting

1. Create the WordPress site in the host’s dashboard.
2. Add the domain as the site’s primary or custom domain.
3. Use the host’s supplied nameservers or the specified A and CNAME records.
4. Set the site URL and preferred version, such as the HTTPS version of the root domain.
5. Activate SSL only after DNS points to the WordPress host.
6. Check both the root domain and the www version, then choose one as the canonical address and redirect the other.

Do not install a second WordPress site in a different directory simply because the domain has not resolved yet. DNS delay and an incomplete site installation are separate issues.

Scenario 4: VPS or self-managed server

1. Assign the domain to the server’s public IP address with an A record.
2. Configure the web server’s virtual host or server block for the domain and its www variant.
3. Open the required web ports in the server firewall according to your hosting provider’s instructions.
4. Install and configure the website application.
5. Set up SSL after the web server responds correctly for the domain.
6. Test redirects, the document root, permissions, and application configuration.

Pointing DNS at a VPS does not configure the server automatically. A correct A record can still lead to a default server page, a connection error, or an application error until the web server is configured.

What to double-check

Nameservers and DNS ownership

Make sure you know where DNS is actually managed. A domain registrar may display nameserver settings while a separate DNS provider controls the individual records. Editing records in the wrong dashboard will not change the live configuration.

Email records

Website DNS changes can affect email when nameservers are replaced or when existing records are deleted. Preserve MX records and any TXT records used for email authentication or service verification. If you need email through Microsoft 365 or Google Workspace while hosting the website elsewhere, use a split-service setup rather than moving all DNS records blindly. See this DNS guide for Microsoft 365, Google Workspace, and web hosting.

SSL certificate setup

SSL is normally issued for a domain that already resolves to the correct hosting environment. Enable the certificate through the host, wait for issuance, and test the HTTPS address. Check that HTTP redirects to HTTPS and that images, scripts, forms, and other resources do not load over insecure HTTP. If the certificate cannot be issued, confirm that the domain points to the expected server and that a proxy or conflicting record is not interfering.

Root and www versions

Test both example.com and www.example.com. They can use different records, and one may work while the other shows an error. Choose the preferred version in your hosting or CMS settings and redirect the alternate version consistently.

Propagation and verification

DNS changes are cached by resolvers, so different networks may show different results temporarily. Check the domain from your normal connection and at least one independent DNS-checking service. A propagation guide such as DNS Propagation Time Explained can help distinguish a normal delay from a configuration error.

Common mistakes

• Using the wrong IP address: Copy the address from the current hosting account, not from an old welcome email or a different server.
• Adding a CNAME to the wrong name: A CNAME for www does not automatically configure the root domain.
• Leaving conflicting records in place: Multiple A records can distribute requests between servers unintentionally, and an old AAAA record may bypass a new IPv4 setup.
• Changing nameservers without copying email records: This can interrupt mail even when the website works.
• Checking too quickly: A cached result is not proof that the new configuration failed. Record the time of the change and check from more than one network.
• Forgetting to add the domain at the host: DNS can point to the right server while the host still does not know which site to serve.
• Activating SSL before DNS is ready: Certificate issuance may fail until the domain resolves correctly.
• Testing only one URL: Check HTTP, HTTPS, the root domain, and the www version.

If the site still does not load, use this order: verify nameservers, inspect the root A or CNAME record, check for conflicting records, confirm the domain is added to the host, inspect the server’s document root, and then review SSL and redirects. If you recently moved providers, avoid deleting the old hosting account until the new site and email have been tested.

When to revisit

Keep this checklist with your launch notes and revisit it whenever the underlying setup changes. Review it before a seasonal campaign or other high-traffic period, before changing hosting plans, and before moving email to a new provider. It is also useful after a domain transfer, a website migration, a redesign, or a server replacement.

Before making a change, save a DNS export or screenshots, record the current IP address and nameservers, and list every service that depends on the domain. After the change, verify the website, email, SSL, redirects, forms, subdomains, and third-party verification records. Schedule a second check after caches have had time to refresh.

For a final launch sequence, use this short action list:

1. Confirm the correct hosting destination.
2. Choose nameservers or individual DNS records.
3. Back up the existing DNS configuration.
4. Apply the change and note the time.
5. Check propagation from multiple networks.
6. Enable SSL and test HTTPS.
7. Test email and every important domain version.
8. Keep the previous service available until the new setup is stable.

If you are moving the registration itself rather than only pointing the domain, use a separate domain transfer checklist. A transfer changes registrar control; connecting a domain to hosting changes where website traffic is directed.