If you have registered a new domain and want it to open your website on your hosting account, you need to connect the domain to the correct DNS records and hosting space. In most cases, this means updating the nameservers at the registrar, pointing the domain to your hosting provider, and then making sure the domain is added inside the control panel. Once the DNS changes propagate, visitors will reach the website files stored on your hosting account.
What it means to point a domain to hosting
Pointing a domain to hosting means telling the Domain Name System (DNS) where the website should load from. When someone enters your domain name in a browser, DNS translates that name into the server address for your hosting account.
For a new domain, there are usually two common setup methods:
- Change the nameservers to the ones provided by your hosting company.
- Keep DNS at the registrar and update A, AAAA, or CNAME records manually.
Both methods work, but the easiest option for most website owners is to use the hosting provider’s nameservers. This gives you control over DNS from your hosting control panel and keeps website setup in one place.
Before you start
Make sure you have the following details ready:
- Your new domain name.
- Your hosting account login details.
- The nameservers or DNS records provided by your hosting company.
- Access to the domain registrar where the domain was purchased.
- The destination folder or site root in your control panel if your website files are already uploaded.
If you use a panel such as Plesk, cPanel, or a similar hosting control panel, you will usually manage the domain and website mapping there after DNS is updated.
Method 1: Change the domain nameservers to your hosting provider
This is the simplest way to point a new domain to your hosting account. Instead of editing individual DNS records, you delegate DNS management to the hosting platform.
Step 1: Find the correct nameservers
Log in to your hosting account or welcome email and locate the nameserver values. They usually look like:
- ns1.example-host.com
- ns2.example-host.com
Use only the nameservers supplied by your provider. Do not guess or mix records from different services.
Step 2: Log in to your domain registrar
Open the account where you bought the domain. This may be a registrar, reseller panel, or a third-party domain management service.
Step 3: Replace the current nameservers
Find the DNS or nameserver settings for the domain. Select the option to use custom nameservers, then enter the values from your hosting provider.
Typical changes include:
- Removing registrar default nameservers.
- Entering nameserver 1 and nameserver 2 from your hosting account.
- Saving the changes.
Step 4: Add the domain to your hosting account
After updating nameservers, sign in to your hosting control panel and make sure the domain is added to the account. Depending on the platform, this may appear as:
- Addon domain
- Domain
- Website
- Domain alias or parked domain
In Plesk, for example, you typically add the domain under the Domains section and point it to the correct document root, such as httpdocs or a custom folder.
Step 5: Wait for DNS propagation
DNS changes do not update instantly everywhere. Propagation can take from a few minutes to 24–48 hours, depending on TTL values, registry caching, and ISP refresh cycles. During this time, some visitors may see the new site while others still see the old destination or an error page.
Method 2: Point the domain using DNS records
If you want to manage DNS somewhere else, you can point the domain manually by editing DNS records at the registrar or DNS provider. This is useful when you want to keep email or other services separate from the hosting platform.
Use an A record for the website
Create or edit the A record for the domain so that it points to your hosting server’s IPv4 address. For example:
- Host: @
- Type: A
- Value: your server IP address
If your provider supports IPv6, you may also need an AAAA record.
Use a CNAME for www
To make sure www.yourdomain.co.uk also works, add a CNAME record for www pointing to the root domain or the provider’s target hostname.
- Host: www
- Type: CNAME
- Value: yourdomain.co.uk
Some hosting setups prefer www to point to the same server IP using an A record instead. Follow the DNS format recommended by your provider.
Check the hosting control panel mapping
Even when DNS is correct, the domain must be assigned inside the hosting account. In your panel, confirm that the domain’s document root points to the correct website folder. If you are using Apache-based hosting, the virtual host or domain alias settings should match the hostname you want to serve.
How to set up the domain in Plesk
If your hosting uses Plesk, the process is usually straightforward:
- Sign in to Plesk.
- Go to Websites & Domains.
- Click Add Domain or Add Subdomain if needed.
- Enter the domain name.
- Choose the correct document root.
- Save the setup.
If the domain is already managed elsewhere, you may need to update DNS records before Plesk can display the site correctly. You can also use Plesk to issue SSL certificates once the domain resolves to the hosting account.
How to verify the domain is pointing correctly
After making changes, check whether the domain is resolving to your hosting account. You can test this in several ways:
- Open the domain in a browser and see whether the default hosting page or website loads.
- Use DNS lookup tools to check the current A record or nameserver values.
- Check the hosting control panel to confirm the domain is attached to the correct site folder.
- Look at server logs if you still see an error such as 404, 403, or a default placeholder page.
If the site loads but shows the wrong content, the domain may be pointing to the correct server but the document root may be set incorrectly.
Common mistakes when pointing a new domain
Many first-time setup issues come from small configuration errors. The most common ones are:
Using the wrong nameservers
If the nameservers do not match your hosting provider’s values, DNS will not route traffic to the correct account. Double-check every character, including numbers and hyphens.
Forgetting the www version
A domain may work without www but fail with it, or vice versa. Make sure both versions resolve properly by setting the correct A or CNAME records and, if needed, redirects.
Not adding the domain in the control panel
DNS alone is not enough. The hosting account must know which website should respond for that domain. Add the domain in the control panel and check the document root.
Using old cached DNS data
Your computer, browser, or local network may cache previous DNS results. If the site does not appear correctly, try a different device, clear DNS cache, or test from another connection.
Changing DNS and website files at the same time
If you are also uploading a new site, wait until DNS points to the right hosting account before troubleshooting files. Otherwise, you may be checking the wrong server.
How long DNS changes take
DNS propagation depends on the DNS provider, TTL settings, and caching across the internet. In many cases, changes begin working within an hour, but full propagation can take up to 48 hours.
If you need a faster switch, lower the TTL value before making the update. However, not all registrars allow instant TTL control, and DNS caches outside your control may still delay updates.
What to do after the domain is connected
Once the domain points to your hosting account, complete the rest of the website setup:
- Upload your website files to the correct document root.
- Install WordPress or another CMS if needed.
- Set up an SSL certificate so the site uses HTTPS.
- Create email accounts only if your email is hosted with the same provider.
- Set redirects from non-preferred versions, such as non-www to www, if required.
If you are launching a new website, it is also a good time to check your homepage, contact page, robots.txt file, and basic SEO settings.
Troubleshooting checklist
If the domain still does not open your site, go through this checklist:
- Confirm the domain is active and not expired.
- Check that the nameservers are saved correctly at the registrar.
- Confirm the domain is added to the hosting account.
- Verify the A record or CNAME points to the right target.
- Check the document root in the control panel.
- Make sure the website files exist in the correct folder.
- Wait for DNS propagation if changes were made recently.
- Test both the root domain and the www version.
FAQ
Do I need to update nameservers or DNS records?
Either method works. Updating nameservers is usually easier because your hosting provider manages DNS for you. Updating records manually gives you more control if you need to keep DNS elsewhere.
Can I point a domain without moving email?
Yes. If you only change the website A record or nameservers carefully, you can keep email services separate. Just make sure MX records remain correct if email is handled by another provider.
Why does my domain still show the registrar page?
This usually means DNS changes have not fully propagated, the wrong nameservers are set, or the domain has not been added in the hosting control panel.
Why does the site work on one device but not another?
Different networks and devices may cache DNS for different lengths of time. This is normal during propagation. Test from another network or use a DNS lookup tool.
Do I need SSL after pointing the domain?
Yes, if you want the site to load over HTTPS. Most hosting platforms let you issue a free SSL certificate after the domain resolves correctly.
What if my hosting account uses a temporary URL?
A temporary URL is useful for testing, but it does not replace proper domain setup. Once the domain is connected, update the site URL so the primary domain is used consistently.
Summary
To point a new domain to your hosting account, you usually either change the nameservers at the registrar or update DNS records such as A and CNAME entries. After that, add the domain in your hosting control panel, confirm the document root, and wait for DNS propagation. Once the domain resolves correctly, you can upload your site, enable SSL, and finish the launch setup.