Custom Domains
Connect your own domain or subdomain to your public dajia.lol profile
Custom Domains
Custom domains let Premium users serve their public profile directly from a domain they own, such as profile.example.com or example.com.
Open Custom Domains ↗ from Settings => Custom Domains.
Dajia connects a domain that you already registered with a domain provider. It does not register or sell the domain for you. Custom domains require Premium: Lifetime Premium includes 3 domains, while an active Premium subscription includes 5.
Before you start
Own the domain
Register the domain with a registrar and make sure you can edit its DNS records.
Have Premium access
Check that your account has an available custom-domain slot before you begin.
Choose a host
Use an apex domain such as example.com or a subdomain such as profile.example.com.
Register the domain in Dajia
Open Custom Domains
Go to Settings => Custom Domains.
Enter your domain
Enter the host you want to connect, without a path. You can use either an apex domain like
example.com or a subdomain like profile.example.com.
The form normalizes the value to lowercase and removes a leading https://, but entering
the hostname directly makes it easier to spot a typo.
Click Add domain
Dajia creates a Pending domain card. The card shows the values you need to add at your DNS provider:
- CNAME target — where your domain should point.
- TXT name — the verification record name.
- TXT value — the unique verification token.
The current defaults are cname.dajia.lol and _dajia, but always use the
exact values shown on your domain card.
Add the DNS records
The DNS records depend on whether you are connecting a subdomain or the root of your domain.
For profile.example.com, create these records in the DNS zone for
example.com:
| Type | Name | Value |
|---|---|---|
CNAME | profile | The CNAME target shown in Dajia, usually cname.dajia.lol |
TXT | _dajia.profile | The full verification token shown in Dajia |
Some DNS providers ask for the full host instead of the short name. In that case, the TXT host
is _dajia.profile.example.com.
If your DNS provider offers a proxy toggle, keep the traffic record DNS only. Dajia terminates HTTPS for verified custom domains; a third-party proxy in front of the CNAME target cannot provision the Dajia certificate.
For example.com, create the records in the DNS zone for example.com:
| Type | Name | Value |
|---|---|---|
TXT | _dajia | The full verification token shown in Dajia |
ALIAS, ANAME, or CNAME flattening | @ or the root | The CNAME target shown in Dajia, usually cname.dajia.lol |
Many providers do not allow a normal CNAME at the root. Use their ALIAS, ANAME, or CNAME-flattening option instead. If none is available, use a subdomain.
The resulting traffic record must resolve directly to Dajia's edge. Do not place a separate proxy in front of it unless that proxy is configured to serve the custom hostname's TLS certificate.
The TXT token is unique to your domain. Never copy the example format from this page; copy the value from the pending domain card in your Dajia settings.
Cloudflare example
These instructions assume that Cloudflare is authoritative for your domain, so the domain uses Cloudflare nameservers. Open your domain in the Cloudflare dashboard and go to DNS => Records. For Cloudflare's current field descriptions, see Manage DNS records ↗.
Use the exact CNAME target and TXT value shown on your Dajia domain card. The values below use
cname.dajia.lol and profile.example.com as examples.
Add the CNAME record
For a subdomain such as profile.example.com, create a record:
| Field | Value |
|---|---|
| Type | CNAME |
| Name | profile |
| Target | The CNAME target shown in Dajia, for example cname.dajia.lol |
| Proxy status | DNS only |
| TTL | Auto |
Use DNS only (the gray cloud). Do not use Proxied (the orange cloud): Dajia needs the hostname to resolve directly to its edge so it can provision HTTPS for the custom domain.
Add the TXT verification record
Create a second record:
| Field | Value |
|---|---|
| Type | TXT |
| Name | _dajia.profile |
| Content | The TXT value shown in Dajia |
| TTL | Auto |
Verify the domain
Return to Settings => Custom Domains and click Verify DNS on the pending domain card.
Cloudflare apex domain
For an apex domain such as example.com, add a CNAME record with Name set to @ and
the target shown on your Dajia domain card. Cloudflare supports this through
CNAME flattening ↗, which is enabled by
default for the zone apex.
| Field | Value |
|---|---|
| Type | CNAME |
| Name | @ |
| Target | The CNAME target shown in Dajia, for example cname.dajia.lol |
| Proxy status | DNS only |
| TTL | Auto |
Add the TXT record separately with Name _dajia and Content equal to the verification value
shown in Dajia. Do not leave an existing conflicting A, AAAA, or CNAME record at the same
hostname; replace it if this domain should point to Dajia.
After both records are saved, return to Settings => Custom Domains and click Verify DNS.
Wait for DNS and verify
Wait for propagation
DNS changes can take a few minutes to appear publicly. Some providers take longer, especially when an older record has a high TTL.
Click Verify DNS
Return to the domain card and click Verify DNS. Dajia checks the TXT record shown for that domain. You can safely retry the check while the status is still Pending.
Use the verified profile
Once the status changes to Verified, open the domain in a new browser tab. The profile must be public and the account must continue to have the Premium access required for custom domains.
The first HTTPS request may take a few seconds while Dajia provisions the hostname's certificate; later requests use the cached certificate.
Domain status and actions
Pending
The domain was added, but the TXT verification record has not been found yet.
Verified
The TXT record was found and the domain can serve your public profile when its DNS target is correct.
Verify DNS
Run the TXT check again after changing DNS or waiting for propagation.
Remove
Delete the domain connection when you no longer want it attached to your profile.