Hi @Yandri Eko ,
I'm glad to hear you solve the problem ,if you have any issue about Exchange, you are welcome to raise a ticket in this forum. By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others.". and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:
[DNS Lookups Error when try to check server from Public ECP]
Issue Symptom:
We've 3 Exchange Server 2016 (2 servers already patched with KB5023697, & we're not yet update 1 server with the KB's), those currently running with Windows Server 2016. And also we've 3 Exchange Server 2019 with WS 2022 in DRC Site (Newly Created). The problem is when we try to check DNS Lookups settings for servers that we already patched, from Public ECP (external url) it got an error says that access denied (before patching it normally running, i mean we can see DNS Lookups settings), same problem comes from all servers in DRC's Site that's using Windows Server 2022 & Exchange Server 2019
The solution:
the issue is resolved after enabling TLS 1.2 on Exchange Server Primary site Servers.
You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!