A domain renewal and a DNS change are different jobs. Renewal keeps your registration active. DNS records direct the website, email and sometimes other services. A business can renew successfully yet break mail with a careless nameserver change; it can also have perfect DNS records but lose the domain if renewal fails.
The small-business website continuity plan puts this change in the wider account and recovery record.
Use this checklist when a renewal is approaching, a designer requests a DNS edit or a host asks you to change nameservers. If you do not know who controls the registrar and DNS, complete the website ownership audit before changing anything.
Before renewal: prove the account is recoverable
Confirm the registrar account is controlled by the business, the renewal date and payment method are current, and notices go to an inbox someone monitors. The NCSC advises small organisations to put domain management under organisational control and protect the account that manages the name. A personal email belonging to a former worker is a risk even when auto-renewal is switched on. Source: NCSC, Protecting your public domain name.
Record the domain name, registrar, account owner, renewal date, authorised support contact and a second way to recover the account. Keep payment details inside the provider’s secure account, not in the checklist. Check the renewal confirmation and new expiry date in the registrar account after payment; do not rely only on an email receipt.
Before a DNS change: find the authoritative settings
Ask what specific outcome the change must produce. For example: point only the website to a new host while keeping email where it is; add a verification record; or move mailboxes as a separate planned project. Do not treat all of these as a generic “domain transfer”.
Record the existing nameservers and the current relevant DNS entries with a date. The person making the change should identify which records affect the website, which affect email and which verify a service. Do not paste sensitive account tokens into an ordinary public ticket. Confirm who can restore the previous settings and how the team will test the affected services.
| Planned change | Owner decision | Acceptance check |
|---|---|---|
| Domain renewal only | Is the business still the account holder, and are notices monitored? | New expiry date visible in registrar account; site and email still work. |
| Website host change | Is email staying with its current provider? | Website and enquiry path work on the intended destination; mail route still works. |
| Nameserver change | Have all necessary DNS records been identified for the new zone? | Web, mail and other named services tested after the switch. |
| Email provider change | Which mailboxes, historical mail and sending records must move? | Send, receive and replies tested by named users; website enquiry mail tested. |
The hosting migration guide goes deeper on separating a WordPress move from email. If a redesign changes page URLs as well, keep a separate redirect map for those web addresses; DNS changes do not replace page redirects.
Make the change as a controlled release
Choose a time when the business can test and respond. Preserve the current settings before editing. Make only the approved change, then have the account owner and the relevant provider check it. A browser showing the new homepage does not prove that email, forms or order notifications are working.
Test the site from a normal device; submit a labelled harmless enquiry and confirm it arrives; send and receive a business email; check any service explicitly named in the change record. If the result is wrong, use the agreed recovery route. DNS propagation and cached results can differ between networks, so record the observation and time rather than declaring success from one screen.
Do not change a live site’s domain or DNS merely to improve search rankings. When a genuine site move changes URLs, Google’s site-move guidance covers URL mapping, redirects, internal links and verification. This checklist deals with account and routing continuity.
Keep the record for the next supplier
Write down who approved the change, old and new settings, when it happened, what was tested and any unresolved issue. Store it with the business’s account map, outside the website itself. That gives a future designer or host a starting point without asking the owner to remember a hurried support call.
If you are moving a Formby or Freshfield business site and need the web, email and enquiry routes scoped together, use our web design service or contact page with the current provider list. The first useful step is to identify exactly what should change and what must stay working.
