Share via

Replication unable to be started on a DAG Exchange 2019 server

Bryce Gerber 0 Reputation points
2025-11-03T21:07:25.58+00:00

DAG based 2019 Exchange on prem environment.

The health test of the TCP listener for the Microsoft Exchange

Replication service on server 'Bxxxxxx2' failed. This server

cannot participate in replication until the error is resolved.

Error: Couldn't determine the IP address for server 'Bxxxxxx02'

because DNS didn't return any information.

How does one fix this. AI and other help are saying that it has 3 A names ad 1 AAAA name but DNS servers are not showing that. Quering the server shows that it does. I just can't get it to go back into replication again.

We are also having an issue with repeatedly being asked to put our passwords in our environment.

Exchange | Exchange Server | Management
Exchange | Exchange Server | Management
The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Vergil-V 6,375 Reputation points Microsoft External Staff Moderator
    2025-11-04T04:25:39.7166667+00:00

    Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.
    Hi @Bryce Gerber 
    Thank you for reaching out to Microsoft Learn Q&A!  
    Regarding the error message “Error: Couldn't determine the IP address for server because DNS didn't return any information”, I found a related article suggesting that you ensure the option “Register this connection's addresses in DNS” (including both IPv4 and IPv6) is selected on the network adapter. 

    User's image

    Reference: Exchange restarts with Stop Error - Exchange | Microsoft Learn 

     
    After confirming this setting, please run the following commands: 

    • ipconfig /flushdns (clears the DNS cache)  
    • ipconfig /registerdns  (forces an update of the DNS records)

    Once completed, restart the Microsoft Exchange Replication Service to fully apply the changes: 

      Restart-Service MSExchangeRepl 

     

    Regarding the issue of repeatedly being asked for a password, could you please provide more details? Is this happening in the Outlook desktop app or another application? 

    If it is the Outlook desktop app, you can try the following steps: 

    If it is not Outlook desktop, could you share a screenshot of the password prompt? This will help us better understand the situation and provide more accurate guidance.   

    Before sharing, kindly ensure that any personal or sensitive information (such as your email address, organization domain name, etc.) is removed to protect your privacy and to ensure your reply remains valid. 

    I sincerely hope this information helps clarify your situation and supports you in resolving the issue. Please don’t hesitate to reply if you have any updates. 

    Thank you for your understanding. 

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

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.