Custom domains let you serve bucket content from your own hostname (e.g. cdn.example.com) instead of the default IBEE Public Access URL. You add a CNAME record in your DNS provider, then register the domain in the bucket settings.
The bucket must be public to configure a custom domain. If Public Access is disabled, the Custom Domains tab shows the error “Bucket must be public to configure custom domain” and the CNAME target shown under Step 1 will be Unavailable.
Open your bucket in the portal, click the Settings tab, then click Custom Domains.
Click + Add Domain. The Add Custom Domain modal appears with the subtitle “Connect your bucket to a custom domain.”
The modal’s Step 1 shows the field “Add a CNAME record in your DNS pointing to:” with the CNAME target. Click Copy to copy the target:
Go to your DNS provider and add a CNAME record:
DNS propagation can take some time before verification succeeds. Wait for propagation to complete before proceeding to Step 2.
Verification fails immediately after adding the domain DNS propagation takes time. Wait a few minutes after adding the CNAME record, then try again.
CNAME record not resolving Verify the CNAME record is saved correctly in your DNS provider. The record value must exactly match the target shown in the portal.
Domain shows as unverified
Ensure the CNAME points to the full target including .ibee.zone. Some DNS providers strip the trailing dot — confirm the value is saved as shown.
CNAME target shows Unavailable
The bucket is not public. Enable Public Access first — see Bucket policies → Public access.