How to Point a Domain to Your Hosting in 2026 (Beginner Guide)

Disclosure: This post contains affiliate links; we may earn a commission at no extra cost to you.

Pointing a domain means updating its Domain Name System records so browsers reach your hosting server. You do not need to transfer the domain to the host. Registration can remain at Namecheap, GoDaddy, Cloudflare, or another registrar while the website runs elsewhere.

There are two common methods: replace the domain’s authoritative nameservers with the host’s nameservers, or keep the current DNS provider and change only the website records. Nameservers are simpler for a new site. Individual records give more control and are safer when email or other services already use the domain.

Understand the four accounts involved

A setup may include:

• Registrar: where the domain is registered and renewed
• DNS provider: where authoritative records are managed
• Web host: where site files and database run
• Email provider: where mailboxes receive and send messages

One company can perform all four roles, but it does not have to. Before changing anything, identify each provider. The registrar dashboard’s nameserver section tells you who controls DNS. A DNS lookup tool can confirm the currently published nameservers.

Method 1: change nameservers

Use this method when the host should manage the whole DNS zone. It is convenient for a new domain with no established email or custom records.

Step 1: get the host’s exact nameservers

Find them in the hosting dashboard or official documentation. Copy them exactly. For example, Bluehost currently documents:

ns1.bluehost.com
ns2.bluehost.com

Do not copy nameservers from an old tutorial because providers can use product- or region-specific values.

Step 2: save the existing DNS zone

Screenshot or export all records before changing delegation. Pay special attention to MX, SPF, DKIM, DMARC, verification TXT records, subdomains, and third-party services. When nameservers change, the old provider’s records are no longer authoritative.

Step 3: update the registrar

Log in to the domain registrar—not necessarily the old host. Open the domain’s nameserver or DNS delegation settings, choose custom nameservers, replace the old values, and save.

Do not add a trailing period unless the interface requires it. If DNSSEC is enabled, ask both providers how to coordinate the change. Leaving a stale DS record at the registrar can make the domain fail validation.

Step 4: recreate required records at the host

Confirm the new DNS zone contains the web records and every mail or verification record you saved. A nameserver change does not copy the old zone automatically.

Step 5: wait and verify

DNS resolvers cache answers according to time-to-live values. Changes begin appearing quickly in some places but can take longer worldwide. Bluehost advises allowing 24–72 hours for global propagation. Avoid repeatedly switching settings during that window.

Method 2: change A and CNAME records

Use individual records when you want Cloudflare or another DNS provider to remain authoritative, or when existing email must not be disturbed.

Step 1: obtain the destination

Ask the host for the correct IP address or hostname for your plan. Do not assume the IP shown in an unrelated control-panel screen is the public website destination.

Step 2: update the root domain

The root, apex, or “naked” domain is example.com. It commonly uses an A record pointing to an IPv4 address and possibly an AAAA record for IPv6. Some DNS platforms support flattened CNAME or ALIAS-style records at the apex.

Remove conflicting old web records only after documenting them. Multiple A records can intentionally distribute traffic, so do not delete unfamiliar values without understanding the design.

Step 3: update www

Set www as a CNAME to the root domain or to the hostname specified by the host. Decide whether visitors should use www.example.com or example.com, then configure the web server to redirect the other version.

Step 4: preserve mail

Do not change MX, SPF, DKIM, or DMARC merely to point the website. Website A records and mail routing are separate. However, inspect mail records for hostnames that depend on an old web-server IP.

Which method should a beginner choose?

Choose host nameservers for a brand-new site when the host will manage website and basic email. Choose individual records when the domain already uses Google Workspace, Microsoft 365, Cloudflare, subdomains, or third-party verification.

Nameservers transfer authority for the complete zone. A records change only specified destinations. That is the most important distinction.

Connect an external domain to Bluehost

First add or assign the external domain in the Bluehost Portal so the hosting account recognizes it. Then either set the registrar to Bluehost’s documented nameservers or keep existing DNS and use the destination records Bluehost provides.

Do not point traffic until the site is installed and tested. For a migration, preview the Bluehost copy first, preserve email DNS, and keep the old host active during propagation.

Configure HTTPS

After public DNS reaches the new host, issue or activate SSL. Certificate authorities must confirm the domain points correctly. This can fail temporarily while some resolvers still see the old destination.

Test four addresses:

• http://example.com
• https://example.com
• http://www.example.com
• https://www.example.com

All should reach one preferred HTTPS version without a redirect loop. Update the WordPress Site Address only when you understand how it affects login; an incorrect value can lock you out.

How to verify the change

Use an authoritative DNS lookup or commands such as:

nslookup example.com
nslookup -type=ns example.com
nslookup -type=mx example.com

Check from mobile data and another network to bypass a local cache. Confirm the returned IP is the destination, the expected nameservers are authoritative, and mail records remain intact.

Then test pages, images, forms, login, redirects, and email. A successful DNS lookup proves routing, not application health.

Common problems

The old site still appears: A resolver or browser may have cached the previous answer. Compare authoritative and recursive results before changing records again.

The host shows a default page: DNS reached the server, but the domain may not be assigned to the correct site or document root.

Email stopped: Nameservers changed without recreating MX and authentication records. Restore them at the new authoritative DNS provider.

SSL is pending: Wait for public DNS to stabilize, verify A/AAAA records, and retry issuance through the host.

Only www works: The root record is missing or misconfigured. If only the root works, inspect the www CNAME.

The domain does not resolve after enabling DNSSEC: A DS record may not match the new provider. Coordinate DNSSEC rather than disabling security blindly.

Reduce risk during a migration

Lower relevant TTL values a day or two before a planned switch when possible. Create and test the destination first. Schedule dynamic sites during a quiet window, pause writes, and keep the old server online.

After the change, monitor uptime and errors. Restore longer TTLs once stable. Do not cancel the old host until website, SSL, forms, and email work from multiple networks.

Final checklist

• Domain is active and not near expiration
• Hosting recognizes the domain
• Old DNS zone is saved
• Correct nameservers or web records are published
• Email and verification records are preserved
• Both root and www reach the site
• HTTPS works without loops
• Forms and mail pass tests
• Old hosting remains available during verification

Final verdict

Pointing a domain is a routing change, not a domain transfer. For a simple new site, changing to the host’s nameservers is easiest. For an established domain, changing only the web records preserves greater control and reduces the chance of disrupting email.

Document first, change one deliberate layer, and verify DNS and the application separately.

Frequently asked questions

How long does DNS propagation take?
Some resolvers update quickly, while worldwide caching can take 24–72 hours.

Will changing nameservers transfer my domain?
No. Registration remains with the registrar.

Does pointing a domain affect email?
Changing only web records usually does not. Changing nameservers can if mail records are not recreated.

Can one domain point to two hosts?
DNS can publish multiple addresses, but an ordinary beginner site should use one intentionally configured destination.