Skip to main content

How to Add a Primary Domain or Subdomain in DNSPod?

Overview​

This guide will show you how to add a root domain or subdomain in DNSPod and configure the DNS records required by uSpeedo, including:

  • SPF
  • DKIM
  • MX
  • DMARC

Prerequisite: You already have a DNSPod account.

If you encounter issues during configuration, contact DNSPod official support for assistance.

I. Choose Root Domain or Subdomain​

Before you start, decide whether to use a root domain or a subdomain.

Examples​

  • Root Domain:
    • example.com
    • google.com
  • Subdomain:
    • mail.example.com
    • sc.example.com

Recommendation​

👉 In most cases, using a subdomain as the sending domain is recommended.

After confirmation:

  1. Add the domain in the uSpeedo Console
  2. The system will generate the corresponding DNS records

II. Add Domain to DNSPod​

Method 1: Register a New Domain​

  1. Log in to DNSPod
  2. Go to Domain Management
  3. Click Add Domain
  4. Enter the domain and complete registration

If your domain is registered with another registrar:

  1. Log in to DNSPod
  2. Add the domain
  3. Obtain the NS records provided by DNSPod
  4. Update the NS servers at your original registrar

III. Configure DNS Records​

Path:

  1. Log in to DNSPod
  2. Domain Management → Select your domain
  3. Click Manage
  4. Click Add Record

IV. SPF Configuration​

Purpose​

Prevent sender spoofing and improve deliverability.

Root Domain SPF​

FieldValue
TypeTXT
Host Record@
Valuev=spf1 include:sendcloud.org ~all
TTL600

📌 Note: If an SPF record already exists: 👉 Insert the following between v=spf1 and ~all: include:sendcloud.org

Subdomain SPF​

FieldValue
TypeTXT
Host RecordSubdomain prefix (e.g., sc)
Valuev=spf1 include:sendcloud.org ~all
TTL600

V. DKIM Configuration​

Purpose​

Verify email signatures and prevent spoofing.

Root Domain DKIM​

FieldValue
TypeTXT
Host Recordsendcloud._domainkey
Valuek=rsa; p=your_public_key
TTL600

📌 Note: The selector may vary, such as:

  • default._domainkey
  • sc._domainkey 👉 You must use the value provided in the console.

Subdomain DKIM​

FieldValue
TypeTXT
Host Recordsendcloud._domainkey.sc
Valuek=rsa; p=your_public_key
TTL600

VI. MX Record Configuration​

Purpose​

Designate the mail servers responsible for receiving emails.

Root Domain MX​

FieldValue
TypeMX
Host Record@
Valuemx.sendcloud.org
Priority10
TTL600

📌 Note: 👉 Do not keep other MX records simultaneously (conflicts will occur).

Subdomain MX​

FieldValue
TypeMX
Host RecordSubdomain prefix
Valuemx.sendcloud.org
Priority10
TTL600

VII. DMARC Configuration​

Purpose​

Prevent fraudulent emails and enforce policy controls.

Root Domain DMARC​

FieldValue
TypeTXT
Host Record_dmarc
Valuev=DMARC1; p=none; rua=mailto:xxx; ruf=mailto:xxx; fo=1
TTL600

Parameter Explanation​

  • v=DMARC1: Protocol version
  • p=none: Monitor mode
  • p=quarantine: Quarantine the email
  • p=reject: Reject the email directly
  • rua: Aggregate reports
  • ruf: Forensic reports
  • fo=1: Trigger on failure

Subdomain DMARC​

FieldValue
TypeTXT
Host Record_dmarc.sc
Valuev=DMARC1; p=none; rua=mailto:xxx
TTL600

VIII. NS (Nameserver) Explanation​

If you are migrating DNS services: 👉 You must update the NS records at your domain registrar.

Otherwise: ❌ uSpeedo will be unable to verify the domain.

IX. Notes​

  • DNS records must match those provided in the console (examples are for reference only)
  • Propagation time: several minutes to several hours
  • Recommended TTL: 300–600
  • TTL can be increased after records take effect

X. FAQ​

1. Verification failed?​

Check:

  • Whether NS records have been switched
  • Whether records match exactly
  • Whether conflicting records exist

👉 Isolate sending reputation Avoid impacting the root domain (official website / brand)