Domains About 3 min read
Connect your own domain and check HTTPS
Set up an address such as short.example.com and identify which step is preventing it from becoming ready.
Choose a domain you control
A custom domain lets you share short links using your own address, such as short.example.com. You need access to that domain's DNS settings. This service does not register a domain for you, and domain registration or DNS hosting may have separate costs.
A dedicated subdomain is often easier to manage than replacing an address that already serves a website. Before changing anything, find out who owns the domain and who can edit its DNS. If someone else manages it, share the connection instructions with them rather than guessing at the settings.
Add the hostname and follow its instructions
Open your account settings and choose the domains tab. Add the hostname by itself: short.example.com, without https://, a page path, or a trailing slash. Open the domain's connection or status page and follow the instructions shown for this deployment.
DNS records tell browsers where to find the service. Use the record type and target shown in the connection guide. A CNAME points a name to another hostname; A and AAAA records point to IPv4 and IPv6 addresses. If the guide shows a TXT ownership record, publish its exact name and value and keep it until setup completes. Do not copy an example address from an unrelated site.
- Add the hostname in your account settings.
- Update its DNS using the service's connection instructions.
- Complete any ownership checks shown on the domain page and wait for administrator approval.
- The service then configures routing and HTTPS automatically. Wait until the status is Active before selecting the domain for a short link.
If the domain is still not ready
Check the exact hostname and compare the public DNS result with the records you intended to save. DNS changes can take time to appear because networks cache old answers. Repeatedly changing records while caches update can make the problem harder to understand.
An old or extra address record can send some visitors to another server. Pay attention to IPv6 records as well as IPv4 records. Changing a domain's nameservers affects its wider DNS setup, which may include websites and email; the short-link hostname should follow the specific connection guide. Administrator approval is also a separate step, so correct DNS alone does not make the domain approved.
Check the secure connection and the whole link
For approved custom domains, the provisioning agent sets up the host configuration and requests the HTTPS certificate. You do not need to add a CloudPanel alias or request a separate certificate for each custom domain. The site's primary hostname and its certificate are managed separately by the administrator in CloudPanel. A browser certificate warning means the secure connection still needs attention, even if DNS reaches the server.
When the status is Active, create a test link using the domain and open its full HTTPS address in a private window. Check that its HTTP address redirects to HTTPS too. Complete any CAPTCHA and check the final page. If HTTPS works but an external CAPTCHA fails, the provider may need the hostname added to its own settings.
What to include in a ticket
Send the hostname, the status or error shown, when you changed DNS, and whether the failure is a DNS lookup, certificate warning, waiting page, or final redirect. Include only the relevant error text. Leave out DNS account passwords, API tokens, CAPTCHA secrets, and private keys.