This article explains how to check DNS delegation before requesting an UltraDNS-managed certificate for HTTPS Web Forwarding and how to investigate a failed certificate request.
When to Use This Article
Use this procedure when a certificate managed by UltraDNS for HTTPS Web Forwarding shows a failed issuance status. Relevant symptoms include a validation TXT record being created in UltraDNS without successful issuance, or public DNS delegation pointing to a different DNS provider.
If your question is about a domain that is visible to CertCentral but is not automated there, use the CertCentral integration troubleshooting article. Account linking, domain import and automation, and managed HTTPS forwarding certificate issuance are separate checks.
A cert-manager error such as spec.acme.solvers[0].dns01: Required value: no DNS01 provider configured concerns the cert-manager DNS-01 provider configuration. It does not establish that UltraDNS rejected a validation record. Review that configuration separately rather than using this procedure to diagnose the webhook rejection.
Why DNS Delegation Matters
Domain Control Validation (DCV) verifies control of a domain before certificate issuance. UltraDNS can create DNS validation records as part of managed certificate provisioning. A record's presence in the UltraDNS portal does not establish that public DNS returns it.
DNS delegation determines which nameservers public queries reach. If the validation hostname is served by another provider, a TXT record created only in UltraDNS is not available through that provider unless it is also published there. Creating a zone or changing its records in UltraDNS does not update the domain's delegation.
Visible to CertCentral makes a domain available through the CertCentral connection. It does not change nameservers at the registrar or copy records to another DNS provider.
A delegation mismatch identifies a configuration problem to investigate. It does not, by itself, establish the cause of a previous certificate failure. Check the failure details and the DNS configuration applicable when validation was attempted.
Check DNS Before Requesting the Certificate
- Confirm which DNS provider is intended to serve the domain.
- If UltraDNS is intended, open the account details in the UltraDNS portal and locate Assigned Name Servers. Use the nameservers assigned to that account.
- Check the delegation with
dig +trace example.com NS. Replaceexample.comwith your domain. Review the nameservers returned by the parent zone, not only the final answer. - Compare the delegation with the assigned nameservers. If the validation hostname is within a separately delegated subdomain, also check that subdomain's delegation.
- Confirm that Certificate Management and the managed certificate option are available for the account. Contact UltraDNS Support if the option is missing.
A standard lookup such as dig example.com NS shows the answer returned by your DNS resolver. Use the trace to investigate the delegation path when that answer does not match the intended configuration.
If the Domain Should Use UltraDNS
- Verify that the UltraDNS zone contains all DNS records required for the domain's services before changing delegation.
- Update the domain's nameservers at the registrar to the assigned UltraDNS nameservers. For a separately delegated subdomain, have the parent zone administrator update its delegation.
- Run the trace again to verify the updated delegation. Changing NS records inside the UltraDNS zone alone does not update the registrar's delegation.
- Allow existing DNS caches to update, and verify public resolution before submitting a new managed certificate request. Registrar processing and cached DNS data can affect when the change becomes visible.
If a certificate request has already failed, complete the investigation below and contact Support to confirm the appropriate retry action.
If the Domain Must Remain with Another DNS Provider
Keep the intended delegation in place. Contact UltraDNS Support to confirm the supported HTTPS forwarding and certificate arrangement before changing DNS. Enabling Visible to CertCentral does not publish validation records at the external provider.
Investigate a Failed Certificate Request
- Record the exact certificate error, affected hostname, and failure time, including the time zone.
- Open Audit and review the affected domain around the original request time. Include TXT, CAA, Web Forwarding, and certificate events. Do not limit the initial review to one user.
- Check whether the audit contains an ADD event for the validation TXT record. An ADD event establishes creation in UltraDNS; it does not prove successful validation. If no event appears in the reviewed history, report the date range and filters used. That absence alone does not establish why the request failed.
- Obtain the validation hostname and current expected TXT value for the request. If these are unavailable, ask Support to confirm them.
- Query each authoritative nameserver serving the validation hostname. For example, run
dig @ns1.example.net _dnsauth.example.com TXT +norecurse, replacing the names with the actual nameserver and validation hostname. Compare each response with the current expected value. - Provide Support with the account name and ID, certificate error, timestamps, audit export, validation hostname, and DNS output. Ask Support to confirm the recovery or retry procedure.
Confirm the Resolution
During DNS TXT validation, the required TXT value must be publicly discoverable through the DNS configuration serving the validation hostname. After provisioning completes, verify that the managed certificate shows Valid in Certificate Management and that the source HTTPS URL redirects to the intended destination without a certificate warning.
An automated validation record may be removed after validation. Its absence later does not establish that it was never created. Review the audit history and certificate status together.
Important Notes
- Do not use Reset or Unlink as a certificate restart step. Reset suspends the CertCentral connection and generates a new secret. Unlink disconnects the integration and stops its automated domain management.
- Do not assume that deleting and recreating a web forward, or waiting for domain revalidation, will restart a failed certificate request. Confirm the retry procedure with Support.
- These checks do not require deleting validation records. If record ownership or management is unclear, review the system-managed DCV record article or contact Support.