Skip to main content

Updating your DMARC Record on your DNS Provider

For domains not using Hosted DMARC, update the DMARC TXT record directly in your DNS provider.

When to Use This Method​

If your domain uses a traditional DMARC TXT record (not a CNAME pointing to Palisade), you need to log into your DNS provider each time you want to change your DMARC policy. This guide walks through that process.

tip

Consider switching to Hosted DMARC for easier future updates. With Hosted DMARC, you manage your policy from the Palisade dashboard without returning to your DNS provider.

Steps​

1. Generate the New Record Value​

  1. In Palisade, navigate to the Manage DMARC page for your domain.
  2. Adjust the policy settings as needed (policy level, subdomain policy, percentage, alignment, etc.).
  3. Copy the generated DMARC record value. It will look something like:
v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com; pct=100; adkim=r; aspf=r

2. Log Into Your DNS Provider​

Access your DNS provider's management console. Common providers include:

  • Cloudflare -- DNS settings under your domain
  • GoDaddy -- DNS Management in domain settings
  • Namecheap -- Advanced DNS in domain management
  • AWS Route 53 -- Hosted zones in the Route 53 console
  • Google Domains -- DNS settings in domain management

Each provider has a slightly different interface, but the process is the same.

3. Find the Existing DMARC Record​

Look for a TXT record with the name/host _dmarc. This is your current DMARC record.

4. Replace the Record Value​

Edit the existing _dmarc TXT record and replace its value with the new value you copied from Palisade.

warning

If using Cloudflare, ensure the proxy status is set to DNS Only (gray cloud icon). Cloudflare's proxy does not apply to TXT records, but having it set to DNS Only avoids any confusion.

5. Save and Wait for Propagation​

Save the record. DNS changes typically propagate within a few minutes to a few hours, but full propagation can take up to 24-48 hours depending on TTL settings and DNS provider.

6. Verify in Palisade​

After updating the record, return to Palisade and click Verify on the Manage DMARC page to confirm the change was detected. If verification fails, wait a bit longer for propagation and try again.