Why are my custom resolver secondary zone records not available in the custom resolver location?

You tried to query a custom resolver's secondary zone records, but it doesn't respond.

A custom resolver that has a secondary zone configured is not responding to DNS queries for the configured zone.

This issue can occur when there is a misconfiguration in either the on-prem resolver or in the DNS Services instance.

To make the custom resolver secondary zone records available for the configured zones, take the following steps.

• Check that the on-prem DNS server is configured to allow transfers to all custom resolver locations
• Check that the secondary zone in their custom resolver is configured to make the transfer from the correct IP
• Check that the on-prem DNS server can be reached by the custom resolver locations