Skip to main content

Troubleshooting DNS Conflicts During Email Sending Domain Verification (iCampaign)

Purpouse: This guide helps resolve DNS record conflicts that prevent email sending domain verification from completing in iCampaign. This specifically addresses when existing SPF and DKIM records interfere with Mailgun verification.

Symptom: Domain Verification Remains Pending

Your sending domain verification remains "pending" or "unverified" even after adding the required TXT and CNAME records to your DNS provider (like GoDaddy, Cloudflare, etc.). The records appear correct in your host, but verification doesn't complete after 24–48 hours.

  1. Click "Settings"

  2. Click "Sending Domains"

  3. We can find the domain registration statuses here.

Cause: Conflicting DNS Records

Conflicting DNS records can prevent Mailgun from properly verifying your domain. This usually happens when existing SPF and DKIM records from previous email services block the new ones.

Common conflicts include:

  • Existing SPF records (e.g., v=spf1 include:websitewelcome.com ~all).

  • Old DKIM records (e.g., default._domainkey).

  • Multiple TXT records configured with the exact same host name.

Solution: Identify and Resolve Record Conflicts

Step 1: Identify Conflicting Records

  1. Log into your DNS provider (GoDaddy, Cloudflare, etc.) and navigate to your DNS management section.

  2. Look for existing TXT records that contain SPF records starting with v=spf1.

  3. Look for DKIM records with hosts like default._domainkey or similar. (📸 Screenshot: Use Scribe to show an example DNS control panel with conflicting TXT/SPF records highlighted)

Step 2: Determine if Records Are Still Needed

Check if the existing records are connected to active email services. If you are unsure, contact your previous email provider or IT team. Document exactly which services are still actively using these records.

Step 3: Resolve the Conflicts

Choose the option below that best fits your situation:

Option A: Remove Inactive Records

  1. If the conflicting records are no longer needed, delete them from your DNS host.

  2. Wait up to 24 hours for the DNS changes to propagate across the internet.

  3. Check your iCampaign domain verification status.

Option B: Merge Active Records If you need to keep existing records for other active services, contact Dazos support. Our technical team can help merge SPF records or find alternative solutions. Please provide screenshots of all current DNS records to support.

✅ Expected Result: After resolving DNS conflicts, your domain verification should complete within 24 hours. You will see a "Verified" status in your iCampaign sending domain settings.

💡 Tip: You only need one verified sending domain to send campaigns in iCampaign. Having multiple verified domains serves as a backup and can improve deliverability for high-volume sending, but it's not required to get started.

Escalation: When to Contact Support

Contact Dazos support if you experience any of the following:

  • You are unsure which DNS records are safe to remove from your host.

  • You need help merging SPF records with existing services.

  • Domain verification still fails after removing known conflicts and waiting 24 hours.

  • You need assistance with DNS provider-specific configuration steps.

Related Articles
Get to Know iCampaign: Defining Features and Key Advantages
Custom Domain Email Setup – Domain Verification Process (CRM)
Did this answer your question?