From a1cb8460f0e5a96f3e1eeb339b7b38aa37082b49 Mon Sep 17 00:00:00 2001 From: Pedro Miola Date: Fri, 24 Jan 2025 18:01:31 -0300 Subject: [PATCH] =?UTF-8?q?AI=20Comment:=20The=20documentation=20was=20upd?= =?UTF-8?q?ated=20to=20address=20user=20queries=20about=20setting=20up=20d?= =?UTF-8?q?omain=20redirects=20to=20external=20platforms=20like=20Zendesk?= =?UTF-8?q?=20and=20handling=20CNAME=20release.=20I=20added=20a=20section?= =?UTF-8?q?=20on=20handling=20SSL=20certificate=20issues=20with=20third-pa?= =?UTF-8?q?rty=20services=20and=20verifying=20domain=20ownership=20for=20C?= =?UTF-8?q?NAME=20release,=20including=20the=20use=20of=20TXT=20records=20?= =?UTF-8?q?for=20verification.=20These=20enhancements=20aim=20to=20guide?= =?UTF-8?q?=20users=20in=20managing=20DNS=20configurations=20effectively?= =?UTF-8?q?=20when=20integrating=20with=20external=20services.=20C=C3=B3di?= =?UTF-8?q?go:=2018268,17710?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../work-with-domains/point-domain.mdx | 22 ++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/src/content/docs/en/pages/main-menu/work-with-domains/point-domain.mdx b/src/content/docs/en/pages/main-menu/work-with-domains/point-domain.mdx index 0b9e8f106b..f608a5fa80 100644 --- a/src/content/docs/en/pages/main-menu/work-with-domains/point-domain.mdx +++ b/src/content/docs/en/pages/main-menu/work-with-domains/point-domain.mdx @@ -103,7 +103,7 @@ curl --location --request PATCH 'https://api.azionapi.net/domains/' \ | `cnames` | Accepts a list of CNAMEs for the domains as values. For example, `["*.yourdomain.com", "*.yourdomain.org"]`. | :::tip -If your application uses HTTPS, you might want to combine this process with the [association of a digital certificate](/en/documentation/products/guides/create-a-digital-certificate/) to your custom domain. +If your application uses HTTPS, you might want to combine this process with the [association of a digital certificate](/en/documentation/products/guides/create-a-digital-certificate/) to your custom domain. Also, ensure to handle any SSL certificate issues that may arise from third-party services like Zendesk by following their SSL integration guidelines. ::: 5. You should receive a response with the updated data. @@ -155,3 +155,23 @@ Once the changes have propagated, you'll be able to access your edge application :::tip Check the [Azion API documentation](https://api.azion.com/) and the [OpenAPI specification](https://github.com/aziontech/azionapi-openapi/) to know more about all features available via API. ::: + +--- + +## Step 3: Handling third-party integrations and verification for CNAME release + +When integrating with third-party services such as Zendesk, ensure you follow their specific host mapping requirements. This often includes configuring DNS records according to their guidelines, which may involve setting up a subdomain and pointing it to their servers. + +### SSL Certificate Issues + +Ensure that you handle SSL certificate issues by adhering to the SSL requirements of third-party services. Refer to their documentation for guidance on SSL integration and potential troubleshooting steps. + +### Verifying Domain Ownership + +For CNAME release, it's important to verify domain ownership. This can typically be done by adding a TXT record or pointing the domain to a specific verification address provided by the service. Follow these steps for verification: + +1. Obtain the verification details from the third-party service. +2. Access your DNS provider and add the necessary TXT records or point the domain to the specified address. +3. Confirm the verification process with the third-party service to ensure successful domain ownership validation. + +By following these steps, you can seamlessly integrate your domain with third-party services like Zendesk while ensuring compliance with their requirements. \ No newline at end of file