The Domain Name That Nearly Took a Business Offline

A domain name can look like a small part of your IT setup. It isn't. For most organisations, the domain sits underneath their website, email and online identity. Lose control of it and what starts as an administrative problem can become a serious business continuity incident.

The Situation

The client's domain had originally been placed into a dedicated registrar account under the client's control. This was deliberate.

Altitude IT had previously advised that the domain should remain independent of web developers and other third-party suppliers. Websites can be rebuilt. Hosting can be moved. Microsoft 365 can be reconfigured. Your domain name is much harder to replace.

Despite that advice, the domain was later transferred as part of a website project involving members of the client's team and an external web supplier. Some time later, that supplier relationship ended. The client then discovered it no longer had effective administrative control of its own domain name.

Why This Was More Than a Website Problem

The Microsoft 365 environment itself remained secure. Altitude IT retained appropriate administrative access to the client's Microsoft 365 tenant, meaning the mailboxes and Microsoft 365 data were not dependent on the former web supplier.

The problem was DNS. The domain's authoritative DNS remained dependent on the previous web arrangement. If that DNS service stopped responding: external systems could lose the ability to locate the client's Microsoft 365 email service; inbound email could eventually fail; the website could disappear; recovering either service quickly would become considerably harder without control of the underlying domain.

This had become a genuine business continuity risk.

Your Microsoft 365 tenant can be perfectly healthy while losing control of the DNS underneath it still takes your email offline.

Establishing What Had Happened

Working alongside the client's digital specialists, Altitude IT helped establish: which registrar currently controlled the domain; which nameservers were authoritative; where the DNS zone was being hosted; where the website was hosted; that Microsoft 365 remained under the client's administrative control; the historical circumstances surrounding the original domain transfer.

The history was important. Altitude IT had previously created an independent registrar account specifically so that the domain remained under the client's control rather than under the control of a website supplier. The later transfer had removed that protection.

Recovering Control

Rather than immediately escalating into a formal dispute, the first approach was to see whether the position could be resolved commercially and voluntarily. At the same time, the client began establishing its position directly with the appropriate UK domain registry. This created two possible routes.

Voluntary Transfer: agree the position with the former supplier and transfer the domain back into an account controlled by the client.

Registry Recovery: establish the client's rights to the domain and recover control using the appropriate registry processes.

Altitude IT supported the technical side while ensuring that questions of ownership and authority remained with the client.

The Outcome

The domain was successfully recovered and returned to an account controlled by the client. The historical evidence helped demonstrate how the domain had originally been managed, why it had been deliberately separated from third-party suppliers, and what had subsequently changed. The costs associated with resolving the dispute ultimately fell to the opposing party rather than the client. Most importantly, the organisation retained its established domain and avoided a prolonged interruption to email and web services. It was a near miss.

Your Web Developer Shouldn't Own Your Business Identity

Neither should your IT company. Your company's domain should sit in an account that your organisation owns and controls. Suppliers should receive the technical permissions they need without owning the underlying asset.

Do you know who controls your domain?

1. Who is the registered holder of your domain name?
2. Which registrar currently holds it?
3. Who can log into the registrar account?
4. Is multi-factor authentication enabled on the registrar account?
5. Which organisation controls your DNS?
6. Who controls the recovery email address and phone number?
7. Could you recover the domain without your current IT provider or web developer?
8. Is your registrar access documented in your business continuity plan?

If you cannot confidently answer these questions, you have a business continuity gap.

Why Altitude IT Looks Beyond the Helpdesk

Good IT support isn't just fixing laptops and resetting passwords. Altitude IT looks at the technology dependencies that could actually stop your organisation operating: Microsoft 365 and cloud services; identity and access management; cyber security; backups and data recovery; internet connectivity; DNS and domain management; domain ownership and registrar control; supplier dependencies; business continuity planning.

Sometimes the best IT incident is the one you identify before anything actually goes offline.