Managing Domains

This guide walks through the complete DNS configuration process for custom domains, including troubleshooting common issues and verifying domain ownership.

DNS Records Overview

When you add a custom domain to daimon.email, you'll need to configure six DNS records:

Step-by-Step DNS Configuration

1. Get Your DNS Records

After adding your domain, retrieve the DNS records to configure:

curl -X GET https://api.daimon.email/v1/domains/dom_abc123 \
  -H "Authorization: Bearer dm_live_account123..."

const domain = await client.domains.get('dom_abc123');

console.log('Configure these DNS records:');
domain.dnsRecords.forEach(record => {
  console.log(`${record.type} ${record.name} → ${record.value}`);
});

domain = client.domains.get('dom_abc123')

print('Configure these DNS records:')
for record in domain.dns_records:
    print(f"{record.type} {record.name} → {record.value}")

2. Configure MX Records

MX records tell the internet where to send emails for your domain.

Add these two MX records:

3. Configure SPF Record

SPF (Sender Policy Framework) authorizes daimon.email to send emails on behalf of your domain.

Add this TXT record:

Example: Merging SPF records

Existing SPF:

v=spf1 include:_spf.google.com ~all

Updated SPF (with daimon.email):

v=spf1 include:_spf.google.com include:_spf.daimon.email ~all

4. Configure DKIM Record

DKIM (DomainKeys Identified Mail) cryptographically signs outbound emails to prove they came from daimon.email.

Add this TXT record:

5. Configure DMARC Record

DMARC (Domain-based Message Authentication) sets policy for emails that fail SPF or DKIM checks.

Add this TXT record:

DMARC Policies:

• p=none: Monitor failures but deliver all emails (recommended for testing)
• p=quarantine: Send failing emails to spam (recommended for production)
• p=reject: Reject failing emails entirely (most strict)

6. Configure Ownership Verification Record

daimon.email requires a unique verification TXT record to prove you own the domain.

Add this TXT record:

Verification Process

Automatic Verification

Once you've configured all DNS records, daimon.email automatically checks them every 5 minutes. Verification typically completes within 5-30 minutes after DNS propagation.

Check Verification Status

Poll the domain status to see verification progress:

curl -X GET https://api.daimon.email/v1/domains/dom_abc123 \
  -H "Authorization: Bearer dm_live_account123..."

const domain = await client.domains.get('dom_abc123');

console.log('Verification status:', domain.verificationStatus);
console.log('MX verified:', domain.mxVerified);
console.log('SPF verified:', domain.spfVerified);
console.log('DKIM verified:', domain.dkimVerified);
console.log('DMARC verified:', domain.dmarcVerified);
console.log('Ownership verified:', domain.ownershipVerified);

if (domain.verificationStatus === 'verified') {
  console.log('✅ Domain is ready! You can now create inboxes.');
} else {
  console.log('⏳ Waiting for DNS propagation...');
}

domain = client.domains.get('dom_abc123')

print(f"Verification status: {domain.verification_status}")
print(f"MX verified: {domain.mx_verified}")
print(f"SPF verified: {domain.spf_verified}")
print(f"DKIM verified: {domain.dkim_verified}")
print(f"DMARC verified: {domain.dmarc_verified}")
print(f"Ownership verified: {domain.ownership_verified}")

if domain.verification_status == 'verified':
    print('✅ Domain is ready! You can now create inboxes.')
else:
    print('⏳ Waiting for DNS propagation...')

{
  "result": {
    "id": "dom_abc123",
    "domain": "yourcompany.com",
    "verification_status": "verified",
    "mx_verified": true,
    "spf_verified": true,
    "dkim_verified": true,
    "dmarc_verified": true,
    "ownership_verified": true,
    "verified_at": "2026-03-16T10:45:00Z",
    "last_checked_at": "2026-03-16T10:45:00Z"
  }
}

Manual Verification Trigger

If you want to force an immediate verification check (instead of waiting 5 minutes):

curl -X POST https://api.daimon.email/v1/domains/dom_abc123/verify \
  -H "Authorization: Bearer dm_live_account123..."

Troubleshooting

DNS Propagation is Slow

DNS changes can take 5 minutes to 48 hours to propagate globally, depending on your DNS provider and TTL settings.

Check DNS propagation:

Use these tools to verify your DNS records are visible:

• Google DNS Checker
• WhatsMyDNS
• MXToolbox

Example: Check MX records

dig MX yourcompany.com +short

Expected output:

10 mx1.daimon.email.
20 mx2.daimon.email.

Verification Failed: MX Records

Error:

{
  "mx_verified": false,
  "mx_error": "No MX records found pointing to mx1.daimon.email"
}

Solutions:

1. Check that you added both MX records (mx1 and mx2)
2. Ensure @ or blank name (for root domain), not www
3. Verify priority values: 10 and 20
4. Wait for DNS propagation (5-30 minutes)
5. Check with dig MX yourcompany.com

Verification Failed: SPF Record

Error:

{
  "spf_verified": false,
  "spf_error": "SPF record does not include daimon.email"
}

Solutions:

1. Ensure SPF record starts with v=spf1
2. Check that include:_spf.daimon.email is present
3. If you have an existing SPF record, merge it (don't create a second SPF record)
4. Ensure SPF record ends with ~all or -all
5. Check with dig TXT yourcompany.com and look for v=spf1

Verification Failed: DKIM Record

Error:

{
  "dkim_verified": false,
  "dkim_error": "DKIM public key not found at daimon._domainkey.yourcompany.com"
}

Solutions:

1. Ensure record name is exactly daimon._domainkey (not @ or blank)
2. Copy the exact DKIM value from the API response
3. Some providers require quotes around the value: "v=DKIM1; k=rsa; p=..."
4. Check with dig TXT daimon._domainkey.yourcompany.com

Verification Failed: DMARC Record

Error:

{
  "dmarc_verified": false,
  "dmarc_error": "No DMARC record found at _dmarc.yourcompany.com"
}

Solutions:

1. Ensure record name is exactly _dmarc (not @ or blank)
2. Ensure value starts with v=DMARC1;
3. Check with dig TXT _dmarc.yourcompany.com

Verification Failed: Ownership

Error:

{
  "ownership_verified": false,
  "ownership_error": "Verification code not found in TXT records"
}

Solutions:

1. Ensure verification TXT record is at @ (root domain)
2. Copy the exact verification code from the API response
3. Wait for DNS propagation
4. Check with dig TXT yourcompany.com and look for daimon-verification=

Managing Domains

List All Domains

curl -X GET https://api.daimon.email/v1/domains \
  -H "Authorization: Bearer dm_live_account123..."

{
  "result": {
    "domains": [
      {
        "id": "dom_abc123",
        "domain": "yourcompany.com",
        "verification_status": "verified",
        "verified_at": "2026-03-16T10:45:00Z"
      },
      {
        "id": "dom_def456",
        "domain": "agents.yourcompany.com",
        "verification_status": "pending",
        "created_at": "2026-03-16T11:00:00Z"
      }
    ],
    "total": 2
  }
}

Delete a Domain

curl -X DELETE https://api.daimon.email/v1/domains/dom_abc123 \
  -H "Authorization: Bearer dm_live_account123..."

Next Steps