Skip to main content

SSL, CDN, and Custom Domains

Overview​

Dotsync provides DNS with built-in CDN and automatic TLS for custom domains. You do not need to configure a CDN or TLS manually — when you add an A, AAAA, or CNAME record in Dotsync you can toggle CDN and TLS for that hostname, and Dotsync will handle provisioning and configuration automatically. This guide explains the usual setup and basic troubleshooting.

Quick setup​

  1. Optional: if you want Dotsync to manage your DNS, point your domain to Dotsync's nameservers (see registering-a-domain.md). Alternatively, keep your existing DNS provider and add the required A/AAAA/CNAME and TXT records there — Dotsync will still provision TLS/CDN for hostnames with correct records.
  2. Create a DNS record for your site (A/AAAA or CNAME) in the Dotsync dashboard. When adding the record you can toggle CDN and TLS — Dotsync will provision certificates and enable caching automatically.
  3. Wait for DNS propagation and certificate provisioning to complete (usually a few minutes; can take longer if DNS is new).

SSL provisioning​

  • TLS certificates are provisioned automatically (ACME / Let’s Encrypt) when you enable TLS for a hostname. In most cases no action is required.
  • For wildcard certificates (*.example.com) or special DNS setups we may need DNS validation; reach out to Dotsync support if you need wildcard coverage.

Common provisioning errors​

  • Domain not pointing to Dotsync: Ensure the A/CNAME is correctly set and propagated.
  • Rate limits by CA: If you request certificates frequently, you may hit CA rate limits; wait or consolidate requests.
  • DNSSEC enabled: In rare cases DNSSEC misconfiguration prevents validation — verify DNSSEC records are correct.

CDN behavior​

  • Dotsync's CDN is built-in and can be enabled by toggling CDN when creating a DNS record for a hostname. Typical sites require no additional CDN setup.
  • If you use your own origin (hosted elsewhere), Dotsync will fetch content from that origin — advanced origin settings are available by request; contact support for custom origin configuration.
  • For most users, simply enabling the CDN is enough; caching rules and advanced headers are handled automatically.

Troubleshooting tips​

  • Check DNS propagation with dig or online tools; verify the A/AAAA/CNAME record is correct and that CDN/TLS toggles are enabled for the hostname.
  • Inspect certificate details in the browser; confirm the issuer and validity period once provisioning completes.
  • If SSL looks self-signed or invalid, check that the certificate has finished provisioning and that intermediates are present.

Best practices​

  • Use HTTP Strict Transport Security (HSTS) carefully — only enable after long-term HTTPS monitoring.
  • Configure appropriate caching headers to maximize CDN effectiveness.

For help with complex setups (multi-tenant, custom origins), contact Dotsync support with your domain and desired configuration.