Set Up & Troubleshoot DNS and SSL for Flipsnack Domains

This article explains common DNS setup steps, typical issues, and expected timelines for DNS propagation when configuring a custom domain and SSL for Flipsnack-hosted publications.

Summary

• Covers the DNS records and verification steps for a custom domain, expected verification timelines, frequent causes of setup failure, and practical troubleshooting actions.

DNS setup checklist (key steps)

1. In Flipsnack: go to Branding > Brand profile > Settings > Custom domain and enter the subdomain or domain (for example, flipbooks.yourcompany.com).
2. In your DNS provider (GoDaddy, Cloudflare, etc.):
   • Create a CNAME record for the chosen subdomain.
   • Point the CNAME value to the provided target (example format: custom.cloudfront.net).
   • If your DNS provider supports proxying (e.g., Cloudflare), disable proxy and set the record to DNS only.
3. Back in Flipsnack: click Verify status to trigger verification.

Expected timelines

• Verification in Flipsnack may update in about 5 minutes after the correct DNS record is in place.
• Allow up to 48 hours for DNS propagation in some cases.

Common issues and causes

• DNS record not set exactly as instructed (incorrect host or value).
• Proxying turned on at the DNS provider (Cloudflare “proxied” mode) instead of DNS-only.
• DNS propagation delays causing a pending status for up to 48 hours.
• SSL certificate problems when importing your own certificate:
  • Public certificate and private key do not match.
  • Private key is encrypted (it must be unencrypted).
  • Wrong file formatting or unsupported encryption.
• Switching between SSL types can require resetting the CNAME record.
• Automated review processes may flag a domain or publication and leave the domain in pending status until a manual check completes.

Verification and validation tips

• Use a DNS lookup tool (for example, Google DIG) to confirm the CNAME points to the exact value provided by Flipsnack.
• After correcting DNS settings, use the Verify status button in Flipsnack; the status may change in about 5 minutes if records are correct.
• If verification remains pending after allowing time for propagation and confirming DNS, consider redoing the setup from scratch: remove the custom domain settings in both Flipsnack and your DNS provider, then recreate them.

Troubleshooting steps (ordered)

1. Double-check the CNAME record:
   • Confirm the host/subdomain and the CNAME value match Flipsnack’s instructions exactly.
2. Ensure proxying is disabled:
   • For Cloudflare and similar services, set the CNAME record to DNS only (disable the proxy).
3. Verify DNS propagation:
   • Use a DNS tool (e.g., Google DIG) to see whether the CNAME resolves to the expected value.
   • Wait up to 48 hours for global propagation if needed.
4. For SSL import issues:
   • Ensure the public certificate and private key match.
   • Upload an unencrypted private key in the correct format.
   • Verify any intermediate certificate chain is provided if required.
5. If persistent failure:
   • Remove the custom domain entries in both Flipsnack and your DNS provider, then repeat the setup steps.
6. If status remains pending and all technical checks are correct:
   • Be aware the domain may be under automated/manual review; allow time for that review to complete.

When to contact support

• If you’ve verified DNS and SSL files are correct, disabled proxying, allowed sufficient propagation time (up to 48 hours), retried the setup, and the domain still does not verify or remains pending, gather the details of the steps you tried and contact support for further assistance.

Conclusion Follow the exact CNAME values and ensure proxying is disabled, then use Verify status in Flipsnack. Verification often completes within minutes but can take up to 48 hours due to DNS propagation. Common failures relate to incorrect DNS entries, proxying, and SSL certificate/key mismatches; redoing the setup and validating with a DNS lookup tool are effective first troubleshooting steps.