What Is DNS? A Plain-English Guide for Business Owners
Understand DNS records, nameservers and how website and email services connect to a domain, with practical precautions before changes.
Part of our guide: Who Owns Your Business Website? Domains, Content, Hosting and Access Explained
DNS is the system that helps computers find the services associated with a domain name. It connects a familiar name such as a business web address with technical destinations.
Different records can direct the website, email and other services separately. That is why a website can move to new hosting while the same domain and email addresses remain in use.
Start with the main parts
The domain registrar manages your registration. The DNS provider hosts the authoritative records. The web host serves the website. The email provider handles mailboxes and mail delivery.
One company may provide all four, or each may be separate. The nameservers listed for the domain indicate which DNS service is authoritative.
Keeping this map makes account changes easier to understand.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
What do common records do?
An A record points a name to an IPv4 address. An AAAA record points to an IPv6 address.
A CNAME record makes one name an alias of another name, subject to DNS rules and provider features.
MX records identify mail servers for incoming email. TXT records hold text used for purposes such as verification and email authentication.
Cloudflare’s DNS record guide explains these types. The exact records needed depend on the services you use.
Nameserver changes affect the whole record set
Changing one web record is different from changing nameservers.
A nameserver change moves authority to another DNS service. If the new service lacks the existing email or verification records, those functions can fail even though the website works.
Before changing nameservers, export or record the current zone and recreate the required records at the destination. Have a knowledgeable person verify the complete set.
Why changes are not visible everywhere immediately
When access fails for only one person, compare browser, device and network conditions before attributing every symptom to DNS.
DNS responses can be cached. A record’s time to live, or TTL, tells resolvers how long it may be retained.
Different users can therefore see old and new destinations during a change. Timing depends on caches, previous settings and the change being made; avoid treating a fixed “propagation time” as a universal guarantee.
Plan an overlap and test from more than one location where appropriate.
Protect email records
Email commonly relies on MX records and authentication records such as SPF, DKIM and DMARC.
Do not remove unfamiliar TXT records merely to tidy the list. They may verify a business service or support mail delivery.
Ask the email provider for the required configuration and preserve it during website changes. See what happens to email when a website is rebuilt.
DNS is not the website content
Editing a DNS record does not rewrite a page or copy files to new hosting. The destination needs to be prepared before visitors are sent there.
Likewise, changing the registrar does not necessarily require changing the host. These operations can be coordinated or separated according to the plan.
The guide to moving agencies explains why the distinction matters.
What should a business owner record?
Keep the registrar, DNS provider, authorised administrators and recovery process in the account inventory.
Record why important entries exist and which supplier owns the associated service. Store sensitive account credentials securely elsewhere.
For a planned change, retain the previous values, the intended new values, the reason and a rollback plan.
How can you make a change safely?
Confirm the exact service being changed. Obtain the destination provider’s instructions, review dependencies and choose a suitable time.
Afterward, test the website, forms, email and relevant subdomains. Do not cancel the old service until the replacement has been verified.
If something fails, use the recorded values and agreed recovery plan rather than making several unrelated changes at once.
Do you need to manage DNS yourself?
Before moving a site, use the domain connection and email protection checklist to record the existing settings, authorised changes and tests.
You can delegate technical work while retaining business control and documentation. The key is knowing who can act and what they are authorised to change.
Read domain ownership checks, hosting control and SSL certificates for the related pieces. Contact AfterWorks if you need a clear map before moving your website.
