User
Add and verify a brand domain
Register a domain/subdomain for supported branded URLs and verify its DNS token. Verification and working HTTPS routing are separate checks.
Step-by-step guide
Before you start
- Use a domain you control and make sure you can edit its DNS records. Have the site administrator’s routing hostname available.
- Do not replace unrelated DNS records while preparing a brand subdomain; use the host/value instructions displayed for this installation.
Open this feature
Open /portal/qr-codes/domains on your application domain. The tasks below name the controls to use after opening the page.
How to use it
Add the domain and its DNS records
- Open /portal/brand/custom-domains or /portal/qr-codes/domains, depending on your menu.
- Enter the hostname in Domain, for example go.yourbrand.com, and select Add domain. Use your own hostname, not the example.
- Read the displayed DNS setup. At your DNS provider, add the CNAME/routing record with the exact target hostname shown by this installation.
- Add the generated TXT verification record at the correct host. Copy the complete token for this domain; do not copy a token belonging to another entry.
- After the DNS record is visible, return to the same entry and select Verify DNS.
Use the verified domain and test it
- Select the verified domain in a supported link/QR/page editor and save that item.
- If you intend it to be the default, use Set default, then inspect the domain selected for a newly created item.
- Open a real branded URL over HTTPS from a separate session. Check routing, certificate and final content.
- If DNS verification passed but HTTPS fails, ask the site administrator to check server routing/certificates rather than repeatedly adding the domain.
Fields and examples
| Field or choice | How to use it |
|---|---|
| Domain | A hostname, not a complete destination path. Use a real domain/subdomain you control. |
| CNAME/routing target | Copy the hostname supplied by this installation. Do not invent an IP or target from a generic tutorial. |
| TXT token | Domain-specific verification content. Use the host/name instructed by the page and wait for DNS propagation. |
| Set default / Unset default | Controls the default selection where supported; review existing items separately. |
Check your finished result
- Check the verified status and then test an actual branded HTTPS URL.
Problems and fixes
| What you see | What to do next |
|---|---|
| TXT record not found yet | Check the record’s host and exact token, then allow DNS propagation before retrying Verify DNS. |
| This domain already exists | Find the existing entry or ask the administrator who owns it; do not create repeated variants. |
| Verified but URL does not load | Check routing/CNAME and certificate configuration with the administrator. |
Technical reference
Sources for these task instructions
Role-scoped source references
Pinned commit: ca125291cce57358ac4842e50928bc31fc6eab07
Source-only route information
| Method | Source-default route |
|---|---|
| GET | /portal/qr-codes/domains |
| GET | /portal/brand/custom-domains |