Business Email Setup Checklist for a New Domain

Business Email Setup Checklist for a New Domain

Registering a new domain is only the first step towards having a professional business email address. The next step is making sure messages can be sent and received reliably, appear trustworthy to customers and remain under your organisation’s control.

An address such as [email protected] or [email protected] can be more suitable for business communication than a personal mailbox. However, a domain-based address does not automatically work as soon as the domain is registered. It needs an email service, correctly configured DNS records, secure user accounts and thorough testing.

This checklist is designed for Nigerian small businesses, entrepreneurs, creators and organisations setting up email for a new domain. It is also useful when moving email from a personal account, former provider or website developer.

1. Confirm that the domain is under your control

Before setting up email, verify that the domain is registered in the business’s name or under an account the business can access. The person managing your website may help with the setup, but essential digital assets should not depend entirely on a former employee, freelancer or agency.

Check the following:

  • The domain registrar account uses a business-controlled email address.
  • The organisation knows the registrar username and recovery method.
  • The registrant or account contact details are accurate.
  • Automatic renewal is enabled where appropriate, with a valid payment method.
  • More than one trusted person knows how to regain access.

A domain that expires can affect the website, email and other services connected to it. Record the renewal date in a calendar or business operations system rather than relying on one person’s memory.

2. Choose an email service that fits the organisation

Business email is usually provided through a hosting plan, a dedicated email hosting service or a productivity platform. The right option depends on the number of users, mailbox size, expected sending volume, collaboration requirements, support needs and budget.

A small business may only need a few reliable mailboxes, while a growing organisation may require shared calendars, larger storage, administrative controls and additional collaboration tools. Avoid choosing an expensive plan simply because it has more features. At the same time, do not select a plan that makes it difficult to create new staff accounts, manage storage or recover access later.

Before subscribing, confirm:

  • How many individual mailboxes are included.
  • Whether aliases such as sales@ or support@ are available.
  • How users access email on phones, computers and web browsers.
  • What support is available when sending or receiving fails.
  • Whether backups, spam filtering and account recovery are included or managed separately.

For many Nigerian businesses, practical support and straightforward administration can matter as much as technical features. A service that is easy to manage helps owners spend less time troubleshooting servers and more time serving customers.

3. Plan the addresses before creating accounts

Create a simple naming plan so addresses remain consistent as the organisation grows. Individual staff should normally have their own accounts, such as [email protected], rather than sharing one password.

Common role-based addresses include:

  • hello@ for general enquiries
  • sales@ for sales conversations
  • support@ for customer assistance
  • accounts@ for invoices and payment matters
  • careers@ for recruitment enquiries

Decide who receives each role-based address. It may be a separate mailbox, an alias, or a forwarding address. Avoid creating addresses that nobody monitors. An attractive contact address is unhelpful if customer messages disappear into an unattended inbox.

4. Connect the domain with the email service

The domain’s DNS settings tell the internet where to deliver email and which servers are authorised to send messages for the domain. Your email provider will normally give you the required records and values.

Important DNS records

  • MX records: Direct incoming mail to the correct email servers. Incorrect or missing MX records can prevent delivery.
  • SPF: Identifies approved servers that may send messages for the domain.
  • DKIM: Adds a verifiable signature to outgoing messages so receiving systems can check that they were authorised.
  • DMARC: Defines how receiving systems should handle messages that fail authentication and provides reporting options.

Copy these records carefully. A common problem is adding a record at the wrong DNS provider or creating multiple conflicting SPF records. If your website and domain are managed by different providers, first identify which service controls the domain’s active DNS zone.

DNS changes may not take effect immediately everywhere. Avoid repeatedly changing records while waiting, because this can make troubleshooting harder. Keep a record of the original settings and the final configuration.

5. Create secure user accounts

Each person should have an individual mailbox with a strong, unique password. Do not send a new password through an insecure group chat or reuse a password from social media, banking or another service.

Use these account practices:

  • Enable multi-factor authentication if the email service provides it.
  • Give administrative access only to people who need it.
  • Set up recovery details controlled by the organisation.
  • Remove or suspend accounts promptly when staff leave.
  • Review forwarding rules and connected applications.

Shared passwords make it difficult to know who accessed an account and create a serious risk when someone leaves. If several people need to handle the same messages, use a shared mailbox, delegation or a controlled forwarding arrangement instead.

6. Configure devices and applications carefully

Set up the mailbox on the webmail interface first. This helps confirm that the account and domain work before adding phones, desktop programs or third-party applications.

When configuring an email app, use the connection details supplied by the provider. Secure connection settings should be used for both incoming and outgoing mail. Check that the outgoing server requires authentication; otherwise, sending may fail or the account could be exposed to misuse.

Keep the business signature consistent across devices. It can include the person’s name, role, organisation, website and relevant contact details. Do not include unnecessary personal information or make the signature so large that it causes delivery and display problems.

7. Test the complete email workflow

Do not consider the setup complete after one successful test. Test the journey in both directions using different providers where possible.

  1. Send a message from the new domain to an external address.
  2. Reply from that external address to the business mailbox.
  3. Send between two addresses on the new domain.
  4. Test delivery to a phone and a desktop or webmail client.
  5. Reply to a message and confirm that the correct address is used.
  6. Send a message with a normal attachment and check how it is received.
  7. Review spam and junk folders if a message does not appear.

Check the sender name, reply-to address, signature, timestamps and formatting. A message that arrives in spam may indicate an authentication or reputation problem, so it should not be ignored simply because delivery technically occurred.

8. Protect the domain after setup

Email security is an ongoing responsibility. Keep the domain registrar, hosting account and email administration account protected with strong passwords and multi-factor authentication where available.

Be cautious of messages requesting urgent password changes, payment updates or domain transfers. Attackers often target email because access to one mailbox can expose invoices, customer conversations, password-reset links and other business information.

Review administrator accounts, forwarding rules, DNS records and unused mailboxes periodically. Maintain a clear offboarding process so former users cannot continue accessing company email.

9. Keep an ownership and recovery record

Store the following information securely:

  • Registrar and email provider details
  • Domain renewal date
  • Names of authorised administrators
  • Recovery methods and emergency contacts
  • DNS records and the reason each one exists
  • List of active mailboxes, aliases and forwarding rules

This record is especially valuable when a business changes its website developer, staff or hosting provider. It reduces the risk of losing access and makes future migration more orderly.

A practical completion test

Before publishing the new address on a website, social media profile, invoice or business card, confirm that the domain is controlled by the organisation, the correct email plan is active, DNS authentication is configured, accounts are secure and messages work in both directions.

A professional business email setup is not just about replacing a personal address. It connects domain ownership, reliable delivery, account security and customer experience. Set it up carefully at the beginning, document the configuration and review it regularly. That small amount of preparation can prevent missed enquiries, confusing communication and avoidable loss of access later.

How to Troubleshoot Email Delivery Problems

How to Troubleshoot Email Delivery Problems

Email problems can quickly become business problems. A customer may not receive a quotation, a supplier may miss an important update, or a password-reset message may never arrive. When email is not being delivered, the cause may be anything from a full mailbox to an incorrect DNS record or a message being filtered as spam.

The most effective approach is to avoid changing several settings at once. Start by identifying exactly what failed, then test the likely cause in a logical order. This guide is designed for small businesses, entrepreneurs and organisations using business email with their own domain.

First, identify the type of delivery problem

“My email is not working” can describe several different situations. The solution depends on which one you are experiencing.

  • Sending fails immediately: Your email program may show an error, or the message may remain in the outbox.
  • The message bounces: You receive an automated delivery failure notice.
  • The message appears sent but never arrives: It may be delayed, rejected later or placed in the recipient’s spam folder.
  • You receive email but cannot send: The outgoing mail settings or authentication may be incorrect.
  • You can send email but cannot receive it: The domain’s receiving records, mailbox configuration or storage limit may be involved.
  • Only one recipient has a problem: The issue may be specific to that recipient’s mailbox or email provider.

Record the sender address, recipient address, approximate time, subject and exact error message. These details are often more useful than a general description of the problem.

Read the bounce message carefully

A bounce message is not just an annoyance; it usually provides a diagnostic clue. Look for phrases such as “mailbox full”, “user unknown”, “message rejected”, “authentication required”, “connection timed out” or “message too large”.

Some bounce messages are temporary. A busy receiving server, a short network interruption or a temporary reputation check may cause delivery to be retried automatically. Others are permanent, such as sending to an address that does not exist.

Do not repeatedly resend the same message without understanding the error. Repeated attempts can create confusion and may make filtering more likely. If the notice contains a technical code, keep it available when contacting your hosting or email support provider.

Check the simple causes before changing technical settings

Many delivery issues have a straightforward explanation. Work through these checks first:

  • Confirm that the recipient’s address is spelled correctly.
  • Send a short test message without attachments or links.
  • Check whether your mailbox is full or has reached its storage limit.
  • Review the Sent, Drafts and Outbox folders for messages stuck in a queue.
  • Sign in to webmail, if available, to determine whether the problem is limited to your phone or email application.
  • Check the recipient’s spam, junk or promotions folders.
  • Ask the recipient to add your address to their contacts or approved senders.
  • Try sending to a second recipient to see whether the issue affects one address or many.

This test separates an account or domain problem from a device-specific problem. If webmail works but your phone does not, review the phone’s account settings rather than changing your domain records.

Review your outgoing mail settings

Email applications use separate settings for receiving and sending messages. A device can sometimes download incoming mail correctly while failing to connect to the outgoing mail server.

Check that the outgoing server name, connection security and port match the settings supplied by your email hosting provider. The option requiring authentication for outgoing mail should normally be enabled, using the full email address and its password where required.

Avoid copying settings from an unrelated account. The correct configuration for a personal email provider may not be correct for a domain-based business mailbox. If you recently changed your password, update it on every phone, computer or application connected to the account.

If an account has been configured on several devices, temporarily test one device at a time. This can reveal an old device repeatedly attempting to connect with an outdated password.

Check the domain’s DNS records

When a business uses an address such as [email protected], the domain’s DNS records help other mail servers find where messages should be delivered. Incorrect or missing records can prevent incoming email from reaching the right service.

The most important record for receiving mail is the MX record. It identifies the mail server responsible for the domain. If the domain was recently moved, the MX record may still point to an old provider, or it may have been accidentally removed.

Other records help receiving providers verify that messages sent from your domain are legitimate:

  • SPF: Identifies the servers allowed to send email for your domain.
  • DKIM: Adds a digital signature that helps verify messages have not been altered and came from an authorised system.
  • DMARC: Tells receiving providers how to handle messages that fail authentication checks and provides reporting options.

These records must be entered accurately and should not be duplicated without a clear reason. For example, publishing multiple separate SPF records can cause validation problems. DNS changes may also take time to appear across different networks, so avoid repeatedly replacing records while they are propagating.

If you are unsure which records your email service requires, ask your hosting provider to review the domain configuration. This is safer than guessing, particularly when the same domain is used for the website and email.

Investigate spam and reputation issues

A message that leaves your mailbox successfully can still be filtered by the recipient’s provider. Spam filtering may consider the sending domain, server reputation, message content, links, attachments and authentication results.

Start with a controlled test: send a plain-text message with a descriptive subject, a normal signature and no attachment or shortened link. If that arrives but a marketing-style message does not, compare the content and sending method.

Also review whether your account may have been compromised. Unexpected sent messages, unfamiliar login alerts or a sudden increase in bounced messages can indicate that someone else has accessed the mailbox. Change the password to a strong, unique one and contact your email provider for help reviewing the account. Enable additional sign-in protection when it is available.

Do not respond to requests for passwords or payment details merely because they appear to come from an email provider. Use the provider’s known website or support channel instead.

Reduce problems caused by attachments and message size

Large attachments are a common reason for delayed or rejected messages. The sender’s mailbox may allow a file that the recipient’s provider does not. Multiple images, videos and scanned documents can also make a message unexpectedly large.

For important documents, consider sending a secure sharing link through a service you trust, with appropriate access controls. If an attachment is necessary, compress files where practical and send several smaller messages only when that will not create confusion. Never assume that a message was delivered simply because it left the Outbox.

Use a repeatable troubleshooting workflow

A simple workflow helps a small business resolve problems without losing time:

  1. Capture the exact error or bounce message.
  2. Confirm the addresses and test with a short message.
  3. Check webmail, mailbox storage and the Outbox.
  4. Test another recipient and another device.
  5. Review outgoing server settings and password status.
  6. Ask the email host to verify MX, SPF, DKIM and DMARC records.
  7. Check for spam filtering, account compromise or unusual sending activity.
  8. Retest and document the final change.

For example, if a Nigerian business can send mail to one customer but not another, the domain may be working correctly. The next step is to examine the bounce notice and ask the recipient to check filtering. If nobody can receive messages sent to the business domain after a website or hosting change, the MX records deserve attention.

When to ask for technical support

Contact your hosting or email provider when the error is unclear, several users are affected, DNS records need changing, messages are being rejected consistently, or you suspect an account has been compromised. Provide the domain, affected addresses, error text, time of the failed attempt and the troubleshooting steps already completed.

Business email should be managed as part of the organisation’s wider online presence. Keep domain ownership and renewal access under the business’s control, maintain accurate account details, use strong passwords and ensure more than one responsible person knows how to reach the provider.

The fastest solution is usually not a random setting change. It is a clear diagnosis: determine whether the failure is caused by the recipient, the mailbox, the device, the email application, the domain’s DNS records or message filtering. Once that distinction is clear, the right fix becomes much easier to apply and verify.

How to Point DNS Records to Your Hosting Account

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

  1. Log in to the account where your domain is registered.
  2. Open the domain management, DNS management or nameserver section.
  3. Choose the option to use custom nameservers.
  4. Replace the existing nameservers with the nameservers supplied by your hosting provider.
  5. 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:

  1. Confirm that the domain account, hosting account and email accounts are accessible.
  2. Ask the new host for its recommended nameservers or DNS records.
  3. Record the current DNS settings, particularly MX and TXT records.
  4. Choose nameserver changes or manual record updates based on who should manage DNS.
  5. Apply the changes exactly as provided.
  6. Wait for DNS caches to update rather than making repeated unplanned edits.
  7. Test the website, www version, HTTPS, contact forms and email sending and receiving.
  8. 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.

How to Connect a Domain to Your Web Hosting Account

How to Connect a Domain to Your Web Hosting Account

Buying a domain name and buying web hosting are usually two separate steps. Your domain is the address people type into a browser, while hosting is the server space where your website files, database and email services may be stored. To make the website appear when someone visits the domain, you must connect the two.

This process is often called pointing a domain to hosting. It does not usually require advanced technical knowledge, but the correct method depends on where your domain was registered and how your hosting provider has configured its services.

For Nigerian businesses, creators and organisations, getting this connection right is important. A professional domain and dependable website can give customers a stable place to learn about your services, contact you or buy from you, rather than relying only on social media profiles.

What you need before starting

Have the following details available:

  • Access to the account where your domain is registered.
  • Access to your web hosting account or welcome email.
  • The hosting provider’s nameservers, or the hosting account’s IP address.
  • The domain name you want to connect.
  • Any existing email or website DNS details that must remain active.

Your hosting provider normally supplies the nameservers in the account dashboard or setup instructions. They may look similar to ns1.example-host.com and ns2.example-host.com. Do not copy these sample values; use the exact nameservers provided for your hosting account.

Method 1: Change the domain’s nameservers

Changing nameservers is usually the simplest option when your domain and hosting are managed by different companies. It tells the internet to use your hosting provider’s DNS system for the domain.

Step 1: Find the correct nameservers

Log in to your hosting account and look for a section such as Account Information, DNS details, Nameservers or New account information. Copy each nameserver carefully. A hosting provider may give you two or more nameservers.

Step 2: Open your domain registrar

Sign in to the company where you registered the domain. Look for options such as Manage Domain, DNS management, Nameservers or Change nameservers.

Replace the existing nameservers with the ones supplied by your hosting provider. Save the change. Avoid adding extra spaces or changing the spelling.

Step 3: Wait for the DNS change to take effect

DNS changes are not always visible everywhere immediately. Different internet providers, devices and locations may continue showing the previous information for a while because DNS results are cached.

During this period, your website may appear from one connection but not another. That does not necessarily mean the setup has failed. Allow time for the updated DNS information to become available across the internet.

Method 2: Point the domain using DNS records

You may prefer to keep DNS management at your domain registrar, especially if the domain already has important email or other services connected to it. In this case, you normally update specific DNS records instead of changing the nameservers.

The A record

An A record connects the domain to an IPv4 address. Your hosting provider will give you the correct server IP address. The main domain, sometimes shown as @, is usually pointed to this address.

For example, the record may be structured like this:

Type Name Value
A @ Your hosting server IP address

The IP address in this example is only a placeholder. Use the address assigned to your hosting account.

The www record

Many websites also use the www version of the domain. A CNAME record can commonly point www to the main domain, although your hosting provider may recommend another arrangement.

Type Name Value
CNAME www Your main domain name

DNS control panels differ. Some automatically add the domain name after you enter a short value, while others expect a complete domain name. Follow the instructions shown by your registrar.

Protect existing email and other services

Before changing DNS records, check whether the domain is already used for business email. Email depends on records such as MX, SPF and DKIM records. Replacing nameservers without recreating the required email records can interrupt mail delivery.

This is particularly important when a business uses a domain-based address such as [email protected] or [email protected]. If you are unsure which records are required, record the existing DNS settings first and ask your hosting or email provider for guidance.

The same caution applies to payment services, verification records, subdomains and external tools. A domain may support more than just a website.

Add the domain inside your hosting account

Some hosting accounts create the website automatically when the domain is purchased together with the hosting plan. If the domain was registered elsewhere, you may still need to add it inside the hosting control panel.

Look for an option such as Add Domain, Domains or Create Website. Enter the domain exactly as registered. Depending on the hosting setup, the system may ask you to choose a document root, create a folder or assign the domain to an existing website.

For a new website, make sure the domain points to the correct folder. If it points to the wrong document root, visitors may see an empty page, a default hosting page or another website in your account.

How to check whether the connection works

After updating nameservers or DNS records, use this simple verification process:

  1. Open the domain without adding a page name, such as yourdomain.com.
  2. Try the www version if you plan to support it.
  3. Check the domain from a mobile connection as well as Wi-Fi.
  4. Confirm that the correct website loads rather than a default or unrelated page.
  5. Check whether the website uses HTTPS and displays a secure connection in the browser.
  6. Test important pages, contact forms and links.

A new website may initially show a temporary page while the hosting account is being prepared. If the domain still does not work after DNS information has had time to update, review the nameservers, IP address, domain status and hosting account configuration.

Common problems and practical fixes

The domain shows an error or cannot be reached

Check that the domain has not expired, the nameservers are typed correctly and the domain has been added to the hosting account. Also confirm that the hosting account is active and that the DNS record points to the correct server.

The website shows a default hosting page

This usually means the domain is reaching the server but has not been connected to the correct website folder. Review the domain’s document root or ask the hosting provider to confirm the account configuration.

The website works without www but not with www

The main domain and the www version may use separate records. Check whether the required CNAME or A record exists and whether both versions have been added to the hosting account.

Email stopped working after the change

Review the MX records and the email provider’s required DNS records. If nameservers were changed, those records may need to be recreated in the new DNS zone. Avoid repeatedly changing records without first keeping a copy of the original settings.

HTTPS is not active

DNS must point to the correct hosting account before an SSL certificate can normally be issued for the domain. After the domain resolves correctly, use the hosting control panel’s SSL settings or contact support. Remember to update website links and settings so visitors are directed to the HTTPS version.

Keep control of your domain

Whoever controls the domain registrar account can usually manage important settings, including renewals and nameservers. A business should keep accurate ownership information, use a strong unique password and enable available account security controls.

Do not allow a domain to remain registered only through an unknown third party, former employee or developer without retaining access. Keep renewal notices active and document where the domain, hosting, email and website credentials are stored.

A simple connection workflow

For most small businesses, the safest workflow is:

  1. Confirm where the domain is registered.
  2. Confirm where the website will be hosted.
  3. Copy the correct nameservers or DNS values from the hosting provider.
  4. Check existing email and other DNS records.
  5. Update the domain settings.
  6. Add the domain to the hosting account if required.
  7. Wait for DNS changes to become visible.
  8. Test the website, HTTPS, www version and business email.

The key is to change only what is necessary. If you are moving both a website and business email, plan the DNS changes instead of treating the domain as though it only controls the website.

Connecting a domain to hosting is mainly a matter of directing the domain to the correct server and checking that every related service still works. Once the setup is complete, keep your domain access secure, monitor renewals and maintain reliable hosting, backups, HTTPS and website support so your online presence remains a dependable business asset.

A Beginner’s Guide to Nameservers

A Beginner’s Guide to Nameservers

When someone types your domain name into a browser, how does the browser know which server contains your website? The answer involves nameservers.

Nameservers work behind the scenes to connect a domain, such as yourbusiness.com or a Nigerian domain, to the correct hosting service. You do not need to become a DNS specialist to use them, but understanding the basics can help you launch a website, move hosting providers and avoid common setup problems.

This guide explains what nameservers are, how they differ from domain names and hosting, and what to check before changing them.

What are nameservers?

Nameservers are specialised servers that tell the internet where to find the DNS records for a domain name. DNS stands for Domain Name System. It translates human-readable domain names into the technical information computers use to locate websites and other online services.

For example, when a visitor enters example.com in a browser, the domain’s nameservers help direct the request to the DNS system responsible for that domain. The DNS records then provide information such as:

  • Which server hosts the website
  • Where email for the domain should be delivered
  • Which services are authorised to send email
  • Whether a subdomain should point to another service

A simple way to think about nameservers is to treat them like a signpost. Your domain is the address people remember, while the nameservers point internet services towards the records that explain where the website and email are located.

Nameservers, domains and hosting: what is the difference?

These three terms are connected, but they are not the same.

Domain name

A domain is the address people use to reach your website. It might be your company name, a personal brand or an organisation’s name. Registering a domain gives you the right to use that address for the registration period, provided it is renewed and kept in good standing.

Web hosting

Web hosting is the service that stores your website’s files and makes them available online. A hosting account may contain your website files, databases, SSL configuration, backups and other resources.

Nameservers

Nameservers connect the domain’s DNS management to the DNS service that contains its records. If your domain uses the nameservers provided by your hosting company, that hosting company will usually manage the main DNS zone for the domain.

Domain registration and hosting can be purchased from the same provider or from separate providers. The important issue is that the domain points to the correct DNS service and that you retain access to the accounts controlling it.

What do nameservers usually look like?

Nameservers are normally written as hostnames, such as:

  • ns1.examplehost.com
  • ns2.examplehost.com

Your hosting provider supplies the exact nameservers to use. They may contain the provider’s brand, or they may use a domain created specifically for its DNS service. Nameservers are not the same as IP addresses, although the nameserver system eventually helps direct requests to IP addresses and other DNS destinations.

Most hosting services provide at least two nameservers. Using more than one helps provide continuity if one nameserver is temporarily unavailable, although the exact design depends on the provider.

When do you need to change nameservers?

You may need to update nameservers in several situations:

  • You registered your domain with one company and bought hosting from another.
  • You are moving an existing website to a new hosting provider.
  • A developer or agency originally configured the domain and you want to manage it yourself.
  • You are setting up a new website for your business or organisation.
  • Your provider has asked you to move to new DNS servers.

For a new domain and a new hosting account, the process is usually straightforward: obtain the correct nameservers from the hosting provider, enter them at the domain registrar and wait for the DNS changes to take effect.

How to update nameservers safely

1. Confirm where the domain is registered

First, identify the company where the domain was registered. This may be different from the company hosting the website. You will need access to the domain registrar account, not just the hosting control panel.

If a former employee, developer or agency registered the domain, make sure your organisation has the login details and that the registration information is accurate. Losing access to a domain can create serious problems for a website, business email and customer communications.

2. Obtain the correct nameservers

Ask your hosting provider for the exact nameserver addresses for your hosting plan. Copy them carefully. A small spelling error can prevent the domain from resolving correctly.

Do not guess nameservers based on another customer’s website or an old setup guide. Providers can change their DNS arrangements, and different hosting services may use different nameservers.

3. Record the existing DNS settings

Before making changes, save a copy or screenshot of the current DNS records. This is particularly important if the domain already has business email, verification records or subdomains.

Changing nameservers can move control of the domain’s DNS records from one provider to another. If the new DNS zone does not include the necessary email records, website email may stop working even if the website itself loads normally.

4. Enter the new nameservers at the registrar

Log in to the domain registrar, find the domain management or nameserver section, and replace the existing nameservers with the new ones. Save the change and check that the values displayed afterwards are correct.

Some registrars use labels such as “Custom nameservers”, “Use my own DNS” or “Change DNS servers”. The wording varies, but the purpose is the same.

5. Allow time for the change

Nameserver changes are not always visible everywhere immediately. Different internet providers, devices and DNS resolvers may temporarily hold older information in their cache. As a result, one person may see the new website while another still sees the old one.

Avoid repeatedly changing the nameservers because the website does not appear instantly. Check the settings first, then allow the DNS change time to spread. If the problem continues, contact the domain or hosting provider and provide the domain name and the exact nameservers you entered.

Nameservers and business email

A common mistake is to focus only on the website during a hosting change. Your domain may also support addresses such as [email protected] or [email protected].

Email delivery depends mainly on DNS records, including MX records. If you change nameservers and the new DNS zone does not contain the correct MX records, incoming email may be delayed or delivered incorrectly. Other records can also matter, including SPF, DKIM and DMARC records used to help authenticate outgoing email.

Before changing nameservers, list the services connected to the domain:

  • Website hosting
  • Business email
  • Payment or booking tools
  • Subdomains
  • Website verification services
  • Marketing and email delivery platforms

This short inventory can prevent an unexpected interruption. If you are unsure which records are needed, ask your current email provider or hosting support team before making the change.

Common nameserver problems

The domain shows an error page

This may happen if the nameservers are incorrect, the DNS records are missing or the hosting account is not configured for the domain. Check the spelling and confirm that the domain has been added to the correct hosting account.

The website works, but email has stopped

This often points to missing or incorrect mail records in the new DNS zone. Restore the required email records or ask the email provider for the correct settings.

Only some people see the new website

This can be normal while DNS information is being refreshed. Check the configuration before assuming the change failed.

The domain is not under your control

If you cannot access the registrar account, work on recovering ownership and account access before attempting technical changes. A business should keep control of its domain, hosting and email rather than relying entirely on a former employee or third party.

A practical example

Imagine a Nigerian business has its domain registered with one company but decides to host a WordPress website with a new provider. The business receives two nameservers from the new hosting company and updates them at the registrar.

Before the change, the business records its existing email and verification records. After the change, it confirms that the domain points to the new website and that messages to its domain-based email addresses are still arriving. If the website loads but email does not, the next step is to check the MX and related mail records rather than changing the nameservers again.

This approach is especially useful for small businesses and entrepreneurs who need a reliable website without turning every technical change into a major disruption.

What to remember

Nameservers are the connection between your domain and the DNS records that direct website, email and other online services. You usually change them when setting up hosting or moving a website, but the change should be planned carefully.

Keep access to your domain registrar, record existing DNS settings, confirm the correct nameservers with your provider and check both your website and business email afterwards. With those precautions, nameservers become a manageable part of running a professional online presence rather than a confusing technical obstacle.

What Is DNS and Why Does It Matter?

What Is DNS and Why Does It Matter?

When someone types your business domain into a browser, how does their device find the correct website? The answer is DNS, or the Domain Name System.

DNS connects a human-friendly domain such as yourbusiness.com to the technical destinations used by websites, email services and other online tools. You usually do not see DNS working, but a problem with it can make a website unavailable, stop business email from arriving or send visitors to the wrong service.

For a Nigerian business, creator or organisation building a dependable online presence, understanding the basics of DNS can help you protect your domain, troubleshoot problems and avoid losing access to important digital assets.

DNS explained in simple terms

Computers communicate using numerical Internet Protocol (IP) addresses. People, however, find names much easier to remember than strings of numbers. DNS acts like a directory that helps translate a domain name into the destination a device needs to contact.

For example, when a customer enters your domain in a browser, a DNS lookup helps identify the server hosting your website. The browser can then request the website’s files and display the page.

The same domain can also use DNS to direct other services. Your website may point to one provider, while your domain-based email uses another. This is why changing a website host does not always require moving business email, provided the relevant DNS records are preserved and updated correctly.

What happens when someone visits a website?

A simplified version of the process looks like this:

  1. The visitor enters a domain name in a browser or follows a link.
  2. The device asks a DNS resolver for the domain’s current records.
  3. The resolver finds the authoritative DNS information for that domain.
  4. The browser receives the destination, such as a web server’s IP address.
  5. The browser connects to the server and requests the website.

Several systems may cache DNS information temporarily to make repeat lookups faster. This is useful for performance, but it also explains why a DNS change may not appear everywhere immediately. Different networks and devices can retain the previous information until their cached data expires.

Important types of DNS records

DNS records tell the Internet what different services should do with your domain. You do not need to memorise every technical detail, but knowing the main record types makes hosting and email conversations much clearer.

<

Record Common purpose
A Points a domain or subdomain to an IPv4 address, often for a website.
AAAA Points a domain or subdomain to an IPv6 address.
CNAME Points one hostname to another hostname, often for a subdomain or external service.
MX Identifies the mail servers responsible for receiving email for a domain.
TXT Stores text used for verification and email-authentication policies, among other purposes.
NS Identifies the name servers that provide authoritative DNS information for the domain.

These records work together. A website may need an A record, while professional email commonly depends on correct MX and email-authentication records. Removing or replacing records without understanding their purpose can interrupt one service while fixing another.

DNS, a domain and hosting are not the same thing

These terms are often confused:

  • A domain name is the memorable address people use to reach you, such as yourbusiness.ng or yourbusiness.com.
  • Web hosting provides server space and resources for your website’s files, database and applications.
  • DNS directs requests for your domain to the appropriate website, email provider or other online service.

They can be purchased from the same company or managed through separate providers. The important issue is not whether everything is with one provider; it is whether your organisation knows who controls each account and can access the domain and DNS settings.

A website developer may set up DNS during launch, but the business should retain access to its domain registrar account and understand where DNS is managed. This protects the business if a developer, employee or service relationship changes.

Why DNS matters to a business

It keeps your website reachable

If the records directing your domain to your hosting server are wrong, visitors may see an error or an unrelated page instead of your website. For a business that relies on enquiries, bookings or online sales, even a basic DNS mistake can create missed opportunities.

It helps business email work

Website hosting and email hosting are separate functions. MX records tell other mail systems where to deliver messages sent to addresses such as [email protected]. Incorrect MX records can cause mail delivery failures or route messages to the wrong provider.

It supports trust and security

DNS is involved in domain verification and email authentication. TXT records may be used to confirm ownership of a service or publish policies that help receiving mail systems assess whether messages are legitimately sent for your domain. DNS is not a complete security solution, but careful management reduces avoidable risks.

It affects changes and migrations

When moving a website to a new host, DNS is often the final connection between the domain and the new server. Planning the records in advance can reduce disruption. A migration should account for website records, email records, subdomains, verification records and any other service connected to the domain.

A practical DNS change workflow

Before changing DNS, use this simple process:

  1. Identify the purpose. Decide whether you are connecting a website, setting up email, verifying a service or creating a subdomain.
  2. Record the current settings. Keep a copy or screenshot of existing records before editing them. Include the record type, name, value and any relevant timing setting.
  3. Confirm the destination. Obtain the exact values from your hosting or service provider. Do not guess an IP address or mail-server name.
  4. Change only what is necessary. Avoid deleting unrelated records, especially MX, TXT or verification records.
  5. Test from more than one connection. Check the website and send or receive test email. A mobile network and a fixed connection may update at different times.
  6. Keep access and documentation. Store the registrar and DNS-management details securely so another authorised person can maintain the setup.

For example, if a business moves its website to new hosting but keeps its existing email provider, it should update the website-related record while preserving the MX records and relevant email-authentication records. Changing every record at once could take the website online while silently breaking email.

Common DNS problems and what they usually mean

  • The domain shows an old website: the DNS change may not have reached every network yet, or the old record may still exist.
  • The domain does not load: the website record may be missing, incorrect or pointing to a server that is not configured for the domain.
  • Email stops arriving after a website change: MX records may have been removed or replaced.
  • A service cannot verify the domain: a TXT or CNAME record may have the wrong name, value or formatting.
  • Only one subdomain fails: that hostname may need its own record even though the main domain works.

DNS issues can resemble hosting, website or email problems. If the symptoms are unclear, checking the records and contacting the provider that manages DNS is often safer than repeatedly changing settings.

Good DNS habits for Nigerian businesses

Keep the domain registration details accurate, monitor renewal dates and use a strong, unique password for the registrar account. Enable multi-factor authentication when available. Limit DNS access to trusted people and avoid giving permanent control to a contractor who no longer needs it.

It is also worth documenting which provider manages the domain, website hosting, email and DNS. This is particularly useful for small teams where one person may handle several online responsibilities. A reliable hosting and support partner can manage the technical work, but the business should still retain ownership and access to its core accounts.

Visitors may discover a business through social media, but a domain gives the organisation a stable digital home. When that domain leads to a secure website and dependable domain-based email, it supports a more consistent customer experience.

The practical takeaway

DNS is the connection layer between your domain and the online services behind it. You do not need to become a server administrator, but you should know who controls your DNS, what the main records do and which services depend on them.

Before making a change, document the current setup, update only the required record and test both your website and email. That small amount of care can prevent a confusing technical issue from becoming a lost enquiry, missed message or damaged customer experience.

Can You Buy Hosting Without Buying a Domain?

Yes, you can buy web hosting without buying a domain name. Hosting and domain registration are separate services, even though they are commonly purchased together when launching a website.

This flexibility can be useful for business owners, SMEs, churches, law firms and other organisations that want to prepare a website before choosing a permanent web address. You may also already own a domain registered with another provider and only need hosting for your website.

Understanding the difference between these services will help you avoid unnecessary costs and make setup easier.

What is web hosting?

Web hosting is the service that stores your website’s files and makes them available online. These files may include your website pages, images, databases, videos and application code.

When someone visits your website, the hosting server delivers the relevant files to their browser. Hosting can come in different forms, including shared hosting, VPS hosting and cloud hosting. The right option depends on the size of your website, expected traffic, technical requirements and available budget.

Without hosting, your website files do not have a reliable place to operate online. You may have designed a website, but visitors will not be able to access it through the internet until it is placed on a suitable server.

What is a domain name?

A domain name is the address people type into a browser to find your website. It is the readable alternative to using a numerical IP address.

For example, a business might use a domain based on its name, while a church, law firm or professional organisation may choose an address that reflects its identity. A domain can help people remember your website and can support a more professional online presence.

Registering a domain gives you the right to use that web address for the registration period, subject to the terms of the domain extension and registrar. It does not automatically provide storage for your website files. That is the role of hosting.

Can hosting work without a domain?

Yes. Many hosting providers allow you to purchase a hosting plan without registering a new domain. You may be given a temporary address, a server address or another access method for viewing and managing your website.

This allows you to:

  • Upload website files before selecting a permanent domain.
  • Build and test a website privately or on a temporary address.
  • Use a domain registered with a different provider.
  • Move an existing website to new hosting without transferring the domain.
  • Set up a website project while your preferred domain choice is still being decided.

The exact temporary access method depends on the hosting provider. It may not be suitable as a permanent public address, but it can be useful during development and migration.

When might you buy hosting first?

1. You are still choosing a domain name

A suitable domain name may require careful thought. You may want to confirm your business name, review available domain extensions or agree on a name with business partners before registering it.

Buying hosting first can allow your website work to begin while that decision is being finalised. However, if you have already found a valuable and suitable domain name, registering it promptly may reduce the risk of someone else taking it.

2. You already own a domain

Many website owners purchase their domain and hosting from different companies. For example, you may have registered your domain previously but now need more suitable hosting for a new website.

You do not need to purchase the domain again. Instead, you can connect the existing domain to your new hosting account by updating its DNS settings or nameservers.

3. You are moving an existing website

When transferring a website to a new hosting provider, the domain can remain with its current registrar. The important task is to point the domain to the new server after the website files and databases have been moved.

Keeping the domain and hosting separate can also make future changes easier because you are not required to transfer both services whenever you change hosting.

4. You are developing a website before launch

A designer or developer may need hosting to build and test a website before the organisation is ready to publish it. A temporary address can support this stage, although access controls should be considered if the website contains confidential information or unfinished content.

How do you connect a domain to hosting?

After purchasing hosting, you generally connect your domain by changing its DNS configuration. The hosting provider will normally supply the nameservers or DNS records required for the connection.

The usual process is:

  1. Purchase or choose a hosting plan.
  2. Obtain the hosting account details and required nameservers or DNS records.
  3. Log in to the account where your domain is registered.
  4. Replace or update the relevant DNS settings.
  5. Upload your website files or install your chosen website platform.
  6. Test the domain and confirm that the website loads correctly.

DNS changes may not appear everywhere immediately. The time can vary depending on the records involved, caching and the providers handling the domain and hosting. During this period, some visitors may see the old destination while others see the new one.

What happens to email if you change hosting?

Business email often depends on DNS records, so changing hosting should be planned carefully. If your organisation uses email addresses connected to its domain, do not remove or replace mail-related records without knowing how your email service is configured.

A website can be moved to new hosting while email continues to operate through a separate email provider. The key is to update only the records required for the website and preserve the records needed for mail delivery.

Before making DNS changes, record your existing settings and confirm which service handles your email. This is especially important for organisations such as law firms and businesses that rely on consistent communication with clients.

Is it better to buy hosting and a domain together?

For many beginners, purchasing both services from one provider is convenient. One account may make billing, support and initial setup easier. Some providers also offer domain registration during the hosting order process.

However, buying them together is not required. Separate providers may suit you if:

  • You already have a domain.
  • Your preferred domain registrar does not provide the hosting features you need.
  • You want to keep your domain independent from your hosting provider.
  • You are moving a website and want to avoid changing several services at once.

When comparing options, look beyond the introductory offer. Consider renewal terms, storage, backups, support, security features, control panel access and the hosting resources your website needs. The lowest initial cost is not always the lowest overall cost or the best fit for a business website.

What can you do before buying a domain?

While using temporary hosting access, you can prepare much of your website. You may create page content, upload images, configure a content management system, test forms and organise your navigation.

It is still wise to delay public promotion until you have a permanent domain and have tested the complete website. A temporary address may be difficult to remember and may not represent your brand professionally.

You should also confirm that your final domain can be connected easily to the hosting account. Check whether the host supports the technology your website requires, such as databases, programming languages, content management systems or specific server configurations.

Do you need a domain for every website?

A domain is not required for every type of online project. A website can be tested on a temporary address, hosted within an internal network or accessed through a platform-provided address.

For a public-facing organisation, however, a custom domain is usually the more practical choice. It gives visitors a clear address, supports brand recognition and can make it easier to create professional domain-based email addresses. The domain should be chosen carefully because changing it later can affect links, search visibility, printed materials and customer awareness.

Final considerations before you buy hosting

Before ordering, identify what you need now and what you may need later. A small informational website may have different requirements from a busy online shop, a client portal or a website with custom applications.

  • Decide whether you need a domain immediately or already own one.
  • Confirm how you will access the hosting account without a domain.
  • Check how the provider connects external domains.
  • Review backup, security and support options.
  • Protect existing email and DNS settings during any change.
  • Choose hosting that can support your website’s expected requirements.

Sonhosting can help simplify the process of choosing hosting and setting up the tools needed for a website. Whether you are preparing a new website or moving an existing domain, understanding how hosting and domains work separately makes it easier to plan with confidence.

In short, you can buy hosting without buying a domain. You can use temporary access while building your website, connect a domain registered elsewhere or purchase a domain later. The best approach depends on your project timeline, technical needs and how quickly you are ready to establish a permanent online identity.

Your Cart

©2018 - currentyear Sonhosting • By Digital Nigeria - RC 7487481
All Rights Reserved
Powered by ShootOut Now Services