Domain Names and DNS: A Plain Guide for Business Owners

A domain name is the unique address that identifies a business on the internet; ICANN describes it as representing a company, organisation or individual, standing in for the numeric address known as an IP address in a form people can actually remember. Buying a domain is not ownership in the usual sense, it is renting the right to use that address for a set period; if it is not renewed when the term ends, the address becomes available to anyone again.

Whichever email address and payment method the registration is tied to effectively holds control. That is why a domain should sit under a business's own corporate email and its own account, not a former employee's or a previous agency's personal one; it is the single most important control point.

DNS, the Domain Name System, is the routing system that translates your domain name into the server address a visitor's browser can use. As ICANN puts it, DNS lets you use a memorable domain name instead of a hard-to-remember IP address.

In practice, a DNS record holds which server your site is hosted on, an A or CNAME record, which server your email passes through, an MX record, and verification records such as SPF, DKIM and DMARC, TXT records. Get one of these wrong and either the site stops loading or the email stops arriving; both live in the same place but do different jobs.

Most businesses buy the domain from one provider, host the site somewhere else, and run email through a third service. That is normal; the DNS record is the bridge connecting all three. The trouble starts when no one knows which account each of the three actually sits in.

When an agency changes or a site is rebuilt, all three connection points need to be found and carried over; miss one, an old email service's MX record, for instance, and business email can stop overnight with no error showing on the site at all.

Under ICANN policy, registrars must send at least two renewal reminders, roughly one month and one week before expiry. Once a domain expires it is usually suspended for a period; if deleted, it can still be recovered during a thirty-day redemption window offered by the registrar, after which the address becomes available to anyone on a first-come basis.

Recovering a domain during that redemption window usually costs considerably more than a normal renewal. Tracking the renewal date, keeping auto-renewal switched on, and making sure the registered contact email is current is an administrative task, not a technical one.

A DNS change does not take effect instantly; it spreads gradually across the internet, a process called propagation, which can take anywhere from a few hours to a full day. Work such as migrating a site or switching email providers should happen during a quiet traffic window, tested in advance.

It should be clear who is authorised to make the change: someone with access to the domain's own registrar panel, ideally under the business's own account. Temporary access can be given to an outside agency, but lasting control should stay with the business.

The most frequent mistake is leaving a domain registered under an employee's personal email. If a manufacturing site registered its domain years ago under the personal address of whoever handled IT at the time, access to the account leaves with that person the day they do.

The second mistake is pushing a DNS change live without testing it first. If a spa chain's booking system moves to a new provider and the MX record is entered wrong, email flow breaks while the site itself keeps loading fine, so the problem can go unnoticed for days.

The third is leaving auto-renewal switched off, so a card that has expired lets renewal fail silently. The fourth, and most common, is never keeping a single written record of who owns the domain, hosting and email accounts; when passwords sit with one manager, registration details with an agency, and the payment card with finance, working out who can actually access what turns into an argument right when there is a crisis to deal with.