Overview

To point a domain to a website or server, log into your domain registrar's DNS settings and either (1) set an A record to your server's IP address, (2) add a CNAME record pointing to a hostname, or (3) update your nameservers to your hosting provider's nameservers. Changes take 2–48 hours to propagate.

Why You Need to Point Your Domain

When someone types your domain into a browser, the internet needs to know where to find your website. That's the job of the DNS (Domain Name System). DNS records act like a directory — they map your human-readable domain name (like yourbrand.com) to an actual IP address or server location where your content lives.

Without proper DNS configuration, your domain just sits there doing nothing. By pointing it correctly, you bring your site to life.

Understanding the Key DNS Records

Before diving into steps, it helps to understand the DNS record types you'll be working with.

A Record (Address Record)

The DNS A record is the most fundamental record type. It maps your domain directly to an IPv4 address (like 192.168.1.1). When you want to point a domain to a web server, you're usually setting an A record.

AAAA Record

Same as an A record but for IPv6 addresses (like 2001:0db8:85a3::8a2e:0370:7334). Most modern hosting providers support both.

CNAME Record (Canonical Name)

A CNAME maps one domain or subdomain to another domain name rather than an IP address. For example, you might point www.yourdomain.com to yourdomain.com using a CNAME. CNAMEs are also commonly used to point subdomains to third-party services.

Nameservers (NS Records)

Nameservers tell the internet which DNS provider controls your domain's records. If you change your nameservers to point to a new hosting provider, that provider handles all your DNS records going forward.

Method 1: Point Your Domain Using an A Record

This is the most direct way to point a domain to a web server. Use this when your hosting provider gives you an IP address.

Step-by-Step: Setting Up a DNS A Record

Step 1: Get your server's IP address Log into your hosting account and find the IP address of your server. This is usually listed under "Hosting Details," "Account Info," or in your welcome email.

Step 2: Log into your domain registrar Go to the website where you purchased your domain (GoDaddy, Namecheap, Google Domains, etc.) and log in.

Step 3: Find the DNS management section Look for "DNS Settings," "Manage DNS," "DNS Zone Editor," or similar. This varies by registrar.

Step 4: Locate or create the A record

Find an existing A record for your root domain (@) or create a new one

Set the Host/Name field to @ (which represents the root domain itself)

Set the Value/Points to field to your server's IP address

Set the TTL to 3600 (1 hour) or your registrar's default

Step 5: Update the www A record Repeat the process for www — set the Host to www and the Value to the same IP address.

Step 6: Save and wait Save your changes. DNS propagation typically takes 2–48 hours, though many changes take effect within a few hours.

Method 2: Point a Subdomain Using a CNAME Record

If you want to point a subdomain (like shop.yourdomain.com or blog.yourdomain.com) to a third-party platform, a CNAME is usually the right approach.

Step-by-Step: Setting Up a CNAME Record

Step 1: Get the target hostname from your service provider For example, Shopify might give you shops.myshopify.com. Squarespace might give you ext-cust.squarespace.com. Check your platform's documentation.

Step 2: Go to your DNS settings Log into your registrar's DNS management panel.

Step 3: Create a CNAME record

Set the Host/Name to your subdomain prefix (e.g., shop)

Set the Value/Points to to the target hostname your platform provided (e.g., shops.myshopify.com)

Include a trailing period if required by your registrar (e.g., shops.myshopify.com.)

Step 4: Save and verify Save the record and allow time for propagation. Use a tool like whatsmydns.net or dig to verify the CNAME is resolving correctly.

Method 3: Change Nameservers to Point to a New Host

If you're moving your entire website to a new hosting provider, the cleanest approach is to update your nameservers. This delegates all DNS management to your new host.

Step-by-Step: Updating Nameservers

Step 1: Get your new host's nameservers

Your hosting provider will give you two or more nameserver addresses, such as:

ns1.newhost.com

ns2.newhost.com

Step 2: Log into your domain registrar Navigate to your domain's settings.

Step 3: Find the nameserver settings Look for "Nameservers," "DNS Servers," or "Custom Nameservers."

Step 4: Replace the current nameservers Delete the existing nameservers and enter the ones from your new host. Most providers require at least two.

Step 5: Save and wait Nameserver changes can take up to 48 hours to propagate globally. During this time, some users may see your old site while others see the new one.

Method 4: URL Redirect (Forwarding a Domain)

If you want to redirect your domain to an entirely different website (not a server you control), you can use URL forwarding.

Types of Redirects

301 Redirect (Permanent): Tells browsers and search engines the move is permanent. Best for SEO if you're changing your domain long-term.

302 Redirect (Temporary): Indicates a temporary move. Search engines keep the original URL indexed.

How to Set Up URL Forwarding

1. Log into your registrar

2. Find "Domain Forwarding" or "URL Redirect" settings

3. Enter the destination URL (e.g., https://www.newwebsite.com)

4. Choose the redirect type (301 or 302)

5. Save and allow propagation

Note: URL forwarding works at the registrar level and may not forward subfolders or query strings in all cases. For complex redirects, server-level configuration is better.

Common Mistakes When Pointing a Domain

Mistake 1: Forgetting the www Subdomain

Setting up the A record for @ (root domain) but not for www means visitors who type www.yourdomain.com won't reach your site. Always configure both.

Mistake 2: Using a CNAME on the Root Domain

Most DNS providers don't allow a CNAME on the root domain (@) because it conflicts with other required records (like MX records for email). Use an A record for the root and a CNAME for www if needed.

Mistake 3: Not Waiting for Propagation

Changes take time to spread. Don't make additional changes in a panic if the site doesn't appear immediately — you may end up with conflicting records.

Mistake 4: Mixing Up Hosting IP Addresses

If your host offers both shared and dedicated IPs, make sure you're using the correct one. Point to the wrong IP and your site won't load.

How to Verify Your DNS Setup Is Working

Once propagation has settled, verify everything is correct:

1. Use dig (Mac/Linux): Run dig yourdomain.com A to see what IP the domain resolves to

2. Use nslookup (Windows): Run nslookup yourdomain.com

3. Use an online checker: Sites like mxtoolbox.com or dnschecker.org let you check A, CNAME, MX, and other records from multiple locations

If the IP address shown matches your server's IP, you're good to go.

Real-World Example

Let's say you purchased yourbrand.com on Namecheap and signed up for hosting with SiteGround. SiteGround gives you an IP address of 185.68.14.3.

Here's what you'd do:

1. Log into Namecheap → Manage → Advanced DNS

2. Set A record: Host = @, Value = 185.68.14.3, TTL = Automatic

3. Set A record: Host = www, Value = 185.68.14.3, TTL = Automatic

4. Delete any conflicting CNAME records for @ or www

5. Save changes and wait up to 48 hours

Within a day, anyone typing yourbrand.com or www.yourbrand.com will land on your SiteGround-hosted site.

Expert Verdict

Pointing a domain is one of the most fundamental DNS tasks, yet it's a step where many website launches stall. The single most common failure is configuring the root domain A record without also configuring the www A record — causing roughly half of all URL variations to fail silently. Always treat the root domain and www as separate records that both require explicit configuration.

For teams migrating from one host to another, the nameserver method is the cleanest long-term approach because it centralizes all DNS management at the new host. The A record method is better for granular configurations where you need the registrar to continue managing DNS for email or subdomains separately. The CNAME method is the correct choice for connecting subdomains to third-party services — and critical to get right because platforms like Shopify, HubSpot, and Squarespace provide hostname targets that must be matched exactly.

When in doubt, verify every change with dig or an online DNS checker before assuming the configuration is complete. DNS errors are silent by default — the domain simply won't resolve rather than throwing an obvious error message.

Frequently Asked Questions

Conclusion

Pointing a domain to a website or server is a foundational skill for anyone managing a web presence. Whether you're using a DNS A record for a direct IP connection, a CNAME for subdomains, or updating nameservers for a full host migration, the process is manageable once you understand the steps.

The key is knowing which method fits your situation and being patient during propagation.

Looking to register the perfect domain before setting up your DNS?

Use DomainsDiscovery.com to check domain availability and compare prices across registrars instantly.