Topic hub

DNS

The Domain Name System directs traffic for websites, email and other internet services. A DNS change is therefore an operational change: the right record can connect a service, while the wrong nameserver or MX edit can…

1 published guides0 subtopicsUpdated 21 July 2026

Start here

The main guide for this topic

Complete guide

What Is DNS? A Business Owner's Guide

DNS is the directory that connects a business domain to its website, email and verification services. You do not need to memorise every record type, but you should know where DNS is hosted, who can ch…

Open the complete guide →

Published guides

Articles in this section

Complete guide21 July 2026

What Is DNS? A Business Owner's Guide

DNS is the directory that connects a business domain to its website, email and verification services. You do not need to memorise …

Read guide →

About this section

The business view of DNS

People use a domain name; computers look up records that describe where to send a request. DNS may be hosted by the registrar, web host, CDN or a specialist provider. The location matters because that account can control website and email routing even if it does not own the domain registration.

Records you are likely to encounter

Common DNS records
Record	Typical purpose	Common risk
A / AAAA	Points a name to an IPv4 or IPv6 address	Old address left live after migration
CNAME	Aliases one hostname to another	Used incorrectly at a provider-restricted root
MX	Directs incoming email	Mail stops after an accidental replacement
TXT	Verification, SPF, DKIM or DMARC	Old senders remain authorised
CAA	Restricts certificate authorities	Certificate issuance fails after an incomplete policy
NS	Delegates DNS hosting	Entire zone changes when nameservers move

Safe working method

Export or record the current zone.
Identify every service using the record.
Check the provider’s exact host/name and value format.
Prepare a rollback value.
Make one logical change.
Verify from an external resolver and test the affected service.
Update the change log after the result is confirmed.

Propagation is not a diagnosis

Cached DNS answers can delay visibility, but “wait for propagation” should not replace checking the authoritative nameservers, record type, hostname, value and TTL. If the authoritative answer is wrong, waiting will not correct it.

When to ask for help

Escalate before changing nameservers, DNSSEC, live MX records or a complex email-authentication setup unless the business has a current export and rollback route.

Who should have DNS access?

Give access according to responsibility. A web developer may need to edit web records, while the email administrator may manage authentication records. Where the provider cannot restrict permissions, use a controlled change process and avoid sharing the master password. A password manager with named access is preferable to credentials copied into chat.

For a critical domain, enable provider alerts and retain an offline zone export. If DNS hosting is tied to a web-hosting account, understand what happens to the zone when hosting is cancelled.

Final publication check

The authoritative DNS provider is known.
A current zone copy exists.
High-risk changes require approval and rollback.
Cancellation of hosting will not unexpectedly delete the only DNS zone.

Sources and date checked

Technical and policy information was checked on 21 July 2026. Recheck provider-specific procedures before making a live change.