Verify Domain DNS
Check DNS records and activate a custom domain.
After you add a custom domain, Agiled shows DNS records that must exist at your DNS provider before the domain can become active.
Verify DNS before sharing public links on the custom domain.
DNS verification should be treated as a launch step. Do not announce the custom domain until both DNS and HTTPS tests pass.
Keep the built-in workspace domain available until DNS verification and HTTPS activation are complete.
Verify DNS
- Open Settings.
- Go to Domains.
- Copy each DNS record name and value exactly.
- Add the records at your DNS provider.
- Return to Agiled.
- Select Verify DNS.
Each DNS row shows a status such as pending, verified, or failed.
Copy values exactly from Agiled. Extra spaces, missing subdomain prefixes, or records added to the wrong DNS zone are common causes of failed verification.
Do not remove the old working domain while verification is pending. Keep public forms, booking pages, invoices, estimates, checkout links, storefronts, and document links available on the built-in workspace domain until the custom domain is fully active.
If Verification Fails
Check these items:
- The record type matches the value shown in Agiled.
- The record name is exact.
- The record value is exact.
- The record is in the correct DNS zone.
- DNS propagation has had enough time.
If your DNS provider automatically appends the domain name, do not paste the full host twice. Compare the final record shown by the DNS provider with the record Agiled expects.
If your DNS provider has proxying, flattening, or forwarding features, confirm they do not change the record Agiled asked you to create.
When checking DNS with your provider, compare the final hostname and value after the provider has saved the record. Some providers show shorthand names while the public DNS record uses the full hostname.
HTTPS Activation
After DNS verifies, the domain can still need time for certificate activation. Keep the built-in workspace subdomain available while the custom domain becomes ready.
After activation, test a public form, booking page, invoice, estimate, document, checkout link, and storefront on the custom domain if those pages are used by your workspace.
Use a private browser window for the final test so cached sessions do not hide a domain, redirect, or certificate issue.
Troubleshooting
If verification passes but the browser shows a certificate warning, wait for HTTPS activation and keep using the workspace subdomain until it clears.
If only some public links use the custom domain, regenerate or resend those links from the workspace after the domain is active.
If DNS appears correct but Agiled still cannot verify it, capture the expected record from Agiled, the saved record from the DNS provider, and the domain being verified before asking for help.
Evidence To Capture
When DNS verification needs help, capture:
- domain being verified
- expected record type, name, and value from Agiled
- saved record from the DNS provider
- proxy or DNS-only status
- time the record was changed
- screenshot of the provider's final saved value
Do not share unrelated DNS records or registrar credentials.