Nuage Solutions All articles
Cloud Strategy

Custody Before Configuration: A Domain and DNS Control Review for UK Businesses

Nuage Solutions
Custody Before Configuration: A Domain and DNS Control Review for UK Businesses

The domain is the least glamorous component of a cloud estate, and for that reason it is often the least examined. Identity providers, mailboxes, customer portals and payment pages all depend on a name resolving correctly, yet few UK organisations can say with confidence who holds the registrar account, which provider serves the zone, or which individual last changed a DNS record. The dependency is absolute and the cost of verification is modest. That imbalance is what makes the domain layer worth reviewing on a fixed schedule rather than after a failure.

Why the domain layer escapes routine review

Cloud strategy documents tend to concentrate on workload placement, resilience and cost. Domain registration sits outside those discussions because it is neither a workload nor a platform. It is a contractual and administrative arrangement, usually made years ago, often by a web agency or a former member of staff, and rarely revisited while everything continues to resolve.

The result is a quiet accumulation of risk. A registrar account may still be registered to a personal email address. A renewal card may have expired with the employee who set it up. DNS may be hosted by an agency whose contact details have changed, or by a provider nobody remembers selecting. None of this is visible in a service status page, and none of it appears in a typical cloud cost report.

Start with registrar custody, not DNS records

A custody review should begin with the registrar account rather than the records themselves. Records can be rebuilt from a zone export; an inaccessible registrar account cannot. For each domain, establish the legal registrant, the account holder, the billing contact and the technical contact. Confirm which individuals can log in, whether multi-factor authentication is enforced, and whether the account is registered to a role-based address rather than a personal mailbox.

For .uk names, the registrant details held by Nominet should match the organisation's current legal entity. Where a domain was registered through a reseller, establish whether the organisation has direct access to the registry record or only a reseller relationship. Check the registrar lock status and confirm that the authorisation code can be obtained by someone inside the organisation, not only by the original supplier.

The practical test is simple: could two named employees, without assistance, renew the domain, transfer it and recover the account if the current administrator left today? If the answer is uncertain, the domain is not under proven custody.

Map where DNS is actually served

The registrar and the DNS provider are frequently different organisations. Delegation at the registry points to nameservers, and those nameservers may belong to a hosting company, a content delivery network or a managed service provider. Record the nameserver hostnames and confirm which account controls the zone.

A useful discipline is to export the full zone and compare it with what the business believes it publishes. Look for records that no longer serve a purpose, subdomains delegated to forgotten third parties, and any wildcard entries that could mask a misconfiguration. Where an agency holds the zone, ask for a read-only account or a documented change process. A supplier who cannot provide either is a single point of failure, regardless of how reliable their infrastructure may be.

DNSSEC and certificates: the expiry surface

DNSSEC adds a chain of trust that can fail silently if key material or delegation records are not maintained. Confirm whether DNSSEC is enabled, who holds the keys, and whether the signing arrangement is compatible with any planned registrar or DNS move. A domain signed by one provider and transferred without adjusting the DS record can stop resolving, which is a severe outcome for a modest administrative oversight.

Certificates form a parallel expiry surface. Inventory publicly trusted certificates for customer-facing services, note the issuing authority and renewal method, and confirm who receives expiry notifications. Where certificates are issued automatically, verify that the automation has permission to update DNS validation records. The same question applies to any service that depends on a DNS TXT record for verification: who can change it, and who would know to do so at short notice?

Mail authentication records are custody evidence too

SPF, DKIM and DMARC records are often treated as a mail configuration task, but they are also evidence of who controls the zone. An SPF record that authorises a departed marketing platform, a DKIM key that nobody can rotate, or a DMARC policy set to none with no reporting address all suggest the domain is being maintained by habit rather than ownership.

Review the authorised senders against the current business. Confirm that DKIM selectors are documented and that private keys are held in an accountable system. Ensure the DMARC reporting address reaches a monitored mailbox. These checks are inexpensive and they reveal whether the organisation can make an authoritative change to its own domain when it needs to.

The one-page handover document

The output of the review should be a single page that a new administrator could act on without a conversation. It should list each domain, the registrar, the registry identifier where applicable, the DNS provider, the nameserver hostnames, the DNSSEC status, the certificate renewal owner and the mail authentication owner. It should name two accountable individuals and describe where credentials are stored.

That page is not a substitute for access controls, but it is proof that control has been considered. It also shortens the handover when a supplier changes or a long-serving employee leaves. Keep it current by reviewing it alongside the quarterly access review rather than treating it as a one-off project.

A quarterly routine, not a project

Domain custody is cheap to verify and expensive to discover late. A short quarterly check covering registrar access, delegation, DNSSEC status, certificate expiry and mail authentication records will catch most of the quiet failures before they surface. The domain layer rarely announces its risk. It simply stops resolving when the arrangement behind it is no longer maintained. Proving custody is the least dramatic form of resilience work, and one of the most useful.

All Articles

Related Articles

After the Last Workload Moves: Five Cloud Contract Terms That Shape the Estate

After the Last Workload Moves: Five Cloud Contract Terms That Shape the Estate

When the Status Page Turns Red: A Practical Outage Rehearsal for UK SMEs

When the Status Page Turns Red: A Practical Outage Rehearsal for UK SMEs

Cheap Cloud Storage Has a Long Invoice: A UK SME Cost-Control Guide

Cheap Cloud Storage Has a Long Invoice: A UK SME Cost-Control Guide