You’ve bought a domain and set up hosting — but when you type the domain into a browser, nothing loads. That’s because buying a domain and getting hosting are two separate transactions, and something has to connect them. That connection is made through DNS, and it usually comes down to updating one or two settings at your domain registrar.
The process is quick once you know what to look for. The part that trips people up is knowing which panel to log into and which setting to change — there are two different approaches depending on your setup, and mixing them up is the most common source of confusion.
Everything covered in the step-by-step guide to building a WordPress website — from installing WordPress to configuring your design — depends on this step being done correctly first. A domain that isn’t pointed to your hosting means nothing else will load.
Quick Answer
Log in to your domain registrar and update the nameservers to the ones provided by your hosting company. Save, wait up to 48 hours for DNS propagation, then visit your domain to confirm it loads your hosting account. If you need to keep your existing DNS provider, the alternative is to update the A record in your DNS settings with your hosting server’s IP address instead.
What Domain Pointing Actually Does
Your domain name is just a label — on its own it doesn’t store any website files. DNS (Domain Name System) is the system that translates that label into the IP address of your web hosting server. IANA coordinates the global DNS infrastructure that makes this possible. When someone types your domain into a browser, their device queries a DNS server to find out where to send the request. That lookup returns your hosting server’s IP address, which then responds with your website.
Updating your domain’s nameservers or DNS records is what tells that lookup system where your site lives.
Step-by-Step: How to Point a Domain to Your Hosting
Step 1 — Get Your Hosting Nameservers or IP Address
Before changing anything, get the connection details from your hosting provider. Log in to your hosting account and look for your nameservers — usually displayed as ns1.yourhost.com and ns2.yourhost.com — or your server IP address if you plan to use an A record instead.
Most hosts display nameservers in the account dashboard under a “General” or “Account Information” section. Check the welcome email if you can’t find them. If your host uses cPanel, the guide to managing WordPress hosting in cPanel shows exactly where to locate this information.
Step 2 — Log In to Your Domain Registrar
Go to the platform where you purchased your domain — Namecheap, GoDaddy, Porkbun, or whoever your registrar is. Find your domain in the dashboard and open its DNS or nameserver settings.
If your domain and hosting are with the same company, they may already be connected automatically. Check before making any changes.
Step 3 — Update Nameservers (Recommended Method)
Find the nameserver section — it may be labelled “Custom DNS”, “Nameservers”, or “DNS Settings” depending on the registrar. Remove the current nameservers and replace them with the ones from your hosting provider. Save the changes.
Most registrars require at least two nameservers (typically ns1 and ns2). Copy and paste them directly from your hosting dashboard — typos here will prevent your domain from resolving at all.
Step 4 — Or Update the A Record (Alternative Method)
If you need to keep DNS control at your registrar — for example, if you have email services with specific MX records already set up — you can point just the web traffic to your hosting by updating the A record.
In your DNS settings, find the A record for the root domain (@ or your domain name itself). Change its value to your hosting server’s IP address. If there is a separate www A record or CNAME, update that to match as well.
This keeps your MX records and other DNS entries intact while routing web requests to your hosting server.
Step 5 — Wait for DNS Propagation
After saving, DNS changes can take anywhere from a few minutes to 48 hours to take effect globally. This is called propagation, and it’s governed by TTL (Time to Live) values on your DNS records.
During propagation, some visitors may still see your old site or a blank page depending on which DNS servers their device has cached. You can check how widely the new DNS has propagated using a tool like dnschecker.org, which shows your domain’s resolution across dozens of global DNS servers.
Step 6 — Verify the Domain Is Resolving
Once propagation is complete, enter your domain in a browser. If WordPress is installed, your site should load. If it shows a holding page from your host, DNS has connected but WordPress still needs to be installed — which is the next step.
Nameservers vs A Records: Which Should You Use?
Use nameservers when you want simplicity. Switching to your host’s nameservers hands all DNS management over to them, which means your host controls email records, subdomains, and everything else. It’s the right choice for most straightforward WordPress sites.
Use A records when you need DNS control at the registrar level — for example, if your email runs through a separate provider with existing MX records. Changing to your host’s nameservers would wipe those records out.
In most WordPress builds I work on, nameservers are the cleaner option unless there’s an email or subdomain dependency that requires otherwise. If you ever need to move the domain to a different registrar, the domain transfer guide covers how to handle DNS during the process.
Common Mistakes When Pointing a Domain
Entering nameservers with a typo. A single wrong character stops the domain from resolving. Always copy and paste nameserver values directly from your hosting dashboard.
Trying to edit DNS at the registrar after switching nameservers. Once you’ve pointed to your host’s nameservers, DNS records at the registrar no longer apply. Changes need to be made in your hosting panel instead. This is probably the most common source of confusion when troubleshooting.
Checking too soon. If the site doesn’t load 15 minutes after making the change, that’s almost always propagation delay rather than a configuration error. Wait a few hours before concluding something is wrong.
Forgetting the www subdomain. Some registrars require a separate CNAME or A record for www. If your root domain resolves but www.yourdomain.com doesn’t, this is usually the cause.
Not knowing which provider controls DNS. If nameservers were changed previously — by you or by someone else — the active DNS settings may be at a third-party provider rather than the registrar. Check the current nameservers first to find out where DNS is actually managed.
Understanding DNS records becomes especially useful once your domain is connected. The guide on managing DNS records for your WordPress website covers each record type in detail — including A records, MX records, and TXT records for domain verification — and explains the safest way to make changes.
Conclusion
Update the nameservers at your domain registrar to point to your hosting provider, save the changes, and wait for DNS propagation. Once your domain is loading your hosting account correctly, the next step is installing WordPress and setting up HTTPS — the guide on how to add an SSL certificate to WordPress walks through that process from start to finish.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.