Comparisons & Alternatives

How to Point Your Domain to a Hosting Server: Step-by-Step

Learn how to point your domain to any hosting provider by changing nameservers or updating DNS A records, regardless of where you bought the domain.

A young boy sitting at a desk, focused on his homework surrounded by school supplies.

To point your domain to a hosting server, change the domain's nameservers to the ones provided by your hosting company, or update the DNS A record with your server's IP address. The nameserver method is most common; the A record method is best when you only want to move the website without touching other services like email.

This guide covers both options, when to use each one, and how to confirm the change worked.

Nameservers or A Record? Pick the Right Method

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

  • Change the nameservers (NS): Hands full DNS control over to the hosting provider. Easiest option and recommended if you want everything managed in one place.
  • Update only the A record: The domain keeps using its current DNS (e.g., GoDaddy or Namecheap), but the A record is updated to point to the new host's IP. Best when you have email or other subdomains already configured that you don't want to disturb.

If this is your first hosting account or you're starting fresh, go with the nameserver change.

Method 1: Change the Nameservers

This is the most common approach. Your new host will provide two or more nameservers in a format like ns1.yournewhost.com.

Step 1: Get the nameservers from your hosting provider

Check your hosting welcome email or log in to the control panel (cPanel, Plesk, etc.) and look for account information. Write down both NS1 and NS2 values.

Step 2: Log in to where you registered the domain

Go to the registrar where you bought the domain (GoDaddy, Namecheap, Google Domains, IONOS, etc.) and find the domain management or DNS / Nameservers section.

Step 3: Replace the current nameservers

  1. Find the option to edit nameservers.
  2. Delete the registrar's default nameservers.
  3. Enter the new nameservers from your hosting provider (NS1 and NS2).
  4. Save the changes.

Once saved, the change begins propagating across the internet. This can take anywhere from 2 to 48 hours, though most users see it complete within 4 hours.

Method 2: Update Only the A Record

If you want to keep DNS control at the current registrar (for example, to preserve existing email settings), just update the A record for the domain.

Step 1: Get the IP address of your new hosting

Log in to your hosting control panel (cPanel, Plesk, etc.) and find the shared IP address or dedicated IP for your account. It's usually in the welcome email too.

Step 2: Edit the A record at your registrar

  1. Open the DNS zone editor for your domain at the registrar.
  2. Find the A record with the name @ (this represents the root domain, e.g., example.com).
  3. Change the value (IP address) to your new hosting server's IP.
  4. If you also want www.example.com to point there, update the A record with name www as well.
  5. Save the changes.

A record propagation is usually faster than a nameserver change: 15 minutes to 4 hours in most cases, depending on the record's TTL.

Method Comparison

Criteria Change Nameservers Change A Record
Difficulty Very easy Easy (requires DNS zone access)
Propagation time 2–48 hours 15 min–4 hours
Affects existing email Yes (if MX isn't reconfigured) No (MX records untouched)
DNS control Moves to hosting provider Stays at the registrar
Best for New sites or full migrations Moving just the website

How to Verify Your Domain Is Pointing Correctly

After making the change, use these tools to check propagation status:

  • whatsmydns.net: Shows real-time DNS propagation across different regions worldwide.
  • dig (Linux/Mac terminal): Run dig +short example.com A to see the IP your domain currently resolves to.
  • nslookup (Windows): Type nslookup example.com in the command prompt to query the current A record.

If the IP shown is your new hosting server's IP, propagation has reached your location. If not, wait a few more hours and check again.

Common Mistakes When Pointing a Domain

  • Typos in nameservers: A single wrong character means the domain won't resolve. Double-check every letter.
  • Forgetting the www record: Updating the root @ A record doesn't automatically update www — edit them separately.
  • Losing email access: After a nameserver change, MX records from the old registrar stop working. Recreate them in the new DNS zone.
  • Impatience: If the old site still shows up right after the change, that's normal — propagation takes time.
  • High TTL: If your DNS record TTL was set to 86400 seconds (24 hours), changes will be slow to propagate. Lower the TTL to 300 seconds well in advance of future migrations.

Want an expert to handle your DNS setup without risking downtime? Visit elenlace.com and get a quote for your website migration.

Find more related guides in our hosting comparisons and tutorials section.

Key Takeaways

  • You have two ways to point a domain to hosting: change the nameservers (simplest) or update only the A record (more surgical).
  • Nameserver changes take 2–48 hours; A record updates can propagate in under an hour.
  • If you have corporate email set up, use the A record method to avoid email interruptions.
  • Verify the result with whatsmydns.net or the dig command.
  • Lower your TTL in advance to speed up future propagation windows.

Not sure which method fits your setup? The team at elenlace.com can advise you and handle the entire DNS change on your behalf.

FAQ

How long does DNS propagation take?

It depends on the type of change and the record's TTL. Nameserver changes typically take 2–48 hours. A record changes can be visible in as little as 15 minutes if the TTL is low, or up to 24 hours if it's high.

Can I point my domain to hosting without changing nameservers?

Yes. If you edit the A record directly in your registrar's DNS zone to point to the new hosting server's IP, the website will work on the new server even though the nameservers remain at the registrar.

What happens to my email if I change nameservers?

When you change nameservers, DNS management moves to the new provider. If your email depends on MX records that were at the previous registrar, you'll need to recreate those MX records in the new DNS zone for email to keep working.

How do I find my hosting server's IP address?

Check your hosting welcome email or look inside the control panel — in cPanel it's under Account Information; in Plesk it's in the Hosting Account panel. You can also ask your hosting provider's support team and they'll give it to you directly.

Further reading

Other providers and guides worth comparing:

← All