Domain names
A domain ownership check proves control of the name. A service address then directs users to the application, website or documentation. These checks use different DNS records and should be completed separately.
Before you start — Have access to the DNS management of the domain you control. Identify the service to connect and copy its current records from the project. Ownership verification and the service’s address connection require different records.
Declare and verify a domain
Verify control of the domain before using it in a service configuration.
- Open the project domain tools and Add a new domain.
- Enter Domain name and click Continue.
- Use Copy for the ownership TXT value shown.
- Add the requested TXT record at your domain's DNS provider.
- Return to the project and click Verify.
The domain is verified when the expected record is found. Enter the actual domain you control; do not reuse another project's verification value.
Assign a production service address
Choose the service address that users should recognize, then read the records for that exact destination.
- Open the service's domain configuration.
- Select the appropriate Verified domain.
- Enter Subdomain for the intended service address.
- Click Save or the linking action shown by the current form.
- Read DNS record to add or DNS records to add for that service.
Use the name, type and value displayed for that service. Website, workspace and documentation are separate destinations.
The website and documentation can use different hostnames of one domain. Copy each service’s own name, type and target. A successful website check does not establish that the documentation hostname is correctly connected, and the ownership TXT record is not the address target.
Check the DNS connection
Complete the address records independently of the earlier ownership TXT check.
- Add the displayed address record at your DNS provider.
- Return to the corresponding service configuration.
- Click Check the DNS record.
- Read the resulting state.
- Open the public service address after verification.
The connection check succeeds and the public hostname opens the intended service.
Note — DNS changes may not be visible immediately. If the first check fails, compare the record exactly and allow propagation before trying again.
Change an existing service address
Review links using the former address as part of the change, not only the new DNS record.
- Open the address configuration for the correct service.
- Use Change when a different domain or subdomain is required.
- Review the new address and the DNS records it requests.
- Complete verification and check the public destination.
- Review website and documentation links that refer to the former address.
The new address works and the affected visitor journeys use the intended destination.
Remove a secondary domain
Remove a secondary domain you no longer need, for example one declared with a typo.
- Under Secondary domains, find the domain and click Delete.
- Check Domain name, then click Delete under Confirm the deletion.
The domain leaves your project; nothing changes at your registrar and you can declare it again later.
Note — The primary domain can't be removed, nor can a domain that still carries a production host. Point that service at another domain first.
Diagnose a failed check
Distinguish a failed ownership check from an address that does not reach the intended service.
| Situation | What to compare |
|---|---|
| Ownership is not verified | The TXT name and value shown for that domain. |
| The service address is not verified | The address record and target shown for that service. |
| The wrong application opens | The selected service, full hostname and project. |
Important — Copy the values from your project's current configuration. An example domain or another service's IP does not establish the required DNS destination.