A domain is your business’s public web address, DNS directs visitors and email to the right services, and web hosting provides the environment where website files run. Before you register, launch or move a site, make sure the business controls the domain account, someone knows which DNS records serve the website and email, and renewal, backup and support responsibilities are written down.
This checklist is designed to prevent avoidable confusion during setup or migration. You do not have to buy your domain and hosting from the same provider, but you do need a clear record of who manages each part.
1. Keep the domain under business control
Record the domain registrar, the registrant name, the renewal date and the email address used for important notices. Use a business-controlled account that will remain accessible if a staff member or agency changes. Keep the account recovery details somewhere the authorised business owners can find them.
If a web agency or supplier helps manage the domain, agree in writing who can access the account, who approves changes and how the business can regain control. ICANN explains that registrants manage domain settings through their registrar and can access information about registration, management, transfer and renewal processes in its registrant guide.
2. Put renewal on a calendar
A domain registration lasts for a set term; it is not a permanent purchase. Check your registrar’s renewal terms, payment method and notice address, then add an internal reminder well before the listed expiry date. Do not rely only on a notice reaching an inbox that might itself depend on the domain.
ICANN advises registrants of generic top-level domains to renew before expiry, follow their registrar’s terms and keep contact details current so they receive notices. Rules can vary for country-code domains and by registrar, so check the terms for the exact domain you use. See ICANN’s domain-renewal guidance.
3. Write down the DNS and hosting map
DNS is the system that translates a domain name into the information computers use to reach online services. Before making a change, note who controls the DNS zone, where the nameservers point and which records connect the domain to the website, email and any subdomains. Cloudflare’s DNS overview explains how domain names are resolved to IP addresses.
Keep a copy of the current DNS records before a migration. This gives your developer or hosting provider a reference point and makes it easier to restore a record if a change affects a live service.
4. Choose hosting around the actual workload
List what the business needs to run: a brochure website, an online store, a booking system, business email, or a mix. Ask the provider about storage and resource limits, supported software, backups and restore help, security responsibilities, technical support, and the process for scaling or moving later. Compare the service details rather than choosing by a plan name alone.
Engage24’s Domains & Hosting service describes shared and cloud hosting options. Ask which option fits the website and support needs you actually have; avoid paying for capacity or services you cannot yet justify.
5. Protect business email during DNS changes
Website hosting and email hosting may be separate. Before changing nameservers or moving a website, identify the current email provider and save the mail-related records. In particular, MX records tell sending mail systems which mail server should receive messages for a domain, as explained in Cloudflare’s MX-record guide.
After a change, test both directions: send a message from the business account and reply from an external address. Also check the website, enquiry forms and any subdomains that customers or staff use. If you are unsure which records can be changed safely, ask the current email provider or developer before editing DNS.
6. Make a recovery plan before launch or migration
Take a current backup before changing a live site, and confirm who can restore it if the move fails. Keep a short change record: the date, the person making the change, the old values, the new values and the checks completed afterwards. For WordPress-specific backup steps, see Engage24’s WordPress site backup checklist.
Before launch, check the main pages, contact forms, mobile layout, website security certificate and business email. Keep access to the old hosting service until the new website and email have been tested and the agreed handover is complete.
A quick pre-launch checklist
- The business knows which registrar holds the domain and can access its account.
- The renewal date, payment owner and contact email are recorded.
- DNS and nameserver details are saved before any changes.
- The hosting plan and support responsibilities fit the website’s requirements.
- Email records are preserved and mail is tested after the change.
- A current backup exists, and someone knows how to restore it.
- The website, forms and key customer journeys have been checked after launch.
Do the domain and hosting need to be bought together?
No. Domain registration and web hosting are separate parts of the setup and can be managed by different providers. If you separate them, keep the account owners, DNS responsibilities, renewal date and support contacts in one place so a change to one service does not become a surprise outage for another.
What should I check before changing DNS?
Save the existing records, identify which ones serve the website and which ones serve email, and confirm the correct new values with the destination provider. MX records direct email to mail servers, so do not remove or replace them as part of a website-only change unless the email provider has confirmed that is required.
Need help with domains or hosting?
If you need help choosing or managing a domain and hosting setup for your business, explore Engage24’s Domains & Hosting service. The team can discuss the available domain and hosting options before you make a change.
Sources: Engage24 — Domains & Hosting; ICANN — Information for Domain Name Registrants; ICANN — Renewing Domain Names; Cloudflare — What is DNS?; Cloudflare — What is a DNS MX record?.