Error 1150 Adding Domain: Domain Validation Failed (No SOA Record)

Error Adding Domain: Domain Validation Failed (No SOA Record)

The Error

When trying to add a domain to your account, you may see an error similar to:

Domain validation failed: No SOA record found for this domain.

This prevents the domain from being added to your hosting plan.

What This Means

Before we accept a domain onto the platform, we perform a basic validation check to confirm the domain actually resolves on the public DNS system. The specific check looks for an SOA (Start of Authority) record — a fundamental DNS record that every active domain must have.

If no SOA record is returned when we query your domain, it tells us one of the following is true:

• The domain has no nameservers set at the registrar.
• The nameservers are set but are not responding (e.g., a nameserver that no longer exists, or a provider whose DNS has been deactivated).
• The domain was recently registered and DNS has not yet propagated.
• The domain is expired, suspended, or in a pending state at the registrar.

Without a working SOA record, the domain effectively doesn't exist on the internet yet, and there's no way for us (or any visitor) to reach it.

Why We Check This

The SOA check prevents a common class of problems:

• Customers adding domains that will never load because DNS isn't configured.
• Tickets later opened reporting "my site doesn't work" when the root cause is a missing DNS zone.
• SSL issuance failures, since Let's Encrypt and other CAs also require working DNS to validate ownership.

Catching this at the "add domain" step means the issue is resolved before it becomes a bigger troubleshooting problem downstream.

How to Fix It

You have two straightforward options. Choose the one that matches where you want your DNS hosted.

Option 1: Use Your Registrar's Parking / Default DNS

Most registrars offer free "parking" or default DNS service for domains you haven't configured yet. This creates a valid SOA record even if you're not actively using the domain.

1. Log in to your domain registrar.
2. Look for an option like "Use default nameservers", "Park domain", or "Enable basic DNS".
3. Enable it and save.
4. Wait for propagation (usually 15–60 minutes), then retry adding the domain to your account.

This is useful if you want to keep DNS at your registrar but don't yet have specific records to configure.

Option 3: Use a Third-Party DNS Parking Service

If your registrar doesn't offer parking name servers:

1. Update your domain's nameservers at the registrar to point to ns1.sedoparking.com and ns2.sedoparking.com
2. Wait for propagation, then retry adding the domain to LaunchCDN.

How to Verify the Fix

Before retrying, you can confirm the SOA record is in place using any of these tools:

• Command line (Linux/Mac): dig SOA yourdomain.com +short
• Command line (Windows): nslookup -type=SOA yourdomain.com
• Web-based: Any public DNS lookup tool that supports SOA queries, such as DNSResults.com.

A working SOA response will return a single line containing the primary nameserver, the zone administrator email (with the @ replaced by a dot), and several numeric values (serial, refresh, retry, expire, minimum TTL).

If the command returns nothing or an error, DNS still isn't ready — wait longer or re-check your nameserver configuration at the registrar.

Special Cases

Recently Registered Domains

If you registered the domain within the last few hours, DNS may still be propagating globally. Wait 1–4 hours and try again. Some TLDs propagate faster than others.

Expired or Suspended Domains

If the domain has expired or been suspended by the registrar, no DNS configuration will bring it back until the registration issue is resolved. Check the domain status with a WHOIS lookup — look for statuses like clientHold, pendingDelete, or redemptionPeriod.

Domains Using DNSSEC

In rare cases, a misconfigured DNSSEC setup can cause SOA lookups to fail at validating resolvers. If you've recently enabled DNSSEC and are seeing this error, verify the DS records at your registrar match the keys at your DNS provider.

Still Stuck?

If you've followed the steps above and you're confident DNS is configured correctly, open a ticket and include:

• The exact domain name you're trying to add.
• Where DNS is currently hosted (registrar, Cloudflare, etc.).
• The output of dig SOA yourdomain.com +short or equivalent.

We'll investigate from our end and help get the domain onto your account.