A domain can be registered in one place and hosted somewhere else. That is normal, but it means you need to know how to point a domain correctly before visitors can reach your website. One incorrect DNS change can send visitors to an old site, display an error, or interrupt email. With a few checks before you start, the process is straightforward and low risk.
What pointing a domain actually means
Pointing a domain means telling the internet where to find the services connected to it. For most website owners, that means connecting a domain name such as `yourbusiness.co.uk` to the server that holds the website files, WordPress installation or web application.
This connection is controlled through DNS, short for Domain Name System. DNS records act like directions: when someone enters your domain in a browser, those records tell their browser which server to contact. The same DNS zone can also contain instructions for email, website verification tools and other services.
There are two main ways to point a domain. You can change the domain’s nameservers so that your hosting provider manages all DNS records, or you can keep DNS with the registrar and update only the records required for the website. Neither option is always better. The right choice depends on where your email is managed, whether you use external services, and how much control you need over individual records.
Before you point a domain, check these details
The most common problem is changing DNS before the hosting account or website is ready. First, make sure your hosting package is active and that the domain has been added to it. If you are moving an existing site, upload or migrate the site and test it on a temporary URL, preview address or staging environment where possible.
You will also need the correct destination details. Your host may provide an IPv4 address for an A record, a hostname for a CNAME record, or a pair of nameservers. Copy these exactly. A single wrong character can prevent the connection from working.
Email deserves special attention. If you already receive email at addresses such as `hello@yourbusiness.co.uk`, record the current MX records before changing anything. You may also have SPF, DKIM and DMARC records that help other providers trust your messages. Replacing nameservers without recreating these records can stop mail delivery or cause outgoing messages to fail authentication.
Finally, check whether DNSSEC is enabled at your domain registrar. DNSSEC adds protection against DNS tampering, but its settings must match the DNS provider in use. If you move DNS management to a different provider, you may need to remove the existing DNSSEC delegation first and enable it again once the new zone is working.
How to point a domain using DNS records
Updating individual DNS records is usually the safest route when your email, domain verification records or other services are already managed at the registrar. You leave the existing nameservers in place and amend only the website records.
Point the main domain with an A record
Sign in to the control panel where the domain’s DNS is managed. Find the DNS zone or DNS records section, then locate the A record for the root domain. It may appear as `@`, your full domain name, or an empty host field.
Replace its current value with the IP address supplied by your hosting provider. If there is no A record for the root domain, create one. The record should normally use `@` as the host name, with the supplied IP address as the destination.
Avoid creating multiple conflicting A records for the same root domain unless your host has specifically given you several IP addresses. A browser may be sent to either address, which can produce inconsistent results.
Point the www version with a CNAME record
Visitors may use either `yourdomain.co.uk` or `www.yourdomain.co.uk`, so both should reach the intended site. The usual setup is a CNAME record for `www` that points to the root domain. In the host field, enter `www`; in the destination field, enter your domain name.
Some providers instead ask you to create an A record for `www` using the same IP address as the root domain. Follow the hosting instructions if they specify this. Once both versions resolve, configure a permanent redirect in your hosting control panel, CMS or web server so only one preferred version is shown in search results and shared links.
Check for records that should not be removed
Do not delete MX, TXT or CNAME records simply because they are unfamiliar. They may be used for Microsoft 365, Google Workspace, email security, payment tools or domain ownership checks. If your old website used a record for `www`, it is normally fine to replace that one, but retain unrelated records unless you know their purpose.
This record-by-record method gives you precise control. The trade-off is that you are responsible for keeping website records updated if your host changes server details, which is uncommon but possible.
How to point a domain by changing nameservers
Changing nameservers hands DNS management to the provider named in those settings. It can be the simpler choice when your hosting provider supplies a complete DNS zone and you want website, mail and related services managed in one place.
At your domain registrar, open the domain management area and look for nameservers. Select the option to use custom nameservers, then enter the two or more nameserver addresses supplied by your host. Save the changes.
Before doing this, recreate any essential records in the new DNS zone. That includes MX records for third-party email, TXT records for SPF, DKIM and DMARC, and records for services such as website analytics verification. A nameserver change does not copy your existing records automatically.
Nameserver changes are less granular than updating an A record. They are useful for new websites and straightforward hosting setups, but they require more care for established businesses with several connected services. If you are uncertain, updating the A and CNAME records is often the lower-risk option.
Allow time for DNS propagation
DNS changes do not appear everywhere at the same moment. Internet providers and devices store DNS information temporarily in a cache. This is known as propagation, although the records themselves are simply being refreshed over time.
Many changes are visible within minutes or a few hours. Allow up to 24 to 48 hours for the change to be recognised widely, particularly after a nameserver update. During that period, some visitors may see the old site while others reach the new one.
The TTL, or time to live, of your current DNS record affects this timing. If you are planning a website move, reduce the TTL a day or two beforehand where possible. A value such as 300 seconds lets DNS resolvers refresh more quickly. After the move is stable, you can raise it again to reduce unnecessary DNS lookups.
Do not keep changing records while waiting. Every new edit can make troubleshooting harder and may extend the time before you can tell which configuration is active.
Test the domain after the change
Open the domain in a private browser window and test both the root and `www` versions. Check the homepage, a few internal pages, contact forms and any online checkout or login area. Test on mobile data as well as your usual Wi-Fi connection, as local networks can retain old DNS results.
If email is attached to the domain, send a message to and from an address on that domain. A website may load correctly while mail remains affected by missing MX or TXT records. Also check that your SSL certificate is active. Browsers should show HTTPS without a certificate warning once the domain is connected and the certificate has been issued.
At Blended Hosts, free wildcard SSL certificates and support from a technical team can reduce the number of moving parts, but the DNS records still need to point to the right place. If a certificate does not appear immediately after a DNS change, give the new records time to resolve before requesting further changes.
Common problems when pointing a domain
A parked page or an old website usually means the domain is still pointing at the previous server, or the correct record has not propagated to the network you are using. Recheck the A record destination and confirm that there is no conflicting record for the same host.
A “server not found” message can indicate missing nameservers, a typo in a nameserver address, or an expired domain. Start by confirming that the domain registration is active, then review the DNS settings exactly as supplied by the host.
If the website works but email stops, restore or recreate the previous MX records and relevant TXT records. Do not assume a web host’s default mail records are suitable if your mail is delivered by another provider. Email setups vary, and preserving the working configuration is usually wiser than replacing it.
A certificate warning after a move often means DNS has not fully updated, the domain was not added correctly to the hosting account, or the SSL certificate has not yet been provisioned. Avoid bypassing browser warnings for customers. Resolve the underlying domain and certificate settings first.
Pointing a domain is a small technical task with a big effect on how customers find and trust your business. Prepare the destination, protect your email records, make one deliberate DNS change, then test patiently. That approach keeps your website available while giving your domain a dependable home.
