Skip to main content

Troubleshoot DNS setup

Identify where setup is failing, check the relevant configuration, and verify the result after making a correction. Follow the sections that match your symptoms.

Collect diagnostic information

  1. Record the affected zone and fully qualified names, such as www.example.com.

  2. Identify the record types involved and their expected values.

  3. Note when the problem started, including the time zone.

  4. Record any recent changes to records, delegation, DNSSEC, access, or transfer settings.

  5. Capture the exact error message or unexpected DNS response.

  6. Go to DNS > Zones, open the zone, and review its status and Health tab.

  7. If investigating a configuration change, review the relevant activity in DNS audit logs.

Keep this information available as you investigate. Avoid changing unrelated settings while testing a correction.

Troubleshoot access and permissions

If you cannot access DigiCert®​​ DNS:

  1. Confirm that you signed in with the intended user identity.

  2. Check that you selected the account or organization associated with your DNS service.

  3. Confirm with your account administrator that the Essentials purchase and entitlement activation have been completed.

  4. Ask an administrator to check your status under Configuration > Access management > Users.

  5. If your status is Deactivated and access should be restored, ask the administrator to activate your user.

  6. If the account and user are correct but DNS remains unavailable, contact us with your account details and the displayed message.

Do not purchase another entitlement solely to resolve an access problem before confirming the existing account’s activation.

If you can open DigiCert®​​ DNS but cannot perform an action:

  1. Identify the action that is unavailable, such as creating a zone, updating a record, or generating a token.

  2. Ask an administrator to open your profile and review Roles and permissions.

  3. Compare the assigned roles with the required action in the role permission matrices.

  4. Update the role assignments if the action is part of your responsibilities.

  5. Retry the action.

Review all assigned roles. Their permissions are combined; a role with fewer permissions does not restrict permissions granted by another role. See DNS roles and permissions.

Troubleshoot zone delegation and transfers

If queries are reaching the wrong nameservers:

  1. Open the zone’s Nameservers tab.

  2. Compare Assigned nameservers with Delegated nameservers.

  3. Check the full assigned hostname list against the nameserver settings saved at your registrar.

  4. Correct missing or mistyped hostnames and save the registrar changes.

  5. Return to DigiCert®​​ DNS and review delegation again after allowing time for publication.

If No delegated nameservers found appears, verify registration and delegation at the registrar. For a separately delegated subdomain, check its delegation in the parent zone.

Use authoritative nameserver hostnames for delegation. Do not substitute zone transfer or notification addresses.

If DigiCert®​​ DNS hosts a secondary zone and records are not synchronizing:

  1. Review the zone’s transfer status and error details.

  2. Confirm that its inbound IP set identifies the intended primary nameservers and permitted notification sources.

  3. At the primary provider, verify that transfer requests from DigiCert®​​ DNS are allowed.

  4. Confirm that the primary provider sends notifications to the DigiCert®​​ DNS notification destinations.

  5. If TSIG is used, verify that the key name, algorithm, and shared secret match at both providers.

  6. Correct the configuration and select Force zone transfer.

  7. Review the new transfer result and confirm that the expected records were received.

If an external secondary provider is not receiving your DigiCert​​®​​ primary zone:

  1. Review the primary zone’s assigned outbound IP sets.

  2. Confirm that Transfer to includes the source addresses used by the secondary provider to request transfers.

  3. Confirm that Send notifications to identifies the secondary provider’s notification receivers.

  4. Verify that the secondary provider uses the DigiCert​​®​​ primary transfer endpoints.

  5. Check matching TSIG settings when authentication is required.

  6. Verify the transfer result at the secondary provider.

An Active zone status does not prove that delegation or synchronization is complete. See Primary nameservers and delegation, Secondary nameservers and delegation, and DNS zone health.

Troubleshoot missing or incorrect records

  1. Open the intended zone’s Records tab.

  2. Search for the affected record and confirm its name and type.

  3. Check the resulting full name.

    For example, www in the example.com zone represents www.example.com; @ represents the zone apex.

  4. Compare the saved values and TTL with your service provider’s instructions.

  5. If regional views are enabled, check the applicable regional configuration.

  6. If records were imported, review import warnings for entries that were not added.

  7. Use a DNS lookup tool to query the full name and record type directly against an assigned authoritative nameserver.

  8. Repeat the query against the other authoritative nameservers and compare their responses.

If saving a record reports an existing record with the same name and type, edit the existing record to add or update its values.

For secondary zones, correct records at the primary provider and verify synchronization. For integration-managed records, review the managing integration before attempting removal.

If authoritative responses match the intended values but the service still fails, check the destination website, mail service, or application configuration. See Manage DNS records for record-specific requirements.

Troubleshoot propagation and caching

If authoritative nameservers return the new value but other lookups return an older result:

  1. Record the authoritative answer and the recursive resolver’s answer.

  2. Confirm that both queries use the same full name and record type.

  3. Check the TTL that applied before the change.

  4. Allow previously cached answers to expire, then query again.

  5. Repeat the lookup through another recursive resolver.

  6. If you recently changed delegation, check whether cached delegation still directs queries to the previous provider.

Lowering a TTL does not shorten the lifetime of answers already cached under an earlier TTL. A recently created or restored record can also remain temporarily unavailable to a resolver that cached an earlier “not found” response.

Avoid repeatedly changing a correct record while waiting for caches to refresh. If authoritative nameservers disagree, investigate zone configuration or synchronization first.

Troubleshoot API errors

  1. Capture the request method, endpoint, timestamp, response status, and error body.

  2. Confirm that the request targets the intended account and resource.

  3. Check that the API token is complete, active, and has not expired.

  4. Review the owning user’s or service user’s access status and assigned roles.

  5. In Postman, check the collection variables and confirm that the request uses the intended authentication settings.

  6. Review enabled parameters and the request body for unchanged example values or missing required fields.

  7. Use the error details and the DC: DigiCert® DNS API documentation to identify the correction.

Remove API tokens and other credentials before sharing request details. For client configuration, see Set up Postman for the DNS API.

Troubleshoot DNSSEC

If DNSSEC setup is incomplete or validating resolvers fail to resolve the zone:

  1. Open the primary zone’s DNSSEC tab.

  2. Review the displayed setup message.

  3. For Pending DNSSEC setup, confirm that the supplied DS record has been added at the registrar.

  4. For DS record mismatch, compare the registrar’s DS values with those displayed in DigiCert®​​ DNS and correct the mismatch.

  5. For DS record lookup failed, retry the check and verify the DS configuration with the registrar if the message persists.

  6. After a correction, allow time for publication and cached data to expire.

  7. Review the DNSSEC page again and repeat resolution checks.

If the problem followed a migration or KSK rollover, verify that the parent zone DS records match the intended signing keys.

Do not unsign the zone while its DS records remain published. Follow DNSSEC for the required setup, rollover, or disablement sequence.

Escalate unresolved problems

If the problem remains unresolved:

  1. Summarize the issue and the services affected.

  2. Include your account details and the affected fully qualified names.

  3. Provide the expected result and examples of the actual DNS query results or error responses.

  4. Include timestamps, recent changes, and the checks you have already completed.

  5. Remove API tokens, passwords, TSIG shared secrets, and other credentials.

  6. Email digicertdns@digicert.com.

For contact information and account-wide support package options, see Contact us.