How to Point a Domain to Hosting

What “Point Domain to Hosting” Means

A domain and a hosting account exist independently until DNS links them. Pointing a domain to hosting means updating the domain’s DNS so that requests for example.com resolve to the IP address, or hostname, of the server where the site’s files actually live. Without this step, a domain shows either a registrar parking page or nothing at all. This happens regardless of how well the hosting itself is configured.

The Two Ways to Point a Domain to Hosting

Option 1 — Change the nameservers

This hands full DNS management to the hosting provider. The host supplies its nameservers, often two, for example ns1.hostname.com and ns2.hostname.com. Every DNS record — A, MX, CNAME — is then managed inside the host’s control panel. This is the simplest option for most beginners. Full walkthrough: how to change nameservers.

Option 2 — Edit individual DNS records

This keeps the domain’s existing DNS provider (often the registrar) in charge. It only points the specific records needed at the host — typically an A record for the root domain, and sometimes a CNAME record for www. This is preferred when other services (email, subdomains) are already configured elsewhere and shouldn’t move.

Point Domain to Hosting: Step-by-Step

1. Get the hosting details. From the new host’s welcome email or dashboard, note either the assigned nameservers or the server’s IP address.
2. Decide nameserver change vs record edit, based on whether anything else currently depends on the domain’s existing DNS.
3. Log in to the DNS control panel — either at the registrar (if keeping existing DNS) or the new host (if switching nameservers).
4. Update the nameservers, or add or edit the A record to point the root domain at the host’s IP. Also point the www CNAME at the root domain or host.
5. Save changes and wait for propagation. Check with a DNS lookup tool rather than just refreshing the browser, since local caching can mask the live state.
6. Verify the site loads over HTTPS once an SSL certificate is issued for the new host.

Timing and Propagation

DNS changes made during this process are subject to propagation — the delay before every resolver worldwide picks up the new value. Typical full propagation ranges from a few minutes to 48 hours. The speed depends on the record’s TTL and how aggressively various networks cache DNS. During this window, some visitors may reach the old server and others the new one. This is a normal, temporary state, not a fault.

Record Reference for Pointing a Domain

The core records involved:

• A record — maps the root domain directly to an IPv4 address. See DNS A record.
• CNAME record — maps a subdomain (commonly www) to another hostname. See CNAME record.
• NS records — define which nameservers are authoritative for the domain, changed when switching to a host’s DNS entirely.

The complete field-by-field reference is at DNS record types.

Troubleshooting a Domain That Won’t Point Correctly

• Site still shows the old host after 48 hours: check that the A record or nameservers were actually saved. A common cause is editing the wrong DNS zone, for example at the registrar when nameservers already point elsewhere.
• “This site can’t be reached”: usually mid-propagation, or the A record has a typo in the IP address.
• Site loads but email breaks: happens when nameservers are switched without recreating the MX records at the new provider. See MX record.
• SSL warning after pointing the domain: the certificate for the new host hasn’t been issued yet. This typically resolves once the host detects the domain resolving correctly.

Relationship to Hosting

This step is the literal handshake between a domain purchase and a hosting purchase. Neither is usable to the public without it. It comes up constantly during setting up hosting for the first time and every time a site switches hosts. The new host always needs the same pointing step, even though the domain itself doesn’t move.

FAQ

Should I change nameservers or just edit the A record? Change nameservers for full simplicity when the new host will manage everything. Edit individual records only when other services still depend on the current DNS provider.

How do I know when the domain has fully pointed to my new host? Use a DNS lookup tool to check the live A record value or nameservers from multiple locations. Don’t rely on a single browser’s cached result.

Will my email stop working while I point the domain? Only if the MX records aren’t recreated at the new DNS provider when switching nameservers. Editing individual records without touching MX leaves email untouched.

Can I point one domain at two different hosts? Not for the same record — a root domain’s A record can only point at one IP at a time. Different subdomains, though, can point at different hosts via separate records.