Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Website & Infrastructure 6 min read

DNS security and configuration checklist for business domains

A domain-by-domain DNS checklist covering registrar locks, authoritative servers, DNSSEC, email records, change control and quarterly evidence.

E
EncryptTechBD · 0 comments
Coiled ethernet cable on a blue background
Photo: Markus Spiske / StockSnap

Most domain failures are not sophisticated attacks. They are an expired registration, a missing record after a migration, a nameserver change nobody documented or a mailbox that still receives recovery email for a former employee. DNS is a control plane for your website, email and payments, and it deserves the same change discipline as a production server.

This checklist is designed for a business that owns several domains and subdomains but does not have a dedicated network team. Use it once to establish a baseline, then keep the recurring items on a calendar. Each control has an owner and a piece of evidence, because a DNS review without screenshots or exports is only a conversation.

Set the scope and the source of truth

Start with a complete portfolio: the primary domain, campaign domains, parked domains, country domains and any domain held for a product or acquisition. Include subdomains that point to SaaS tools, because those records can outlive the service that created them.

  • Domain register: registrar, expiry date, billing owner, technical contact and the business service that depends on it. Owner: IT lead. Evidence: dated export. Frequency: quarterly.
  • DNS provider register: which provider hosts each zone, who has admin access and whether there is a secondary provider. Owner: infrastructure lead. Evidence: provider console export. Frequency: twice a year.
  • Record inventory: A, AAAA, CNAME, MX, TXT and CAA records with a purpose for each. Owner: infrastructure lead. Evidence: zone export. Frequency: quarterly.
  • Shadow DNS: records created by marketing tools, website builders or staff without a change ticket. Owner: IT lead. Evidence: comparison of zone export to approved list. Frequency: quarterly.

Registrar and account controls

The registrar account is a single point of failure. Treat it as a privileged system, not a billing convenience.

  • Registrar lock enabled on every production domain, with the unlock procedure documented.
  • Multi-factor authentication on the registrar account, with at least two people able to recover access.
  • Recovery email on a monitored company mailbox, not a personal address or a departed employee's account.
  • Auto-renew enabled where available, plus a calendar reminder before expiry in case the card fails.
  • Registrant contact details current, including a role-based address that survives staff changes.
  • Transfer authorization codes stored in the password manager and access limited to named administrators.

Authoritative DNS configuration

A zone should be small, documented and served by more than one nameserver. Remove records that no longer serve a purpose, especially wildcard records and test subdomains that point to internal systems.

  • At least two authoritative nameservers on separate networks, confirmed by a query from outside your office.
  • Zone transfers restricted to known secondary servers; public transfers disabled.
  • Recursion disabled on authoritative servers.
  • Wildcard records removed unless there is a documented business case and an owner.
  • TTL values chosen deliberately: short enough for planned migrations, long enough to reduce query load.
  • DNSSEC considered for zones that support it. Signing adds integrity but also adds key-management work; confirm the provider handles rollover and that monitoring covers expiration.
  • CAA records listing the certificate authorities allowed to issue for the domain.

Email authentication records

SPF, DKIM and DMARC are DNS records with a security consequence. They are not set-and-forget. Every time a new sending tool is added, the records may need to change.

  • SPF: one record per domain, under the lookup limit, listing only approved senders. Review when a marketing or support tool changes.
  • DKIM: a selector and public key for each sending service, rotated with the provider's guidance and documented in the register.
  • DMARC: a policy record with a reporting address, starting in monitoring mode before enforcement. Confirm alignment with the domains actually used in the From header.
  • Reporting: aggregate reports reviewed monthly by a named owner, with a process for investigating failures.
  • Lookalike domains: a watchlist for common misspellings, with a decision to register, monitor or ignore each one.

Change control and monitoring

DNS changes are easy to make and hard to see. Put them through a ticket with a rollback record, even when the change is a single TXT value.

  • A named approver for production zone changes, separate from the person making the change where staffing allows.
  • Before-and-after zone exports attached to the ticket.
  • Alerting on changes to nameservers, MX records and CAA records, not just on website uptime.
  • Certificate issuance monitoring for unexpected certificates on your domains.
  • Uptime and resolution checks from more than one network, with an alert route that reaches a person.
  • A quarterly reconciliation between the approved record list and the live zone.

Review calendar and sign-off

ActivityFrequencyOwnerEvidence
Domain expiry and registrar access reviewQuarterlyIT leadRegistrar export and access list
Zone export compared with approved recordsQuarterlyInfrastructure leadDiff report with exceptions
SPF, DKIM and DMARC reviewMonthlyEmail administratorReport review note
DNSSEC key and expiry checkQuarterlyInfrastructure leadProvider status screenshot
Full domain portfolio reviewAnnuallyIT and financeSigned portfolio register

Sign-off should record the reviewer, date, scope and every accepted exception with an end date. If a domain is intentionally parked or a record is intentionally wild, write that down. The next reviewer needs to know the difference between a decision and a mistake.

Incident readiness

Keep a one-page runbook for domain takeover, accidental deletion and email spoofing. It should name the registrar support channel, the DNS provider escalation path, the person authorised to change nameservers and the customer communication owner. Test the contact list twice a year; a runbook with an old phone number is worse than no runbook because it creates false confidence.

Where this fits in our work

DNS and domain hygiene is part of Managed Technology & Cybersecurity, alongside website hardening and infrastructure monitoring. The pricing page explains how a baseline review differs from ongoing management. For the configuration sequence behind this checklist, read the step-by-step DNS configuration guide.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes