How to Point a Domain to Web Hosting: DNS Records, Propagation Checks, and Troubleshooting

Overview

Your domain registrar controls the domain name, while your hosting provider stores the website files and serves the site to visitors. DNS, or the Domain Name System, connects the two by telling browsers where to find the website and related services such as email.

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

• Change nameservers: You delegate DNS management to the hosting provider. The host usually supplies two or more nameserver addresses, and its control panel manages the required records.
• Edit DNS records: You keep DNS management at the registrar or another DNS provider and add specific records, usually an A record for the root domain and a CNAME record for www.

Neither approach is automatically better. Nameservers can be simpler when the hosting provider gives you a complete setup. Individual records offer more control when you already use separate email, verification, security, or third-party services. Before changing anything, record your current DNS settings and confirm which services depend on them.

For broader launch planning, see How to Launch a Website With Your Own Domain. This article focuses specifically on the DNS and domain-management connection.

Checklist by scenario

Scenario 1: Your host provides nameservers

1. Sign in to your hosting account and locate the account’s nameserver addresses. Copy them exactly; do not substitute the website’s IP address unless the host specifically instructs you to do so.
2. Sign in to your domain registrar and open the domain’s nameserver or DNS management settings.
3. Replace the existing nameservers with the host’s nameservers. Save the change.
4. Return to the hosting control panel and add the domain to the hosting account if the provider requires this separate step. Some hosts call this an “ addon domain,” “domain alias,” or “primary domain” setting.
5. Confirm that the website files or content are installed in the directory assigned to the domain.
6. Wait for DNS changes to become visible, then test both the root domain, such as example.com, and the www version.

Changing nameservers can also affect email and other DNS-based services. If the domain already has MX, TXT, or custom records, recreate or verify them in the new DNS zone before relying on the new setup.

Scenario 2: Your host gives you an IP address

1. Keep the current nameservers if you want DNS to remain with your registrar or existing DNS provider.
2. Find the hosting provider’s server IP address. Use the value supplied for your specific account, not an IP copied from another website or general help article.
3. Create or update an A record for the root domain. The host or DNS dashboard may represent the root as @ or leave the host field blank.
4. Set the record’s value to the hosting IP address and use the provider’s recommended TTL, or leave the default if no guidance is provided.
5. Create a CNAME record for www pointing to the root domain, if your provider recommends that arrangement. Alternatively, the host may provide a separate target for www.
6. Make sure the domain is also configured inside the hosting account. DNS alone does not tell the server which website to display.

An A record maps a name to an IPv4 address. A CNAME creates an alias to another hostname. Use the record type and target specified by the host, and avoid creating conflicting records for the same hostname.

Scenario 3: You are connecting managed WordPress or a hosted platform

Managed WordPress services and hosted platforms often provide a setup wizard with a verification record, an A record, a CNAME, or a combination. Follow the platform’s exact order: add the domain in the platform dashboard, copy the requested DNS values, enter them at the active DNS provider, and return to the platform to verify ownership.

Do not assume that a successful verification means the public website is fully ready. Check the platform’s domain settings, preferred version, redirects, SSL status, and whether the domain is assigned to the correct project or site.

Scenario 4: You also use email on the domain

Website records and email records are separate. MX records identify the mail service, while TXT records may be used for email authentication or service verification. When changing nameservers, copy the required MX and TXT records into the new DNS zone. When editing records manually, avoid deleting existing mail records simply because the website host did not mention them.

What to double-check

• Active DNS provider: The place where you edit records may not be the registrar. Check the domain’s current nameservers first.
• Correct domain scope: The root domain and www are separate hostnames. Configure both or use the redirect and alias settings supplied by the host.
• Record conflicts: Do not leave an old A record in place if it conflicts with the new target. A hostname should not have competing instructions unless the provider explicitly supports that configuration.
• Hosting account setup: Add the domain to the server and select the correct document root, site, or project.
• Email continuity: Preserve MX records and relevant TXT records before changing nameservers.
• Propagation checks: Use a DNS propagation checker to compare the A, CNAME, and nameserver results from multiple locations. Results can differ temporarily while caches expire.
• Local caching: Test from a different network or device if your computer continues showing an old result. A browser, operating system, router, or internet provider may cache DNS information.
• SSL after the DNS change: Once the domain resolves to the correct host, enable or request the host’s SSL certificate. Test both HTTP and HTTPS, confirm the certificate covers the intended hostname, and check that the site redirects to the preferred secure version.

Keep a simple connection worksheet with the domain, registrar, active DNS provider, nameservers, hosting account, A record target, CNAME target, MX records, SSL status, and the date of the last change. This makes future domain transfers, host changes, and troubleshooting much easier. The Domain Management Checklist can help organize the wider ownership and security tasks.

Common mistakes

Changing records at the wrong provider

If the domain uses external nameservers, edits made in the registrar’s default DNS panel may have no effect. Identify the authoritative nameservers before making changes.

Expecting instant propagation

DNS changes are cached. Some networks may show the new destination while others still show the previous one. Avoid repeatedly changing records during this period; confirm the intended values first and allow caches to update.

Using the wrong record type

An IP address normally belongs in an A record, while a hostname target normally belongs in a CNAME record. Do not place a hostname in an A record or an IP address in a CNAME record unless the provider’s instructions clearly describe a different setup.

Deleting email records

Replacing a DNS zone without preserving MX and TXT records can interrupt email or service verification even if the website works. Export or document existing records before switching nameservers.

Assuming DNS creates the website

DNS only directs traffic. The hosting account must contain the site, recognize the domain, and serve the correct files or application. A “domain not connected” message can therefore come from either DNS or the hosting configuration.

Requesting SSL too early

Many hosting platforms need the domain to resolve correctly before issuing or activating SSL. Complete DNS setup first, then follow the host’s SSL process and retest the secure URL.

When to revisit

Use this checklist whenever you register a new domain, move to different web hosting, change nameservers, create a subdomain, migrate email, or add a third-party platform. Revisit it before seasonal planning cycles or major campaigns so the domain, redirects, SSL certificate, email, and landing pages are confirmed before traffic increases.

Also review your connection worksheet after changes to the registrar, DNS provider, hosting account, or site architecture. Provider dashboards and recommended record values can change, so use the current instructions for your account rather than relying on an old screenshot or copied configuration.

Final action checklist: identify the active DNS provider; choose nameservers or individual records; preserve email records; configure the domain inside hosting; verify the root and www hostnames; check DNS results from more than one location; enable SSL; test redirects and email; then document what changed. If the site still does not connect, compare the expected records with the actual DNS results and contact the registrar or host responsible for the mismatched step.