A hosting invoice does not tell you everything about how your website works. Your domain, website files, email and enquiry system may live with different providers. Understanding the connections gives you a useful starting point when something needs changing, without needing to manage the technical work yourself.
- Domain
- Registration and control of the business address.
- DNS
- Records that direct web, email and other services.
- Hosting
- The environment that serves the website.
Moving website hosting does not require every service to move. Identify the relevant records and preserve the services outside the agreed change.
Separate the address from the website.
The domain is the name people use to find you. The registrar manages its registration. Hosting serves the website, while DNS holds records that direct services using that name. One company can provide several of these jobs, but they are still separate responsibilities.
Cloudflare documents different records for website addresses, mail delivery and verification. That matters when a website moves: changing where the website points should begin with an account of the email and other services that also use the domain.
Reading behind this section: Cloudflare
Know who can make each change.
Keep a short register of the registrar, DNS provider, host and email provider. Record the account holder, renewal contact, billing contact and person authorised to make changes. Store passwords and recovery codes securely rather than putting them in the register.
Confirm how the business can regain access if a staff member or supplier becomes unavailable. Provider-managed accounts can have different access arrangements. The useful question is whether the business understands that arrangement and has a documented way to request a change.
Allow for different people seeing different results.
Julia Evans explains how DNS resolvers cache answers. After a record changes, some visitors may receive an older answer until that cache refreshes. A successful check on your own laptop therefore does not establish that every customer has reached the new website.
Ask for a change plan that identifies the record being changed, the existing value, the new destination and the checks afterwards. Those checks should cover the website and the other services affected by that particular change.
Reading behind this section: Julia Evans
Give the ongoing work an owner.
Agree who watches renewals, who receives service alerts and who handles a reported problem. Hosting, content changes, software maintenance and email support may have different scopes. Writing those boundaries down helps a busy team reach the right person with the right information.
If you are unsure what exists, start with the invoices and access you already have. A practical first step is a one-page service map with the gaps clearly marked.
Put it to use
A useful check for your business.
- List the domain, DNS, hosting and email providers.
- Confirm renewal contacts and a secure recovery route.
- Record the services affected before changing DNS.
- Agree who handles each kind of support request.
The thinking behind this guide
Sources & further reading.
Our practical interpretation, with the references below for the specific principles and further detail.
- DNS record types
Different DNS records support website addressing, mail delivery and service verification.
- What happens when you update your DNS?
Resolver caching and TTL help explain why a DNS change can be observed at different times.
