Domain and Hosting Guide

A domain name is the address people use to reach a website. Hosting is the service that stores and serves the website. DNS connects the domain to the correct website, email and other services. They are related, but they should not be treated as one indivisible product.

For a small business, the most important principle is control: the business should know where each service is held, who owns the account, how it renews and how it can be moved without losing the website or email.

The four parts to understand

Domain and hosting components in plain English

Component	What it does	What can go wrong
Domain registration	Records the right to use a name such as example.co.uk for a registration period	The domain expires, is registered to the wrong person or recovery details are inaccessible
DNS	Directs the domain to web hosting, email and other services	A careless change takes the website or email offline
Web hosting	Stores and delivers website files, databases and applications	Poor performance, unsupported software, missing backups or difficult migration
Email hosting	Provides mailboxes using the business domain	Email is lost during a hosting or DNS change because it was assumed to be part of the website

Choose and register the domain

A good domain is easy to say, type and recognise. It should reflect the business name or a stable brand rather than a temporary marketing slogan.

• Avoid unnecessary hyphens, unusual spelling and ambiguous characters.
• Check that the name does not create an obvious trade mark or passing-off risk.
• Consider how it sounds when given over the phone.
• Check matching business email addresses and social names where relevant.
• Do not register many speculative extensions unless there is a real brand-protection or campaign reason.

.co.uk or .com?

A .co.uk address is a natural choice for a business focused on the UK. A .com can be useful for an international brand or where customers already expect it. Neither extension creates rankings by itself.

Some businesses register both and choose one primary address, redirecting the other correctly. This can reduce customer confusion, but it creates another renewal to manage. Do not publish identical versions of the site on both domains.

Register it in the business's name

Use contact and recovery details controlled by the business. If an agency registers the domain on your behalf, obtain written confirmation of the registrant and account ownership. Keep the registrar name, account email, renewal date and support details in the business's asset register.

For .uk domains, Nominet sets the registry policies, while registrations and renewals are normally handled through registrars. The price charged to the customer is set by the registrar, not by a universal retail tariff.

Choose hosting by operational need

Do not choose hosting from storage size alone. A small brochure site may use little disk space but still need reliable support, current server software, working backups and a clear recovery process.

Shared hosting

Shared hosting places many sites on the same server environment. It is often sufficient for a modest brochure or content site when the provider manages resources well. Ask what happens if the site exceeds CPU, memory, traffic or database limits.

Managed WordPress hosting

Managed WordPress hosting may include WordPress-focused support, caching, backups, staging and security controls. The label is not standardised. Compare the actual service rather than assuming “managed” means every update, error or recovery task is included.

VPS, cloud and dedicated hosting

These options provide more resources or isolation, but they also require more administration unless the service is fully managed. They are justified by workload, technical requirements or risk, not by the desire to make a small site sound more professional.

Hosting questions to ask

• Which software versions does the platform support, and how are security updates handled?
• Is HTTPS included and renewed automatically?
• How often are backups taken, where are they stored and how long are they retained?
• Can the customer restore a backup, or must support do it?
• Has the restoration process been tested?
• Is staging available?
• What are the resource and traffic limits?
• What support is available outside normal working hours?
• What does the host monitor?
• Can the site, database and email be exported without a proprietary lock-in?
• What is the renewal price after any introductory offer?

DNS: change only what you understand

DNS records can control the website, email delivery, subdomains and verification for third-party services. Before making a change, export or record the complete existing zone.

Common records

• A and AAAA records direct a name to an IPv4 or IPv6 address.
• CNAME records make one name an alias of another name.
• MX records direct incoming email.
• TXT records are often used for ownership verification and email-protection policies such as SPF, DKIM and DMARC.

DNS changes can take time to be observed because resolvers cache previous information. Avoid promising one universal “propagation time”. The effective delay depends on record settings, caches and the systems involved.

Keep email separate in your plan

A web-hosting migration should begin with an email audit. Identify:

• the current email provider;
• all mailboxes and aliases;
• MX and relevant TXT records;
• how users sign in and recover accounts;
• whether old messages must be migrated;
• how sending will be tested after DNS changes.

Changing nameservers can replace the entire DNS zone. If the new zone does not contain the correct email records, the website may work while messages stop arriving.

HTTPS and certificates

Every public business website should use HTTPS. Many hosts provide automated domain-validated certificates, often through Let's Encrypt. A certificate should renew automatically, but the business should still monitor expiry and configuration errors.

HTTPS protects data in transit between the visitor and the website. It does not secure an outdated application, prevent phishing or prove that the business behind a site is legitimate.

A safe setup sequence

1. Register the domain in an account controlled by the business.
2. Record registrar, DNS, web-hosting and email details separately.
3. Choose hosting against written technical and support requirements.
4. Create and test the website on a temporary or staging address where appropriate.
5. Record the existing DNS zone before any change.
6. Configure HTTPS and test the intended domain.
7. Recreate and verify every necessary web and email DNS record.
8. Reduce DNS time-to-live in advance only when you understand the effect and have a migration plan.
9. Switch the domain at a controlled time.
10. Test the website, forms, email sending and receiving, redirects and certificates.
11. Keep the old hosting available until the new service is proven and a rollback window has passed.

Ownership checklist

• The domain registrant and billing account belong to the business.
• At least two authorised people know where recovery information is stored.
• Multi-factor authentication is enabled where available.
• Renewal dates and payment methods are monitored.
• The business can access DNS without relying on one contractor.
• The business knows which supplier hosts the website and which hosts email.
• A recent website and database backup exists outside the live hosting account.
• There is a written handover process for developers and agencies.

What to check before acting

Domain policies, hosting specifications, prices and software requirements change. Confirm current details with the registrar, registry, host and software provider before registering, transferring or migrating a live business service.

Sources and further guidance

• Nominet: .UK policy and rules (checked 21 July 2026).
• Nominet registrar resources: .UK renewals (checked 21 July 2026).
• Let's Encrypt: getting started (checked 21 July 2026).
• WordPress.org requirements (checked 21 July 2026).