How to Point DNS Records to Your Hosting Account
Registering a domain and buying hosting are usually two separate steps. Your domain may be registered with one company while your website is hosted somewhere else. To make the domain open your website, you must connect the two using DNS.
DNS, or the Domain Name System, works like an address book for the internet. When someone enters your domain name, DNS helps their browser find the server where your website is hosted. If the records are missing or incorrect, visitors may see an error page, an old website or a message saying that the domain cannot be found.
This guide explains the two common ways to connect a domain to a hosting account: changing nameservers and editing individual DNS records. It also explains how to avoid disrupting business email, which is especially important for Nigerian businesses, creators and organisations that rely on domain-based communication.
What you need before making changes
Have the following details ready:
- Your domain registrar login details. This is the account where the domain was registered.
- Your hosting account login details.
- The nameservers provided by your hosting company, or the hosting server’s IP address.
- Any email settings supplied by your email hosting provider.
- Access to the email address used for important account notifications and domain renewal reminders.
If a developer, former employee or agency registered the domain for you, confirm that your organisation still has access. Losing access to a domain can make it difficult to change hosting, renew the domain or recover the website. Domain ownership and account access should remain under the business’s control.
Option 1: Change the domain’s nameservers
Changing nameservers is usually the simplest option when your website, DNS and email will all be managed through the same hosting provider. Instead of editing several records manually, you tell the domain to use the hosting provider’s DNS system.
Your hosting provider may give you details similar to:
- Nameserver 1: a provider-specific server name
- Nameserver 2: a second provider-specific server name
The exact names are different for each provider, so copy them from your hosting account or support instructions. Do not guess them.
Steps for changing nameservers
- Log in to the account where your domain is registered.
- Open the domain management, DNS management or nameserver section.
- Choose the option to use custom nameservers.
- Replace the existing nameservers with the nameservers supplied by your hosting provider.
- Save the changes and check that they were entered correctly.
Changing nameservers transfers DNS management to the new provider. This means the new DNS zone must contain all the records your services need, including website records, email records and any verification records used by other services.
If your email is hosted separately, changing nameservers without recreating the email records can interrupt mail delivery. Before changing nameservers, ask the hosting or email provider which records must be added.
Option 2: Edit the DNS records manually
Manual DNS editing is useful when you want to keep DNS management at your current provider or when different services are managed by different companies. You connect only the records required for the website instead of moving the entire DNS zone.
The most common records are:
| Record | Purpose | Typical use |
|---|---|---|
| A | Points a domain or subdomain to an IPv4 address | Connecting the domain to a hosting server |
| AAAA | Points a domain or subdomain to an IPv6 address | Used when the host provides an IPv6 address |
| CNAME | Points one hostname to another hostname | Connecting a subdomain such as www to another hostname |
| MX | Identifies the servers that receive email | Directing business email to an email provider |
| TXT | Stores text used for verification and email security | Domain verification or sender policies |
Common website records
To connect the main domain, the hosting provider may ask you to create or update an A record. The host or name is often shown as @, meaning the root domain, and the value is the server’s IP address.
For the www version of the domain, the provider may recommend a CNAME record pointing to the main domain or to a specific hostname. Follow the provider’s instructions because hosting platforms can use different configurations.
Do not create conflicting records for the same hostname. For example, a hostname generally should not have both an A record and a CNAME record serving the same purpose. Remove or update the old website record only after confirming what it does.
Do not overlook email records
A common DNS mistake is connecting a website while accidentally breaking email. Website traffic and email use different records. An A record can send web visitors to your hosting server, while MX records determine where incoming email is delivered.
If your business uses an email service separate from your website hosting, do not delete its MX, TXT or other required records. These may be needed for incoming mail, sender authentication and protection against messages being marked as spam.
Before changing DNS, make a note of the existing records or export a copy if your DNS provider supports that option. If you are unsure which records belong to email, ask your email provider or hosting support team before saving changes.
DNS propagation: why changes are not immediate
After you update DNS, the change may not appear everywhere at the same time. DNS information is cached by internet service providers, browsers, devices and other systems. The time it takes for updated records to be recognised can vary.
During this period, some people may see the new website while others still see the old one. This does not necessarily mean that the change failed. Avoid repeatedly changing records while waiting, because additional edits can make troubleshooting more difficult.
You can test the domain from a different network, such as mobile data instead of office Wi-Fi, and check both the root domain and the www version. Also test important website pages, contact forms and business email.
A practical connection workflow
For a small business moving a website to new hosting, a careful workflow might look like this:
- Confirm that the domain account, hosting account and email accounts are accessible.
- Ask the new host for its recommended nameservers or DNS records.
- Record the current DNS settings, particularly MX and TXT records.
- Choose nameserver changes or manual record updates based on who should manage DNS.
- Apply the changes exactly as provided.
- Wait for DNS caches to update rather than making repeated unplanned edits.
- Test the website, www version, HTTPS, contact forms and email sending and receiving.
- Keep the old hosting active until the new website and essential services have been checked.
This approach reduces the risk of downtime and gives you a way to restore or correct a setting if something was entered incorrectly.
Common mistakes to avoid
- Using the wrong IP address: Copy the address from your hosting account, not from an old message or a different server.
- Editing the wrong domain: Check the spelling and domain extension before saving.
- Deleting email records: Website migration does not automatically mean email should move too.
- Forgetting www: Test both the root domain and the www hostname.
- Leaving duplicate or conflicting records: Old records can send visitors to the wrong server.
- Ignoring HTTPS: After the domain points to the new host, confirm that an SSL certificate is installed and the website loads securely.
- Losing account access: Keep registrar and hosting credentials secure and ensure renewal notices reach the business.
When should you ask for help?
DNS changes are often straightforward, but they can affect several connected services. Ask your hosting provider for help if the domain is registered elsewhere, email is hosted separately, the current DNS setup is unclear, or the website remains unavailable after the records have had time to update.
A good hosting support process should explain which record to change and why, rather than expecting you to understand every technical detail. This is particularly useful for businesses that want reliable websites and professional email without becoming server administrators.
The key takeaway
Pointing a domain to hosting means directing DNS to the server where your website lives. Nameserver changes are convenient when one provider manages the DNS, while manual A and CNAME records provide more control. Whichever method you choose, protect your MX and email-related records, keep ownership access under the business’s control, and test every important service after the change.
