Skip to content
  • There are no suggestions because the search field is empty.

Troubleshooting DNS Setup and Propagation for Custom Domains

See what usually goes wrong with CNAME values, proxy settings, and SSL certificates, plus how long DNS changes take to take effect.

Summary This article explains common issues that can occur during DNS setup and propagation for a custom domain or subdomain, typical timelines for DNS changes to take effect, and practical verification and troubleshooting steps.

Common issues during DNS setup

  • Incorrect CNAME values: The CNAME record must point exactly to the value provided (for example, custom.cloudfront.net). A misspelled host or value prevents verification.
  • Proxy/SSL services enabled on the DNS provider: If using services like Cloudflare, ensure the CNAME proxy is disabled (set to DNS only).
  • Switching SSL types: Changing between using Flipsnack’s SSL and importing your own certificate may require resetting the CNAME record.
  • Certificate errors when importing SSL:
    • Private key does not match the certificate public key
    • Private key is encrypted (must be unencrypted)
    • Wrong file formatting or unsupported encryption
  • Automated review or manual checks: A domain or publication can remain in pending status if an automated review flagged it for manual checking.

Typical timelines for DNS propagation and verification

  • Flipsnack verification: After adding the CNAME and completing setup, clicking Verify status in Flipsnack may show success in about 5 minutes.
  • DNS propagation: Allow time for DNS propagation; it can sometimes take up to 48 hours for new DNS records to take effect.

Verification and troubleshooting steps

  1. Confirm DNS record values

    • In your DNS provider, create a CNAME record with:
      • Host: your chosen subdomain (e.g., flipbooks)
      • Value: the exact value provided (for example, custom.cloudfront.net)
    • Disable any proxy feature (set the record to DNS only).

  2. Verify DNS propagation

    • Use a DNS lookup tool (for example, Google DIG) to confirm the CNAME resolves to the correct value.

  3. Retry verification in Flipsnack

    • In Brand settings > Custom domain, click Verify status after DNS is updated. Verification can complete in ~5 minutes once DNS is visible.

  4. If SSL import fails

    • Ensure the certificate public key and private key match and that the private key is unencrypted.
    • Check file formats and encryption types are supported.
    • If switching from a custom certificate back to Flipsnack’s SSL, reset the CNAME if required.

  5. Recreate the setup if problems persist

    • Remove the custom domain settings from both Flipsnack and your DNS provider, then repeat the setup from scratch.

  6. When to contact support

    • If verification remains pending for more than a few hours after you have confirmed DNS and SSL settings, contact support with details of what you tried. Live chat availability (for real-time help) is Monday–Friday, 6:00 AM–11:00 PM GMT.

Troubleshooting tips — quick checklist

  • Double-check for typos in the CNAME host and value.
  • Ensure proxy is disabled on DNS records (DNS only).
  • Use a DNS lookup tool to confirm propagation before clicking Verify.
  • Verify SSL files: matching keys, unencrypted private key, correct formats.
  • If switching SSL methods, reset the CNAME and redo verification.
  • If automated review flagged the domain, allow a few hours for manual checks.

Conclusion Ensure the CNAME exactly matches the value provided, set the DNS record to DNS only (disable proxy), and verify with a DNS lookup tool. Flipsnack’s verification often completes in about five minutes after DNS is visible, but DNS propagation can take up to 48 hours. If issues persist after following the verification and troubleshooting steps, contact support during live chat hours with details of the steps you’ve taken.