Small Business DNS Records Guide: A Maintenance Checklist for Websites and Email

Overview

DNS, or the Domain Name System, tells browsers and email servers where to find services connected to your domain. Your registrar, website host, email provider, and other platforms may each provide records to add or change. The exact values depend on those providers, so treat the records below as a planning reference rather than universal copy-and-paste settings.

A small business website commonly uses an A record, an AAAA record, or a CNAME record. Business email normally requires MX records and several TXT records, including SPF, DKIM, and DMARC. A software platform may also ask for a TXT or CNAME record to verify ownership of the domain.

DNS changes are separate from changes made inside your website or email account. Adding an MX record does not create an inbox, and adding an A record does not automatically configure a website. Complete the provider’s setup steps as well as the DNS step.

Checklist by scenario

When launching or moving a website

1. Write down the domain, subdomains, current registrar, website host, and any connected services.
2. Save a copy or screenshots of the current DNS zone before editing it.
3. Confirm whether the host requires an A record, AAAA record, CNAME record, or a combination.
4. Check the root domain and the www hostname separately. They may use different records.
5. Remove or replace old website records only after confirming that they are no longer needed.
6. Test the homepage, secure HTTPS connection, contact forms, redirects, and important subdomains after the change.

Do not assume that a CNAME for www also controls the root domain. Your provider should explain how the root domain is connected. If the domain uses forwarding, a website builder, or a proxy service, follow that product’s instructions rather than combining settings from multiple guides.

When setting up business email

1. Confirm the email provider’s required MX records and their priority order.
2. Identify every service that sends messages using your domain, such as your mailbox provider, website forms, customer relationship system, newsletter platform, or invoicing tool.
3. Add the provider’s SPF instruction as a TXT record. If an SPF record already exists, update it instead of creating a second competing SPF record.
4. Generate or copy the DKIM record from the provider. It commonly uses a selector hostname, so copy the selector exactly.
5. Add a DMARC TXT record after reviewing which legitimate services send mail for the domain.
6. Send test messages to more than one mailbox and inspect the authentication results where available.

Email authentication is a maintenance task, not a one-time installation. Adding a new marketing or support platform may require an SPF update, a new DKIM record, or a review of DMARC alignment.

When verifying a service or subdomain

1. Read whether the service requests a TXT record, CNAME record, or a file placed on the website.
2. Enter the host or name exactly as shown. Some DNS dashboards automatically append your domain, while others expect the full hostname.
3. Leave unrelated records unchanged.
4. Complete verification in the service dashboard after saving the DNS record.
5. Keep a note of the record’s purpose so it is not accidentally deleted during a later cleanup.

For a broader website and domain planning checklist, see Local Business Domain and Website Setup Guide on a Budget.

What to double-check before saving

• Correct DNS provider: Make sure you are editing the nameservers currently authoritative for the domain. Changes in an unused registrar dashboard will not affect the live domain.
• Host or name field: A provider may describe the host as @, the root domain, or a subdomain such as mail. Use the format expected by your DNS interface.
• Record conflicts: A hostname generally cannot use a CNAME alongside other record types at the same name. Look for existing records before adding one.
• MX priorities: Preserve the priority values supplied by the email provider. They determine how mail systems choose among servers.
• SPF scope: List all approved senders, including services used by forms or automated notifications. Avoid adding services that do not actually send mail for the domain.
• DKIM selector: Copy the selector and destination precisely. A small spelling difference can prevent validation.
• DMARC impact: Choose a policy that matches your testing and operational readiness. A strict policy introduced before all legitimate senders are aligned can affect delivery.
• TTL and timing: DNS updates are cached. The time before a change is visible can vary by record, resolver, and previous cache settings, so do not plan a critical launch around an immediate result.

Keep a simple DNS inventory with columns for hostname, record type, value, purpose, provider, date checked, and owner. This is more useful than relying on memory, especially when several people manage the domain.

Common mistakes

Deleting all records during a website move. A website migration usually does not require removing email, verification, or unrelated subdomain records. Change only the records covered by the migration plan.

Creating two SPF records. SPF is published through TXT records, but multiple separate SPF policies for the same domain can create an ambiguous setup. Edit the existing policy or follow the email provider’s documented method for combining senders.

Changing MX records without checking existing mail. MX changes affect where new incoming mail is delivered. Confirm mailbox access, aliases, forwarding, and historical mail before switching providers.

Using the wrong hostname format. Some dashboards automatically add the domain name; others do not. Entering a full domain where only a label is expected can create a record at the wrong location.

Leaving old services authorized forever. When a newsletter platform, form tool, or hosting account is retired, remove its email authorization or verification record after confirming that no active workflow depends on it.

Making several unrelated changes at once. If the website, email, and domain verification all fail after one large edit, troubleshooting becomes harder. Group changes by purpose and record what was changed.

For related name-and-address consistency work, the Local Citation Building Guide can help connect website maintenance with accurate local business information.

When to revisit

Review your DNS records at least whenever one of the underlying services changes. Put the checklist on your calendar before seasonal planning cycles if your business runs campaigns, launches promotions, or changes staffing around those periods.

• Before launching a new website, landing page, or subdomain.
• Before moving hosting, changing registrars, or changing nameservers.
• When switching email providers or adding a service that sends mail.
• After a rebrand, domain renewal issue, ownership change, or security incident.
• When contact forms stop arriving, messages are rejected, or email authentication reports show unexpected senders.
• After retiring software, marketing tools, or old hosting accounts.
• When workflows or provider requirements change.

For each review, export or record the current zone, confirm the website and email tests, remove only obsolete entries, and note the person responsible for the next check. If a change is business-critical, lower-risk testing and a rollback copy are more valuable than making many edits quickly. DNS is part of your web presence infrastructure: a small, current inventory can prevent avoidable downtime and email confusion.