Conditional forwarder no longer resolving partner domain

Rohan Joshi 20 Reputation points
2026-07-28T05:11:06.9066667+00:00

We have a conditional forwarder configured for a partner company's DNS domain, but it stopped resolving names after they made changes to their DNS infrastructure.

I would like to understand the recommended process for verifying the current forwarder configuration, confirming connectivity to the partner's DNS servers, and re-establishing reliable name resolution.

Windows for business | Windows 365 Enterprise
0 comments No comments

2 answers

Sort by: Most helpful
  1. JimmySalian-2011 45,881 Reputation points Volunteer Moderator
    2026-07-28T06:38:06.3633333+00:00

    Hi Rohan,

    You can follow the steps and will require Network Engineer to work on this with you

    1. Port 53 open: Your firewall must allow traffic from your local DNS server to the external DNS IP over port 53 (both UDP and TCP).
    2. Direct IP routing: The local DNS server must have a valid network path (via WAN or VPN/ExpressRoute) to reach the target external IP.

    You can try telnet or port query to the target DNS Server on port 53.

    Hope this helps.

    JS

    ==

    Please Accept the answer if the information helped you. This will help us and others in the community as well.

    Was this answer helpful?

    0 comments No comments

  2. Ivy Bui (WICLOUD CORPORATION) 510 Reputation points Microsoft External Staff Moderator
    2026-07-28T06:37:36.8766667+00:00

    Hello Rohan Joshi

    Thank you for contacting Microsoft Q&A.

    Based on the information provided, it appears that the issue may be related to the conditional forwarder configuration or connectivity to the partner's DNS servers following recent changes in their DNS environment.

    As a next step, could you please help verify the following:

    • Confirm the current DNS server IP addresses provided by the partner for the affected domain.
    • Verify connectivity from your DNS server to the partner's DNS servers on port 53 (DNS).
    • Test name resolution directly against the partner's DNS servers using tools such as nslookup or Resolve-DnsName.
    • Check whether the conditional forwarder configuration is still pointing to the correct DNS servers.
    • Review the DNS Server event logs for any timeout, SERVFAIL, or connectivity-related errors.

    If the partner has recently migrated or replaced their DNS servers, the conditional forwarder may need to be updated with the new DNS server addresses.

    Please let us know the results of the above checks, and we will be happy to assist you.

    Hope you found something helpful here. Please let me know if you need further assistance.

    If this answer could solve the issue, it's appreciated to accept the answer.

    Thank you again for your patience and support!

    Ivy Bui

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.