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

Overview

A domain is the human-readable address people use to reach your site. Hosting is the server space where the site files, database, and application live. DNS, or the Domain Name System, connects the two by telling browsers where to look.

Before changing anything, collect these details:

• The domain registrar account, where the domain’s registration and DNS settings are managed.
• The hosting account and the provider’s instructions for connecting a domain.
• The hosting destination, usually an IP address for an A record or a hostname for a CNAME record.
• The exact email DNS records if the domain already handles business email.
• The website’s preferred version, such as https://example.com or https://www.example.com.

There are two main ways to connect a domain to hosting:

1. Change nameservers: You delegate DNS management to the hosting provider by replacing the domain’s current nameservers with the provider’s nameserver addresses.
2. Edit DNS records: You keep DNS management at the registrar or another DNS provider and add records that point the domain to the host.

Nameserver changes are often simpler for a new website because the host can provide a ready-made DNS zone. Editing individual records gives you more control and is usually safer when the domain already supports email, subdomains, verification records, or other services.

Checklist by scenario

Scenario 1: A new domain with no existing email or services

1. Sign in to the hosting account and choose the option to add, connect, or use an existing domain.
2. Note whether the host supplies nameservers, an IP address, or a target hostname. Do not guess these values.
3. If using nameservers, open the registrar’s nameserver settings and replace the existing nameservers with the complete set supplied by the host. Save the change.
4. If using records, open the DNS management screen and add the required root-domain record. A root or apex record is commonly represented by @ in a DNS dashboard.
5. Add a www record if the host requires one. This is commonly a CNAME pointing to a host-provided hostname, although some setups use another record type.
6. Wait for DNS changes to become visible, then test both the root domain and the www version.

Avoid adding several competing records for the same hostname unless the hosting provider specifically instructs you to do so. For example, an A record and a CNAME generally should not occupy the same name at the same time.

Scenario 2: The domain already has business email

Use extra caution. Email depends on DNS records, especially MX records, and may also use TXT records for sender authentication or service verification. A complete nameserver change can replace the existing DNS zone and interrupt mail if the email records are not recreated correctly.

1. Export, copy, or document the current DNS records before making changes.
2. Identify the email provider’s MX, TXT, and any required CNAME records.
3. Prefer adding only the website records when your current DNS provider can manage them.
4. If you must change nameservers, recreate the email records in the new DNS zone before or during the change, using the values supplied by the email provider.
5. Send and receive test messages after the website is working. Check that existing mailboxes, forwarding, and aliases still behave as expected.

Do not delete an MX record simply because the website host does not mention email. Website hosting and email hosting can be separate services.

Scenario 3: A WordPress site is moving to a new host

Complete the WordPress migration before pointing public traffic to the new server. Confirm that the files, database, media library, redirects, and site URL are ready. Then connect the domain using the new host’s instructions.

• Use a temporary address or preview method when the host provides one.
• Check the homepage, important pages, forms, images, login screen, and redirects before switching DNS.
• Lowering the DNS record’s TTL before a planned move may help reduce the time some networks retain the old answer, but it does not guarantee instant propagation.
• Keep the old hosting account available until the new site and email have been verified.

For broader preparation, use the Website Launch Checklist and the WordPress Maintenance Checklist.

What to double-check

DNS record types

An A record points a hostname to an IPv4 address. An AAAA record points to an IPv6 address when the provider supplies one. A CNAME points one hostname to another hostname and is frequently used for www or service-specific subdomains. MX records direct email delivery, while TXT records can hold verification or email-authentication information.

Use the record name format expected by the dashboard. Some interfaces want @ for the root domain; others want the domain name or leave the field blank. Entering the full domain where only a host label is expected can create an incorrect record.

Propagation and verification

DNS changes are cached by recursive DNS resolvers, so different networks may see the old and new destination for a period of time. Check the domain from more than one connection if possible, but do not repeatedly edit records while waiting. A DNS lookup tool can help you compare the visible A, CNAME, and MX results with the values supplied by your providers.

SSL and the canonical address

After DNS points to the correct hosting account, enable the host’s SSL or HTTPS feature. Many hosting dashboards can issue and renew a certificate automatically, but the domain must usually resolve to the correct server first. Test both http:// and https://, and confirm that the preferred version redirects consistently.

Also decide whether visitors should use the root domain or the www version. The other version should redirect to it rather than showing a separate, inconsistent site. Do not treat an SSL certificate as proof that DNS is correct: HTTPS can be enabled for the wrong site or an incomplete configuration can still produce warnings.

Common mistakes

Another common error is editing DNS at the wrong provider. The registrar may not be the active DNS host if nameservers were previously changed. First identify which nameservers are authoritative, then make edits in the corresponding DNS dashboard.

When to revisit

Keep this checklist with your website records and revisit it before a hosting migration, domain renewal, email-provider change, rebrand, new subdomain, or seasonal campaign. It is also worth reviewing after a hosting dashboard redesign or when a provider changes its connection instructions.

Before making a future change, capture the current DNS zone, note the date and reason for the edit, and record the expected result. Afterward, verify the website, HTTPS, email delivery, contact forms, and important third-party integrations. For a complete launch review, see the Complete Small Business Website Launch Checklist and the SEO Checklist for a New Website.

Final action list: identify the active DNS provider, copy existing records, choose nameservers or individual records, add only the values supplied by your providers, wait for DNS visibility, enable SSL, test both domain versions, and confirm that business email still works. Save the final record list so the next update is a controlled change rather than a guess.