At 8.42 on a Tuesday morning, the website stops loading. Emails start bouncing. The hosted phone handsets will not register, and the payment link on the site is dead. The first assumption inside the business is that several systems have failed at once.
They have not. One thing has failed, or become unreachable: the domain name that connects people and services to your business. Nobody in the room can say who holds the registrar login, or which card pays for it.
That is not simply an outage. It is a control problem. The name, the authoritative DNS records that direct traffic, and many services that depend on those records sit behind a management account that may never have been treated as critical infrastructure.
For an SME, that account can be the hinge between customers and your website, every mailbox, hosted telephony, payment and booking links, a customer portal, API endpoints called by other systems, and TLS certificates used to secure published services. A sensible Cloud Solutions design, Network Solutions and Voice and Connectivity arrangements all depend on knowing who governs the name at the centre.
A domain name feels like a thing you own. In practice, it is a subscription you control, and control sits in one account.
A domain is a subscription, not a possession
A domain registration gives an organisation the right to use a name for a period, through a registrar. The registry is the authority that maintains the records for the relevant domain ending. Your registrar account is the practical control point: it is where registration details, renewals and, often, DNS settings are administered. An invoice proves that someone was billed. It does not necessarily prove the business can log in and make a change.
If registration expires, the name may enter a recovery period when it can be restored, sometimes at additional cost. After it is released, someone else may be able to register it. The precise stages and timings depend on the registry and the domain ending, so a business should not plan around a generic number of days. The point is simpler: an expired domain is not safely waiting for its rightful owner.
A third party registering your old name is not an abstract risk. Domain registration is a service with a price list, and the name may be available to anyone once it is released. The consequences could extend beyond the website. The name may be used to impersonate the organisation, disrupt customer communications or take advantage of services that still trust it.
Keep the registration documentation and evidence of the organisation’s rights to the name. They may be needed to recover access or resolve a dispute. Make the registrant contact details organisation-controlled, using a monitored organisational mailbox rather than a personal address. If that mailbox is at the domain itself, maintain a separate recovery route so the business does not need a working domain to recover the account that controls it.
The account nobody can log in to
In a small business, domain control can be inherited by accident. A web designer registers the name using their personal email. An agency holds it alongside the website hosting. A director who has since left registered it in their own name. The password is in a spreadsheet shared across the office. Two-step verification was switched off because it once blocked a login. No transfer lock is set. Renewal is charged to a personal card that has expired.
None of these arrangements necessarily causes trouble today. Together, they mean the security of the business’s public identity is currently the security of one personal login, a forgotten recovery email or a payment method outside the organisation’s control.
The National Cyber Security Centre advises organisations to secure access to domain management, give more than one trusted person secure access, and have a single internal group responsible for registering and managing domains. Its guidance on protecting your public domain name specifically warns small organisations to move away from personal email accounts for domain management. The NCSC guidance on multi-factor authentication explains the value of stronger authentication for online services; enable the registrar’s two-step verification for every administrator.
The organisation should also choose a registrar with appropriate security features and understand how its recovery process works. The NCSC’s good security practice for domain registrars offers a useful reference when assessing providers. Ask practical questions: can you lock a domain against unauthorised changes or transfers? Can access be managed by role rather than passed around as a shared password? Can you recover the account if a named administrator leaves?

What actually goes wrong
The consequences often begin with something that looks reasonable. An account recovery message is sent to an address at the domain itself. The domain is unavailable, so recovery depends on the thing the business has already lost.
A transfer goes through because no lock was set. A person changing what they believe is a website setting replaces the nameservers, unintentionally pointing mail at a server that does not exist. A DNS record is deleted during a tidy-up, and the website keeps working while the booking system breaks. A certificate expires on a hostname nobody remembered to record.
There are quieter failures, too. A marketing subdomain still points to a service that has been decommissioned. If that record names an external service that someone else can claim, an attacker may be able to take over the subdomain and use it to host content under the business’s name. A lookalike domain registered by someone else may be used to send messages to customers that appear to come from the brand.
The NCSC advises removing stale delegations and alias records when services stop being used. It also recommends enabling available logging and storing logs securely so DNS changes can be reviewed. Without a record of what changed and why, it can be difficult to distinguish an accidental edit from an unauthorised one, or to identify what needs restoring.
The records are a map of the business
A DNS zone is a set of instructions that tells the internet where to find services associated with a domain. Some records point the website to its host. Mail records direct incoming messages. Telephony records can tell softphones where to register. Other records prove to a third-party SaaS platform that the organisation controls the domain and authorises a particular service to act on its behalf.
There may also be records that allow an integration to call back to the organisation. These matter because a hostname can be built into another provider’s configuration. A verification record left behind after a service is retired may amount to delegated authority nobody remembers granting.
Anti-spoofing records, including SPF, DKIM and DMARC, live in the same zone, as described in the NCSC email security guidance. That is worth understanding once, for the governance point: a change made for one purpose can affect something else.
One zone can therefore contain records maintained by different providers and depended on by different parts of the business. Marketing may own a campaign site, finance the payment link, operations the booking system and IT the mail platform. There may be no single person who can read the whole map. That is how a seemingly minor record change can break a service owned by another department.
Change control for something that looks like a setting
DNS is often configured once and then “just works”. That is precisely why it can be maintained less carefully than a server. The control should match the impact, not the appearance of the setting.
For an SME, a controlled change can be straightforward. Name an owner for the domain and records. Require a second trusted person to review changes to nameservers, mail routing or delegation. Record what is changing, who requested it and why. Agree a short verification window after the change, and write down the rollback before making the edit.
A change to a website address might seem routine; a nameserver change can affect the entire zone. The point of a two-person check is not to create a committee for every minor edit. It is to recognise that some changes have a wider blast radius than their interface suggests.
The NCSC advises enabling available logging, storing logs securely and classifying public DNS in the same security category as high-value targets such as web servers. That places domain changes within normal governance: approvals, records, review and accountability. It is also a reason for Managed IT Services to operate under an agreed strategy and authority model, rather than making unrecorded changes on behalf of the business.

Watching it, not hoping
Monitoring should cover both the registrar account and the records that matter. Check that the recovery route works, expiry and auto-renewal are visible, and renewal is tied to an organisation-controlled payment method. Watch for unexpected changes to nameservers, the addresses they point to, mail records and critical service records.
The NCSC also recommends monitoring certificate transparency logs for certificates issued for your domains. An unexpected certificate may indicate someone else has control of the DNS. Monitoring provides a signal to investigate; it does not replace control of the registrar account or a clear response plan.
DNSSEC is a considered decision, not a box to tick by default. It adds cryptographic integrity checking of DNS responses, but also adds key management and zone signing that must be maintained. If configured incorrectly, it can make a domain unresolvable. It needs an accountable owner, not simply an enthusiast who enables it and moves on.
Protective DNS is a related but separate control. It helps protect users on your network by blocking or alerting on requests to malicious domains. It does not manage the records for your own public domain. The NCSC sets out that distinction in its guidance on protective DNS for the private sector. It may complement Network Solutions and other security controls, but it cannot replace sound public-domain management.
The domain in a bad week
An incident is harder when the thing that broke is also the thing you normally use to tell everyone it broke. Work out the recovery route before you need it. Keep the registrar’s recovery procedure and contact details accessible outside the affected account, and keep the documentation that can help prove the organisation’s rights to the domain.
Decide how the business will communicate if its usual email and website are unavailable. That is an out-of-band communications question, not merely an IT one. A separate contact route, staff instructions and a tested Voice and Connectivity arrangement can help people coordinate without relying on the affected domain. The customer contact data used for that purpose needs to be current and available. A logged incident route through Helpdesk Support also gives the business a record of what was tried, by whom and when, which is the difference between a story and evidence when the review happens.
If access is restored, do not stop at restoring the website. Review the zone and registrar activity to identify changes made by anyone who had access. Revoke active sessions and rotate credentials on the registrar and DNS accounts, including recovery credentials where relevant. The NCSC’s advice on recovering a hacked account or service is useful to have in the incident plan before an incident occurs.
If mail was intercepted or a customer portal served content controlled by someone else, assess whether personal data may have been compromised and whether the applicable threshold for notifying the ICO has been met. Record the assessment and the decision either way. The ICO’s guide to data security describes the security principle and the need to consider appropriate measures to protect personal data.
What the estate costs
The domain and DNS estate may include registrar and DNS hosting fees, an agency retainer that includes domain management, certificates bought annually, and a collection of domains kept for campaigns, products or defensive reasons. A domain kept solely to stop someone else registering it can be a legitimate cost, but it should be an explicit decision with an owner and a review date.
Technology Expense Management can help reconcile what is being paid for against what is in use. The purpose is visibility and accountable decisions, not an automatic promise of savings.
A first-month tidy
A practical review can be completed as a sequence, rather than a grand infrastructure programme:
- List every domain from registrar accounts, invoices and the addresses published on your own website. Do not rely on memory.
- Identify which account holds each name and who can log in.
- Move registrant contacts and renewal payments to organisation-controlled details. Enable two-step verification and set a transfer lock where available.
- Name one internal owner and one trusted backup, then confirm both can access the account securely.
- Export or capture the full DNS record set so a copy exists outside the portal.
- Remove dangling aliases and verification records for services no longer used.
- Make a deliberate decision about DNSSEC, and assign responsibility if it is enabled.
- Put domain expiry and certificate renewal into the organisation’s calendar. Write down the recovery route and test that the documentation is accurate.
- Add the domain to the asset register and continuity plan alongside servers and other critical systems.
A Disaster Recovery plan that assumes email and the website will keep working has an unexamined dependency at the top of it. Including the domain in the plan makes that dependency visible, assignable and testable.
Systems that live on a hostname
An IBM i system reached from outside through a hostname and certificate can become unavailable to the people who rely on it if a DNS record changes or a certificate lapses; specialist IBM i Management should account for that external dependency.
An integration or portal may also have a callback URL recorded in a third-party configuration. In that case, the hostname is part of the working agreement between systems. A planned business application change, such as a Dynamics 365 Jump Start, should identify those dependencies before a hostname or its records are altered.

The name is part of the strategy
The domain is the one piece of infrastructure a business shares with everyone it trades with. The register of who controls it, what records exist and what happens if it becomes unavailable is a strategic decision. A Fractal IT Director can establish the governance and architecture; Cloud Solutions, Managed IT Services, Helpdesk Support, Network Solutions and Voice and Connectivity are execution services that support that decision, not substitutes for it. For the wider group of services, evestaff.co.uk is the gateway.
A name is a subscription with a login, not a possession.
SEO keywords:
Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Managed IT Services, Network Solutions, Technology Expense Management, Voice and Connectivity, IT Consultancy, Fractal IT Director
Join The Discussion