Setting Up And Maintaining Cloudflare With Znode

TABLE OF CONTENTS

Cloudflare Processes

Processes that should be followed to initially assist Amla with setting up Cloudflare and (indirectly) assist with maintaining proper Cloudflare configuration on an ongoing basis.

Initial Setup

With a Znode SaaS license, the production Znode environment will automatically come with Cloudflare as an edge service. To allow this to be configured, some information must be provided to Amla.

DNS Handoff Initiation

In order for Cloudflare to provide all of the benefits of an edge service, Cloudflare needs to be configured as the DNS provider for the store’s domain. Please provide Amla with the following:

  • Provide Amla with overall confirmation that having Cloudflare provide their DNS, and having Amla administer this is acceptable.

  • Provide Amla with the domain name on which Znode will be hosted. 

    • For example znodestore.com

  • Provide Amla with the DNS list of any and all existing DNS records that must be properly migrated to Cloudflare. Note that these records should migrate into Cloudflare automatically, but this list serves as a secondary validation.

    • For example:

      • erp.znodestore.com is an A record that points to 120.47.200.151

      • crm.znodestore.com is a CNAME record that points to znodestore.crmsystem.com

      • mail.znodestore.com is an MX record that points to abc.xyz.com


Nameserver Updation

After providing the previous information to Amla, Amla will later provide multiple new Cloudflare nameservers that must be configured for the store’s domain. Any existing nameservers must be removed, and Cloudflare’s nameservers must be added. Perform this configuration in the domain registrar that the domain belongs to (GoDaddy, Domain.com, Namecheap, etc.).

After updating the name servers in the domain registrar, notify Amla so that they can monitor the updation process from the Cloudflare side.

DNS Migration Validation

After updating the nameservers in the domain registrar, some period of time is required before the changes will propagate. The duration that this takes varies depending on the domain registrar and other factors, but this is typically a 24-48 hour window.

Amla will provide confirmation that the Cloudflare nameservers have taken effect once the changes have propagated.

At this point, it is critical that all of the customer’s systems that rely on the migrated DNS records be tested by the customer and verified to still be functioning properly. Issues are not expected, but if any problems do arise, notify Amla of exactly what is being observed and they will work to resolve any issues with DNS records in Cloudflare.

Ongoing Operational Processes

Znode should automatically purge the Cloudflare cache when the Cloudflare setting is ‘On’ for the store and the ZnodeId is provided.  However, if any issues are noticed where it is suspected that stale items are being held in the Cloudflare cache, then a manual purge can be triggered. Details for doing this are in the knowledge base article Global Settings, Refresh Cloudflare Cache section.

Ongoing Custom Dev Support Process

Cloudflare will cache all HTML responses from the Znode WebStore except those known to be unsuitable for caching. This includes user-specific data such as the shopping cart. To blacklist such items from being cached by Cloudflare, the URL must be configured as non-cacheable by Amla.

All out-of-the-box non-cacheable items will automatically be handled. Any custom endpoints added that are non-cacheable must be submitted to Amla for proper configuration.

For example: A custom endpoint is introduced that renders a snippet of HTML with some user-specific information such as a custom “Reward Balance” functionality. The URL of this endpoint should be provided to Amla for it to be configured as non-cacheable in Cloudflare.

Ongoing Admin/Shopper User Issue Support Process

Cloudflare provides certain firewall and rate limiting mechanisms to help prevent malicious attacks on the site. Such mechanisms are valuable but at the same time can provide false positives. If any well-intentioned users are having issues using the Znode site and this is thought to be the reason, submit a request to Amla with information about the occurrence so that measures can be taken to resolve the issue.

For example:

  • The QA team is performing a load test against the Znode site during off-hours and Cloudflare rate-limiting rules seem to be blocking further requests from that IP address.

  • A remote development team working on Znode from a foreign country is having trouble accessing the Znode site and firewall rules seem to be blocking requests from that country.

Ongoing DNS Support Process

If additional DNS records are desired on the domain that Znode is hosted, then additional records can be configured in Cloudflare by the Amla team.

Submit requests for any such DNS records to Amla, with details of the subdomain, record type, and value (IP address or domain address).

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.