On December 1st, 2024, custom domains used in place of chili-publish.online or chili-publish-sandbox.online will cease to function if not migrated from Azure Frontdoor to Cloudflare. This guide will help you identify and migrate your custom domains to ensure uninterrupted service.

If you do not use custom domain names, then there is no need to worry about this change.

Identifying Custom Domains

Most CHILI clients do not use custom domains, but some employ them for branding purposes.

Custom domains are any domains that:

1. Do not end in chili-publish.online or chili-publish-sandbox.online

2. Point to your CHILI environment

3. Have a CNAME record pointing to a domain ending in azurefd.net, chili-publish.online, or chili-publish-sandbox.online

Examples of Custom Domains

• https://uk-chili.spicy-labs.com

• https://chili.beercompany.thebigspicy.com

Check for Custom Domains

To successfully configure custom domains for CHILI GraFx, collaboration with your IT or technical teams is essential. The configuration process must be carried out outside of the CHILI GraFx application, specifically through your hosting settings.

Follow this step-by-step guide to check for custom domains:

1. Access your domain registrar, DNS hosting provider's management console, or DNS management service provided by your cloud provider.

2. Look for existing CNAME records that point to domains ending in azurefd.net for your CHILI GraFx integration.

   1. Note: You shouldn't have any CNAME records pointing to chili-publish.online or chili-publish-sandbox.online, but if you do, these should be included in your migration plan.

If you are really uncertain, you can email support@chili-publish.com, and the support team can usually determine if you are using custom domains. Although, the only 100% certain way to know is to check your DNS records.

Example

When looking through my DNS settings, I see a CNAME record for azurefd.net

Open

I can even verify this by typing the address https://uk-chili.spicy-labs.com in my browser and see that CHILI Publisher BackOffice is loaded.

Open

Migration Process

If you have no custom domains, you no longer need to worry as this removal of Azure Front Door will not impact you. However, if you have identified the custom domains, migrating them to Cloudflare should be a relatively straightforward process. However, you will need enlist the assistance of your IT, DevOps team, or a colleague with technical expertise who has access to update your DNS records.

Step 1: Access Migration Tool

Visit the Custom Hostname Migration tool. This web application will guide you through the migration process.

Step 2: Enter Your Custom Domain

Input your custom domain into the Custom Hostname Migration tool. You'll see the current status and instructions for migration. The tool displays three key statuses:

• Ownership verification

• Certificate delegation

• Switchover

Initially, these statuses will be yellow, indicating pending actions.

Step 3: Verify Ownership

To fix Ownership verification:

1. Create a TXT record in your DNS settings.

2. Use the hostname and value provided by the Custom Hostname Migration tool.

Step 4: Delegate Certificate

To fix the Cerificate delegation:

1. Create a CNAME record in your DNS settings.

2. Use the hostname and value provided by the Custom Hostname Migration tool.

Step 5: Wait for Propagation

Allow time for DNS changes to propagate:

• This typically takes 30 minutes to an hour but can be longer.

• Refresh the Custom Hostname Migration tool to check for status updates.

• If no changes occur within 3 hours, or if only one status changes:

  • Double-check your DNS entries for accuracy using the values on the tool.

  • If issues persist, contact support@chili-publish.com with your configuration details.

Step 6: Update CNAME Record

Once statuses update with both being green “OK”, you are ready to modify your original CNAME record.

Use the new value provided by the Custom Hostname Migration tool to update your original CNAME record. Change the CNAME from the current Azure Front Door value to the new Cloudflare value.

Step 7: Verify Migration

After updating the CNAME:

1. Wait for propagation (typically 30 minutes to an hour).

2. Verify the CNAME update using the nslookup command-line tool or https://www.nslookup.io

3. Test your custom domain in a web browser to ensure it's working correctly.

Advance Step

Only if your DNS zone utilizes CAA records, you will want to authorize both LetsEncrypt letsencrypt.org and Google Trust Services pki.goog to ensure proper SSL issuance.

See for more details: https://developers.cloudflare.com/ssl/edge-certificates/caa-records/

Common Questions

Will CHILI publish provide any direct support during my custom domain migration process?

We can provide guidance and perform sanity checks, but we do not offer IT support. If you have any questions or concerns, please email support@chili-publish.com.

Do I need to complete these steps all at once?

You don't need to complete all these steps at the same time. For example, you can finish steps 1-5 on the same day and schedule step 6 for a later date. This allows you to work at your own pace and plan accordingly.

Will there be any downtime when I migrate my custom domains?

No, the Azure Front Door will remain active until Dec 1st, 2024, ensuring no practical downtime if you choose to migrate before that date.

How long does the entire migration process typically take from start to finish?

The process typically takes around 2 hours, but most of this time is spent waiting for record additions or updates to propagate to the worldwide web. You may experience a faster migration process.

What happens if I don't complete the migration by the deadline?

If you fail to complete the migration on time, your custom domains will cease to work. You will then need to follow these documentation steps to migrate and restore functionality.

Can I revert the changes if something goes wrong during the migration?

Yes, simply change your CNAME record from the Cloudflare one back to the Azure Front Door one.

Will this migration affect any other services or integrations we have with CHILI GraFx?

It is unlikely, but possible, that services or integrations using the custom domain for API calls may cache the resolution IP address on startup, leading to failure on Dec 1st. If this is a concern, we suggest restarting your services or integrations sometime after your migration and before Dec 1st.

Is there a way to test the migration in a sandbox environment before applying it to our production custom domain?

If you have a custom domain that points to a sandbox environment, then yes. You are free to migrate your custom domains in any order you feel comfortable.

Will our SSL certificates be affected by this migration?

Both Azure Front Door and Cloudflare provide their own SSL certifications. If you are using CAA (Certification Authority Authorization) records, please refer to the advanced step above.

Can we migrate multiple custom domains at once, or do we need to do them one at a time?

You can migrate them all at once with no issues. However, you can also choose to do them one at a time.

Are there any known issues or common pitfalls we should be aware of during the migration?

The most significant issue is failing to properly copy the values from the Custom Hostname Migration tool page into your newly created or updated records.