SaaS Module for Concord CRM
πŸ‘‰ Get it now!Concord CRM modules Β»
  • πŸ™ŒSaaS module for Concord CRM
  • Getting Started
    • ⚑Requirements
    • πŸ› οΈActivating the module
    • πŸ”ŒConfiguring the module
      • πŸ’»1) Webhost Configuration
        • cPanel
        • Plesk
        • CloudPanel
        • Virtualmin
        • All other / No Panel (nude) setups
        • MySQL Root
      • 🌐2) DNS & SSL Settings
        • cPanel DNS settings for Wildcard Subdomain + SSL Support
        • Plesk DNS settings for Wildcard Subdomain + SSL Support
        • CloudFlare DNS settings for Wildcard Subdomain + SSL Support
        • All other providers / Self hosted
      • βš™οΈ3) Module's General Settings
      • πŸ”—4) Module's Integration Settings
  • How to use saas module
    • 🎯Creating a quota
    • πŸ“¦Creating a package
    • πŸ›οΈTenant Self-Registration (frontend)
    • πŸ—οΈCreating a Tenant (backend)
    • ✏️Editing a Tenant
    • ❌Deleting a Tenant
    • 🌐Custom Domain support
    • Common Tenant operations
    • πŸ“„Page & template management
    • πŸ“¦Invoice Module Integration – Enabling monitization features
Powered by GitBook
On this page
  1. Getting Started
  2. Configuring the module
  3. 2) DNS & SSL Settings

CloudFlare DNS settings for Wildcard Subdomain + SSL Support

The Cloudflare Integration enables automated DNS management for your SaaS tenants using wildcard subdomains (e.g., *.yourcrm.com). This setup simplifies tenant provisioning by eliminating the need to manually configure DNS records for every new tenant.


🌐 Why Use Wildcard Subdomains with Cloudflare?

Wildcard subdomains allow all tenants (e.g., client1.yourcrm.com, client2.yourcrm.com) to be routed through a single DNS rule. With Cloudflare, you can leverage this feature to:

  • Reduce DNS configuration time.

  • Eliminate the need to manually add A or CNAME records per tenant.

  • Ensure fast, secure, and automated DNS propagation.


πŸ”§ Prerequisites

Before using Cloudflare integration, make sure you have:

  • A verified Cloudflare account.

  • Your domain (e.g., yourcrm.com) added and pointing to Cloudflare’s nameservers.

  • A Cloudflare API token or Global API Key with permission to manage DNS records.

  • A wildcard subdomain (*.yourcrm.com) DNS record set up in your Cloudflare dashboard.


βš™οΈ How It Works

When Cloudflare integration is enabled and a wildcard subdomain is configured:

  1. The SaaS system assigns subdomains to tenants (e.g., tenant1.yourcrm.com, tenant2.yourcrm.com).

  2. The wildcard DNS record (*.yourcrm.com) already covers all such subdomains.

  3. No additional DNS record needs to be added for each tenant.

  4. Tenants can instantly access their subdomain upon successful provisioning.


πŸ“„ Recommended DNS Setup on Cloudflare

  1. Go to your domain in the Cloudflare Dashboard.

  2. Navigate to the DNS tab.

  3. Add the following A Record:

    Type: A
    Name: *
    IPv4 address: <Your server's IP>
    Proxy status: Proxied (recommended)
    TTL: Auto
  4. (Optional) Add an A Record for the root domain as well (@ β†’ IP).

This configuration ensures that any subdomain like client1.yourcrm.com automatically routes to your server.


🧠 Best Practices

  • Use SSL/TLS Full or Full (Strict) in Cloudflare for encrypted connections to your server.

  • Pair with CPanel Integration setup for fully automated provisioning.

  • Set proper Page Rules or Firewall Rules if tenants are to be isolated or monitored.


⚠️ Troubleshooting Tips

  • Ensure your server is configured to handle requests for wildcard subdomains (e.g., via Apache VirtualHost or NGINX server block with server_name *.yourcrm.com).

  • Check propagation delays when testing new subdomains.

  • Confirm DNS settings are proxied through Cloudflare if you want caching and protection benefits.

PreviousPlesk DNS settings for Wildcard Subdomain + SSL SupportNextAll other providers / Self hosted

Last updated 2 months ago

πŸ”Œ
🌐