Custom Domain Not Loading

Your custom domain for Dialora doesn’t load, shows an error, or displays the wrong content.

Symptoms

• Custom domain returns a “DNS resolution failed” or “Cannot resolve” error
• Shows a generic error page instead of your Dialora agent
• Domain works for a while, then suddenly stops working
• Cloudflare shows a DNS error even though you configured the record
• CNAME record appears configured but the domain still doesn’t resolve
• Mixing up SMTP records with domain CNAME records is causing issues

Common Causes

1. Cloudflare proxy enabled (orange cloud) — Dialora requires DNS-only mode; proxying through Cloudflare causes connectivity issues
2. Wrong DNS record type — Using an A record instead of CNAME, or vice versa
3. CNAME not fully propagated — DNS changes can take 24–48 hours to propagate globally
4. Confusing SMTP settings with domain CNAME — Mixing up mail server records with your Dialora domain routing

How to Fix

Step 1: Disable Cloudflare Proxy (Set to DNS Only)

1. Log into your Cloudflare account
2. Navigate to your domain’s DNS settings
3. Find the CNAME record pointing to Dialora (e.g., app.yourdomain.com)
4. Check the cloud icon next to that record:
   • Orange cloud = Proxied (wrong — causes issues with Dialora)
   • Grey cloud = DNS Only (correct)
5. Click the orange cloud icon to toggle it to grey (DNS Only)
6. Save changes
7. Wait 1–2 minutes and try accessing your domain again

Step 2: Verify Your CNAME Record Points to the Correct Dialora Endpoint

1. In your DNS provider (Cloudflare, Route53, GoDaddy, etc.):
2. Find your CNAME record for the Dialora subdomain
3. Confirm it points to the correct Dialora endpoint (provided in your Dialora dashboard):
   • Check Integrations → Custom Domain in Dialora
   • Copy the exact endpoint URL provided
4. Common CNAME setup example:

   Type:  CNAME
   Name:  app
   Value: cname.dialora.io  (or your assigned endpoint)
   TTL:   3600 (or Auto)

5. Ensure there are no extra characters, spaces, or typos in the endpoint
6. If the endpoint differs, delete the old CNAME record and create a new one with the correct value

Step 3: Check DNS Propagation Status

1. DNS changes don’t take effect immediately — they can take 24–48 hours to propagate globally
2. To check propagation status:
   • Visit DNSChecker.org 
   • Enter your domain name (e.g., app.yourdomain.com)
   • Select CNAME as the record type
   • Review results from multiple locations around the world
3. If most locations show your Dialora endpoint: Propagation is working; wait if needed
4. If locations show “NXDOMAIN” or old values: Your DNS change may not have saved correctly; go back to Step 2

Step 4: Separate SMTP Records from Domain CNAME

Do NOT use these records for Dialora:

• Type: MX records (for email routing)
• Type: TXT records for SPF, DKIM (for email authentication)
• SMTP server endpoints

For Dialora domain setup, use ONLY:

• Type: CNAME record pointing to your Dialora endpoint
• OR Type: A record if using an IP address (rare; check Dialora docs)

If you see MX or TXT records where your CNAME should be, delete them and create the correct CNAME record.

Step 5: Test Your Domain

1. After making DNS changes, wait 5–10 minutes (or longer if propagation is slow)
2. Try accessing your domain in an incognito/private browser window to bypass cache
3. If still not loading:
   • Clear your browser cache (Ctrl+Shift+Delete or Cmd+Shift+Delete)
   • Try from a different network or device
   • Check if your ISP’s DNS is caching old records (try using 8.8.8.8 or 1.1.1.1)
4. Once loading, verify the Dialora agent interface appears correctly