GET
/
api
/
v2
/
domains
/
{id}
/
dns-records
curl -X GET 'https://inbound.new/api/v2/domains/dom_abc123/dns-records' \
  -H 'Authorization: Bearer YOUR_API_KEY'

{
  "domainId": "dom_abc123",
  "domain": "example.com",
  "records": [
    {
      "id": "dns_rec_001",
      "domainId": "dom_abc123",
      "recordType": "TXT",
      "name": "_amazonses.example.com",
      "value": "abc123def456ghi789jkl",
      "priority": null,
      "isRequired": true,
      "isVerified": true,
      "lastChecked": "2024-01-15T10:30:00Z",
      "createdAt": "2024-01-01T00:00:00Z",
      "updatedAt": "2024-01-01T00:00:00Z"
    },
    {
      "id": "dns_rec_002",
      "domainId": "dom_abc123",
      "recordType": "MX",
      "name": "example.com",
      "value": "10 inbound-smtp.us-east-1.amazonaws.com",
      "priority": null,
      "isRequired": true,
      "isVerified": false,
      "lastChecked": "2024-01-15T10:25:00Z",
      "createdAt": "2024-01-01T00:00:00Z",
      "updatedAt": "2024-01-01T00:00:00Z"
    }
  ]
}

​
Overview

This endpoint retrieves all DNS records that are required for domain verification. It includes both the records that need to be added to your DNS provider and their current verification status.

​
Authentication

​
Authorization
string
required
Bearer token for API authentication. Format: Bearer YOUR_API_KEY

​
Parameters

​
id
string
required
The unique identifier of the domain to retrieve DNS records for.

​
Response

​
domainId
string
required
The unique identifier of the domain.
​
domain
string
required
The domain name (e.g., “example.com”).
​
records
array
required
Array of DNS records required for domain verification.

​
Examples

​
Request

curl -X GET 'https://inbound.new/api/v2/domains/dom_abc123/dns-records' \
  -H 'Authorization: Bearer YOUR_API_KEY'

​
Response

{
  "domainId": "dom_abc123",
  "domain": "example.com",
  "records": [
    {
      "id": "dns_rec_001",
      "domainId": "dom_abc123",
      "recordType": "TXT",
      "name": "_amazonses.example.com",
      "value": "abc123def456ghi789jkl",
      "priority": null,
      "isRequired": true,
      "isVerified": true,
      "lastChecked": "2024-01-15T10:30:00Z",
      "createdAt": "2024-01-01T00:00:00Z",
      "updatedAt": "2024-01-01T00:00:00Z"
    },
    {
      "id": "dns_rec_002",
      "domainId": "dom_abc123",
      "recordType": "MX",
      "name": "example.com",
      "value": "10 inbound-smtp.us-east-1.amazonaws.com",
      "priority": null,
      "isRequired": true,
      "isVerified": false,
      "lastChecked": "2024-01-15T10:25:00Z",
      "createdAt": "2024-01-01T00:00:00Z",
      "updatedAt": "2024-01-01T00:00:00Z"
    }
  ]
}

​
Error Responses

{
  "error": "Domain not found"
}

​
DNS Record Types

The following DNS record types are commonly used for domain verification:

​
TXT Records

Used for domain verification and AWS SES identity verification. 
Name: _amazonses.example.com
Value: abc123def456ghi789jkl

​
MX Records

Used to route emails to the correct mail servers. 
Name: example.com
Value: 10 inbound-smtp.us-east-1.amazonaws.com
Priority: 10

​
CNAME Records

Sometimes used for specific subdomain configurations. 
Name: mail.example.com
Value: inbound-smtp.us-east-1.amazonaws.com

​
Verification Status

Each DNS record has a verification status that indicates whether it’s properly configured:
1

Not Verified (isVerified: false)

The DNS record has not been verified yet or is incorrectly configured.
Check that the record has been added to your DNS provider with the exact name and value.
2

Verified (isVerified: true)

The DNS record has been verified and is correctly configured.
This record is properly set up and contributing to domain verification.

​
Common DNS Configuration

Here’s how to configure the most common DNS records:

​
Adding TXT Records

  1. Log into your DNS provider (Cloudflare, GoDaddy, etc.)
  2. Navigate to DNS management
  3. Add a new TXT record with the exact name and value provided
  4. Save the changes

​
Adding MX Records

  1. Remove any existing MX records for the domain
  2. Add the new MX record with the provided hostname and priority
  3. Ensure no conflicting MX records exist

​
Important Notes

DNS propagation can take up to 24 hours, but typically completes within 1-2 hours. Check the lastChecked timestamp to see when verification was last attempted.
Use the domain’s GET endpoint with check=true to trigger a real-time verification check of all DNS records.
All required DNS records must be verified before the domain can receive emails. Missing or incorrect records will prevent email delivery.

​
Troubleshooting

If DNS records are not verifying:
  1. Check DNS propagation: Use online DNS lookup tools to verify records are visible
  2. Verify exact values: Ensure the name and value match exactly (case-sensitive)
  3. Remove conflicting records: Delete any existing MX or CNAME records that might conflict
  4. Wait for propagation: DNS changes can take time to propagate globally
  • Trigger verification check: GET /api/v2/domains/{id}?check=true
  • View domain status: GET /api/v2/domains/{id}
  • List all domains: GET /api/v2/domains

​
Notes

  • DNS records are automatically created when a domain is added
  • The isVerified status is updated during verification checks
  • All required records must be verified for the domain to become active
  • DNS records are automatically deleted when a domain is removed
  • Record verification happens automatically but can be triggered manually