1. Add Your Subdomain in Searcle
In Searcle → Hosting, you will see two CNAME records:
CNAME #1 - Content Record
Connects your subdomain (e.g., ai) to Searcle’s servers.
CNAME #2 - SSL Verification Record
Each record includes:
Field | Meaning |
Type | CNAME |
Name | The hostname to create (e.g., ai) |
Value | Searcle’s target - copy exactly |
2. Add the DNS Records (Namecheap, GoDaddy, Cloudflare, etc.)
Wherever your domain is registered, follow these steps:
Log into your domain provider’s DNS settings
(“DNS,” “Zone Editor,” or “Manage Domain”)Click Add Record → CNAME
Add both CNAME records from Searcle:
Content CNAME
SSL Verification CNAME
Save your changes
This works the same across major providers:
Provider | Where to Edit DNS |
Namecheap | Domains → Manage → Advanced DNS |
GoDaddy | My Products → DNS |
Cloudflare | DNS tab (set records to DNS Only) |
IONOS | Domains & SSL → DNS |
Google Domains | DNS → Custom Records |
Bluehost / DreamHost / Others | “DNS” or “Zone Editor” |
⚠️ Important: Do NOT Modify Existing Records
Do NOT delete the following (on any provider):
Your root A record (this hosts your main website)
Any existing MX (email) records
Any existing CNAME for “www” (unless you intend to replace it)
Any TXT or verification records for Google Workspace, Microsoft 365, etc.
Your new Searcle subdomain is additional — it does not replace your existing website.
3. Verify the DNS Setup
After adding the two CNAMEs:
Go back to Searcle → Hosting
Click Verify DNS configuration
If everything is correct, the subdomain will go live.
⏱ DNS Propagation Timing
Often: 5–30 minutes
Sometimes: 1–4 hours
Worst case: 24–48 hours
If verification fails, wait and try again later — propagation may still be in progress.
4. Safety Tips (Across All DNS Providers)
🔐 SSL / HTTPS Tips
The SSL CNAME must stay in place; removing it will break HTTPS.
Cloudflare users: set both records to DNS Only (Grey Cloud) — not proxied.
🔁 CNAME Rules Across All Providers
These rules are universal:
A CNAME cannot coexist with any other record on the same hostname
(e.g., you cannot have both a CNAME and an A record forai)A CNAME must point to a hostname, not an IP address
You cannot put a CNAME on the root domain (
yourcompany.com)
⏲ TTL Best Practices
Most providers default to 1 hour, which is fine.
If you can set TTL, choose 30 minutes – 1 hour.
🛡 CAA Records
If your domain uses CAA, ensure it includes:
CAA 0 issue "letsencrypt.org"
Without this, HTTPS issuance may fail.
5. Troubleshooting Across Providers
❌ Verification failing?
DNS record not yet propagated
Incorrect “Name” field
Extra whitespace or missing characters
CNAME added to wrong domain
Cloudflare record is proxied
Another record already exists with that hostname
CAA blocks Let's Encrypt
❌ “Not Secure” HTTPS error?
SSL CNAME missing
DNS still propagating
Cloudflare proxy enabled
6. Need Help?
We can fix DNS issues quickly.
📧 [email protected]
Please include a screenshot of your DNS records.