Why Is My Custom Domain Not Verified in Feedspace?

Common Reasons Your Custom Domain Is Not Verified

After adding your subdomain in Feedspace and clicking Verify Domain, verification can fail for several reasons. Work through each cause below to find and fix the issue.

1. DNS has not propagated yet

This is the most common reason. When you add a CNAME record to your DNS, that change does not appear instantly across the internet. Propagation can take anywhere from a few minutes to 48 hours depending on your domain registrar and the TTL (time-to-live) value on the record. If you just added the record, wait at least 30 minutes before trying to verify again, and allow up to 48 hours before assuming something is wrong.

2. CNAME record entered incorrectly

A typo in either the host name or target value will prevent verification. Go back to Feedspace Custom Domain settings and copy the exact host name and target value shown there. Then log in to your domain registrar and compare what you entered against those values. Even a single extra character or a missing dot at the end of the target can cause a mismatch.

Common mistakes include:

• Entering the full subdomain (e.g., reviews.yourdomain.com) in the Host field instead of just the subdomain prefix (reviews). Many registrars automatically append the root domain.
• Missing a trailing dot on the target value if your registrar requires FQDN format.
• Pasting in extra spaces or invisible characters around the value.

3. CNAME added to the wrong domain or zone

If you own multiple domains or your account is split across zones, it is possible to add the CNAME record to the wrong domain entirely. For example, if your subdomain is reviews.yourdomain.com, the CNAME must be added to the DNS zone for yourdomain.com, not to a different domain you also manage. Double-check that you are editing the correct zone in your registrar’s DNS panel.

4. A conflicting A or AAAA record exists for the same subdomain

If an A record or AAAA record already exists for the subdomain you are trying to use (for example, a record left over from a previous hosting setup), it can conflict with the CNAME record. Most DNS providers will either reject the CNAME silently or serve the A/AAAA record instead, causing verification to fail. Log in to your registrar’s DNS panel and check whether an A or AAAA record exists for the same host name. If one does, delete it before saving the CNAME record.

5. Registrar propagation is slower than expected

Some domain registrars and DNS hosting providers are known to propagate changes more slowly than others. If you have confirmed the CNAME record looks correct in your registrar’s panel but it is not yet visible externally, this is likely the cause. You can check whether the record has propagated from your registrar’s servers using a DNS checker tool (see below). If the record is still not visible after 24 hours, contact your registrar’s support team to ask about propagation status.

How to Check If Your CNAME Has Propagated

Use a free DNS lookup tool such as dnschecker.org to see whether your CNAME record is visible from multiple locations around the world.

1. Go to dnschecker.org.
2. Enter your full subdomain (e.g., reviews.yourdomain.com) in the search box.
3. Select CNAME from the record type dropdown.
4. Click Search and review the results from different locations.
5. If the CNAME target value matches what Feedspace provided and most locations show a green tick, return to Feedspace Custom Domain settings and click Verify Domain again.

Still Not Verified?

If the CNAME is visible in dnschecker.org but verification still fails in Feedspace, double-check that the target value shown in Feedspace Custom Domain settings exactly matches what your CNAME points to. If everything looks correct and more than 48 hours have passed since you added the record, contact Feedspace support and include your subdomain and a screenshot from dnschecker.org so the team can investigate further.