21 Oct 20267 minutes read
Waseem OsmanDMARC PractitionerTXT Record Management for DMARC Enforcement at Enterprise Scale

Overview:
- Records that are too narrow fail legitimate email, and records that are too broad can let email from sources you no longer control pass DMARC.
- Multiple SPF records or more than 10 DNS lookups produce a permerror, so email then passes DMARC only through aligned DKIM.
- Assign DNS record ownership to one team per responsibility, and keep a sender registry of every authorized sender.
Large enterprises publish SPF, DKIM, and DMARC as DNS records across dozens or hundreds of domains, sometimes without a named owner for each one. When those records drift, legitimate email can fail authentication, spoofing exposure continues, and auditors can find records that nobody can explain.
Sound TXT record management reduces that exposure. This guide covers which DNS records DMARC enforcement depends on, where TXT record management breaks down in enterprise environments, and how to assign DNS record ownership, so records stay accurate as senders change.
Check your current DMARC record with Sendmarc’s free DMARC record checker to confirm it’s published before you work through the rest of this guide.
Why TXT Record Management Is a Business Risk
SPF, DKIM, and DMARC all depend on DNS records. A DMARC policy is published as a TXT record at _dmarc.example.com, and receiving servers read it when deciding how to treat email that fails authentication.
A policy of p=none means a domain is in monitoring mode. The domain owner receives reports but expresses no preference about what receivers do with failing email. Moving to p=quarantine or p=reject is enforcement, and it works as intended only when the underlying DNS records are accurate.
Inaccurate records create risk in both directions. Records that are too narrow cause legitimate email from your own senders to fail DMARC. Records that are too broad can let email from sources you no longer control pass DMARC.
Both outcomes can produce audit findings that are hard to explain to a risk committee.
Distributed environments make this harder. Marketing, HR, finance, and product teams each run their own sending tools. When a team onboards a vendor, provisions a subdomain, or switches platforms, the related DNS records need to change. Without clear TXT record management, those changes often don’t happen, and stale DNS records accumulate.
Which DNS Records DMARC Enforcement Depends On
SPF record. Publish one SPF TXT record per domain. It lists every IP address and sending service authorized to send email for that domain. For DMARC, an SPF pass counts only when the envelope from domain aligns with the "From" domain.
DKIM records. Each signing key is published in DNS at selector._domainkey.example.com. Publish one record per active platform. A DMARC pass needs only one aligned pass from SPF or DKIM, but RFC 9989 states that domains publishing p=reject must not rely solely on SPF and must apply valid DKIM signatures.
DMARC record. Publish one TXT record at _dmarc.example.com. It sets the version, policy, aggregate report address (rua), and subdomain policy (sp). If a receiver finds more than one DMARC record, RFC 9989 requires it to discard all of them.
Domains that don’t send email still need DNS records. On parked domains, and on legacy or acquired domains that no longer send email, publish a DMARC record with p=reject and an SPF record of v=spf1 -all.
Common TXT Record Management Failures at Enterprise Scale
Multiple SPF Records on One Domain
RFC 7208 requires receivers to return a permerror when a domain publishes more than one SPF record. SPF then produces no pass for that domain. Merge all authorized senders into a single record.
| Host | Type | Value |
|---|---|---|
@ | TXT | v=spf1 include:_spf.vendor-a.example include:_spf.vendor-b.example ip4:192.0.2.10 ~all |
Duplicates appear when teams publish their own SPF record while onboarding a new tool.
Exceeding the 10 DNS Lookup Limit
SPF evaluation allows a maximum of 10 DNS lookups. The include, a, mx, and exists mechanisms and the redirect modifier all count, including lookups inside nested includes. Exceeding the limit produces a permerror, so SPF can’t contribute a pass to DMARC. Email then only passes DMARC if DKIM is aligned.
Enterprise SPF records can breach the limit as includes from third-party senders pile up over time. Remove retired senders first, then consolidate the rest. SPF flattening replaces include chains with resolved IP addresses, but it needs ongoing maintenance because vendors change their IP ranges.
Stale DNS Records
Stale DNS records are records for senders you no longer use. They matter for different reasons:
- A stale SPF
includestill authorizes that vendor’s infrastructure to send as your domain. RFC 9989 advises reviewing SPF records periodically to confirm they match current needs. - A stale DKIM selector keeps a valid public key published for a platform you no longer control. Remove it once you confirm the platform no longer signs for your domain.
- Stale DNS records make audits harder because reviewers can’t tell which entries are intentional.
When a sending platform rotates its signing keys, it typically starts signing with a new key pair under a new selector. The matching public key must be published in the DNS before signing starts.
Alignment Settings That Break Legitimate Email
DMARC uses relaxed alignment by default, which requires only that the authenticated domain and the "From" domain share the same organizational domain. Strict alignment (aspf=s, adkim=s) requires them to match exactly. RFC 9989 notes that nearly all domain owners find relaxed alignment sufficient.
DNS Record Ownership Across Distributed Teams
Different teams own different parts of your DNS records. Marketing owns its sending platform, IT owns DNS, security owns the DMARC policy, and regional entities may control their own subdomains. RFC 9989 recognizes that large companies often delegate DNS management to local departments.
Without defined DNS record ownership, DNS changes skip security review, vendors go live before their SPF and DKIM records exist, and the DMARC policy stays at p=none because nobody has the authority to advance it.
Assign each responsibility to one team:
- DNS changes: infrastructure or IT security applies every change to SPF, DKIM, and DMARC records
- Sender onboarding: the requesting team supplies the SPF
includevalue before the sender goes live - DMARC reports: security reviews aggregate reports and approves each policy change
- Sender registry: a maintained list of every authorized sender per domain, with its SPF
include, DKIM selector, and responsible team
The sender registry is the key output. It shows auditors why each entry exists, and it gives DNS owners a fixed list to check requests against, which shortens approval cycles.
A TXT Record Management Checklist for DMARC Enforcement
Use this checklist as a deployment guide for multi-domain environments and as an audit record.
- Inventory all domains and subdomains. Include parked, legacy, and acquired domains. Record whether each domain sends email, receives email, both, or neither.
- Audit existing DNS records. Confirm each domain has a single SPF record, and count its lookups with Sendmarc’s SPF record checker. List every published DKIM selector and match it to an active sender. Confirm that the
ruamailbox receives reports. - Assign DNS record ownership. Name a DNS change owner for each domain, and require a change request for every SPF, DKIM, or DMARC update.
- Progress the DMARC policy in stages. Start at p=none with a
ruaaddress, and use aggregate reports to identify every legitimate sender. Fix unaligned email streams, then move to p=quarantine and p=reject. - Set a review schedule. Review SPF records whenever a sender is added or retired. Review DKIM keys after each key rotation and on a fixed schedule. Review aggregate reports regularly, and audit all DNS records for stale entries at least annually.
How Sendmarc Can Help
Security and IT teams that are already stretched can’t audit DNS records manually across dozens of domains, and business units keep adding senders nobody approved.
Sendmarc identifies legitimate and unauthorized senders across departments, including shadow IT that breaks authentication, and surfaces misconfigurations before they become incidents. The Sendmarc Platform centralizes SPF, DKIM, and DMARC management across departments, regions, and domains.
For auditors and boards, audit-ready reporting provides verifiable evidence of enforcement status. This supports alignment with frameworks such as PCI DSS, GDPR, POPIA, ISO, and NIST.
Sendmarc’s implementation team moves customers from p=none to p=reject in stages, with guaranteed p=reject enforcement. Monitoring and optimization continue after enforcement, so protection stays current as your environment changes.
Explore DMARC Management to see how sender visibility and record maintenance work across your full domain estate.


