Configure DNS records for custom domains

This page explains how to configure DNS records shown in Xperience Portal when adding custom domains.

Start with a channel-specific custom domain setup flow, then return here to configure records with your DNS provider:

General DNS configuration best practices

Regardless of your DNS provider, follow these best practices when configuring DNS records:

  • Verify exact values: Copy and paste values from Xperience Portal to avoid typos.
  • Match record types carefully: Ensure the Type field matches what Xperience Portal displays (TXT, CNAME, A, etc.).
  • Use appropriate TTL: A TTL of 300-600 seconds is ideal for validation records, as it allows DNS changes to propagate faster.
  • Check for existing records: Some providers may have existing records that conflict. Review existing records before adding new ones.
  • Wait for propagation: DNS changes can take time. Use online DNS propagation checkers if you want to verify propagation status.
  • Use DNS-only mode: If your provider offers a “proxy” or “forwarding” option, set it to DNS only for validation records.
  • Enable DNSSEC cautiously: If your provider offers DNSSEC, ensure it’s configured correctly to avoid validation issues.

Troubleshooting DNS configuration

If validation fails after configuring DNS records, try the following:

  • Wait longer: DNS propagation can take up to 15-24 hours. Wait at least 15 minutes before retrying.
  • Verify the records: Double-check that the Name and Value fields match exactly what Xperience Portal displays.
  • Check TTL propagation: If you set a high TTL before adding records, the old configuration may be cached. Wait for the old TTL to expire.
  • Use online tools: Use DNS propagation checkers to verify your records are visible globally.
  • Contact your provider: If records are correct but validation still fails, contact your DNS provider’s support team.
  • Retry validation: In Xperience Portal, select Validate to retry DNS validation.

Azure App Service DNS configuration

If your domain is registered with Microsoft Azure, follow these step-by-step instructions to configure the DNS records:

Prerequisites

  • An Azure subscription with access to your domain’s DNS zone
  • Admin or contributor permissions in the Azure portal
  • The DNS records from Xperience Portal

Steps

  1. Sign in to the Azure portal.
  2. Go to DNS zones:
    • Select DNS zones from the left navigation panel.
    • If you don’t see it, search for “DNS zones” in the search bar at the top.
  3. Select your domain from the list of DNS zones.
  4. The current DNS records for your domain are displayed. Add each DNS record shown in Xperience Portal:
    • Select + Add record set (or + Record set depending on your Azure version).
    • Fill in the following fields:
      • Name – Enter the hostname from Xperience Portal. For example, if the record shows _acme-challenge.yourdomain.com, enter only _acme-challenge (Azure automatically appends the zone name).
      • Type – Select the record type matching Xperience Portal (typically TXT for validation records, CNAME for aliases, or A for IP addresses).
      • TTL – Enter a value between 300 and 3600 seconds. A shorter TTL (300–600) allows DNS changes to propagate faster but increases DNS queries.
      • Value – Paste the exact value provided in Xperience Portal.
    • Select OK to create the record.
  5. Repeat step 4 for each DNS record displayed in Xperience Portal.
  6. After you have added all records, select Save at the top of the page to commit your changes.
  7. Wait for DNS propagation. This can take up to 15 minutes to verify. If validation doesn’t complete within 15 minutes, the DNS records may not have propagated fully to all DNS servers globally, which can take longer.
  8. Return to Xperience Portal and select Validate to confirm the DNS records are properly configured.

Troubleshooting Azure DNS

  • Record not appearing: Ensure you have saved after creating records.
  • Validation fails: Check that the Name field is correct (without the domain suffix, which Azure adds automatically).
  • Propagation delays: If records still don’t validate after 15 minutes, increase your TTL to 3600 and try again after a few more minutes.

For more information, see Azure DNS documentation.

AWS Route 53 DNS configuration

If your domain is registered with Amazon Route 53, see Route 53 DNS configuration documentation for step-by-step instructions on configuring DNS records.

Cloudflare DNS configuration

If your domain uses Cloudflare as your DNS provider, see Cloudflare DNS records documentation for step-by-step instructions on creating DNS records.

Other DNS providers

If you use a different DNS provider (GoDaddy, Namecheap, 1&1, Bluehost, HostGator, etc.), the general process is the same as the providers listed above. Consult your provider’s documentation for specific instructions on creating DNS records.