Resource domains
Overview
Information about the resource domains is reflected in the Domains tab:
Here you will find two types of domains:
System domains - automatically created by the system to access the resource files
User domains - domains added by the user to access the resource files.
Domain management
You can add, remove, and configure user domains.
Adding your domains
When you click the Add user domain button, a dialog for creating a new domain appears:
Specify a third-order or lower domain name.
You also can add a bundle of your domains at once, for this purpose, use the ADD BULK button and specify all domains of this resource.
Here you can issue a Let’s Encrypt certificates in bulk for all added domains, or you can apply existing certificates that have already been uploaded to the user panel.
To confirm adding a list of domains, click Add User Domains.
Adding an SSL-certificates
Next, select the SSL certificate you want to apply to the domain from the drop-down list:
Let’s Encrypt certificate (auto) - automatically created by the provider
Custom certificate (user) - user-added certificate
If the required SSL certificate is not listed, it must be added to be applied to the new domain. To add it, click Add new SSL-certificate in the certificate drop-down list.
When selecting Add new SSL certificate from the drop-down list, you will be taken to the SSL certificates section of the user panel to add a new certificate.
Only after entering all required data and saving it, the certificate will become available for selection in the drop-down list.
After clicking the Add domain button - the resource will be added a domain with preset (default) settings. The Cancel button cancels adding a custom domain.
You can find more information on SSL certificates in a dedicated article: SSL Certificates [EN]
Changing Your System Domain
Note: While a system domain migration (including its grace period) is in progress, moving your pull zone to a different cluster is restricted. You must complete or cancel the migration before initiating a cluster move.
You can migrate your pull zone to a new system domain via the user panel. You’ll than need to manually update every CNAME record for your custom domains to point to the new (target) domain. Upon your manual CNAMEs update, the process runs automatically.
Migration won't interrupt your CDN service at any point. Resource domains | Zero downtime domain migration
Initiating domain migration
You can only run one migration / migration rollback per pull zone at a time.
Open the Domains tab in your pull zone settings, click Change System Domain
and pick a new system domain from the dropdown. The migration begins the moment you select your target system domain and confirm it.
Once migration is initiated, the banner appears at the top of the page showing your migration status, and the CNAME changes you need to make.
Click Detailed status, to see which custom domain CNAMEs still resolve to the legacy domain.
Updating your DNS
For each custom domain, you need to point its CNAME record at the target (new) system domain. System will only proceed with the migration once none of your custom domains resolve to the legacy (old) system domain.
Only CNAME records can be verified automatically - if a domain uses A/AAAA records, or sits behind a third-party proxy or CDN, it'll be marked Unverifiable and won’t stall the migration, but it’s on you to confirm it resolves correctly.
Click Detailed status link in the migration status banne for per-domain information as shown below.
The system auto-polls your DNS records as follows:
every 5 minutes for the first hour,
every 15 minutes up to 6 hours, and
hourly after that.
To protect against DNS flapping, a custom domain must resolve correctly on two consecutive automatic polls before it is marked as confirmed.
If you are sure your DNS updates are final, you can click the Check Domains button to run an immediate verification. This manual check bypasses the two-poll rule and can complete the migration instantly if all records pass.
Unverifiable Domains
If a domain uses A/AAAA records, sits behind a third-party proxy, or returns NXDOMAIN/SERVFAIL errors (after 3 retries), it will be marked as Unverifiable. Unverifiable domains don't stall the migration - they are protected by our traffic monitoring system to ensure no connections are dropped.
Migration completion and handoff
The legacy domain doesn't die off right away, it stays active for a graceful handoff period of 24 hours to 7 days, depending on your CNAME TTLs, so cached DNS entries have time to expire in peace.
Once the DNS check confirms no custom domains are resolving to the old system domain, the migration automatically completes, and you will receive a confirmation email.
If traffic drops to zero for the duration of the decomission, the old domain is safely and silently removed.
If the old domain is still receiving residual traffic (e.g., from third-party proxies or lingering caches), it will not be removed. Instead, you and our admins will receive a daily email listing the exact hostnames still routing to the old system domain so you can investigate.
Graceful handoff
To guarantee zero downtime, the legacy domain does not die off right away based on DNS alone. Instead, it enters a graceful handoff period (calculated as double your DNS TTL, minimum 24 hours, up to 7 days). The system actively monitors requests hitting the legacy domain.
You can't start another migration during graceful handoff. Once it’s finished, the legacy domain is fully retired.
Resource domains | Zero downtime domain migration
Migration auto-reversal
At the 48-hour mark, if migration is nor yet resumed, the system evaluates migration progress to one of the below results:
Automatic Reversal
If you haven’t updated any CNAME records within 48 hours, the system assumes the migration was abandoned and safely reverts it. Your original system domain is restored as primary, and you will receive an email notification.
No Reversal (Partial Progress)
If you have updated at least one CNAME record, the system will never automatically revert the migration, to preserve the domains you already moved. Both system domains will stay live, and you will receive daily reminder emails to either finish the remaining DNS updates or manually cancel the migration.
Manual migration cancellation
If need be - hit Cancel Migration and confirm.
Upon cancellation, initial system domain is immediately restored as the primary target domain.
To prevent outages for any CNAME records you may have already updated, both involved system domains (initial/legacy and new/target) are kept alive in our system for a 48-hour grace period.
You will need to manually switch your DNS records back to the original legacy domain during this window.
Zero-downtime domain migration
We are keeping the legacy domain running parallel to the new target domain for the migration period. This allows time for DNS propagation and ensures CDN caches update gracefully based on TTL settings.
The legacy domain will remain active during the migration overlap window. This ensures zero downtime by allowing CDN edge nodes to naturally expire their caches and resolve the new target domain according to standard TTLs. To ease your system domain migration we ensure this way you have all the time needed for:
Traffic Drop Prevention: If we shut down the legacy domain the exact second you switch the CNAMEs, any server or user that still has the old routing cached would have hit a dead end (resulting in 404s or connection timeouts).
DNS Propagation: CDNs, local ISPs, and even your users' browsers cache DNS records based on the TTL (Time-To-Live).
Graceful Handoff: Keeping the legacy domain up and running ensures that while the CDN is waiting for its TTL to expire, it can still successfully pull content from the old origin.