question

Hi,

Default Server: UnKnown this message means that there is no PTR entry (it's DNS entry to identify the server name by its IP addresse) for new DNS server. but the PTR dns entry is not required to let client send DNS requests to the server 192.168.201.11 .

check if the client is able to resolve FQDN of any machine to test if it get answer from DNS server 192.168.201:

nslookup domainName:

Please don't forget to mark this reply as answer if it help you to fix your issue

Please run;

Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt

then put unzipped text files up on OneDrive and share a link.

Hello Thmeur,
PRT record is fine

C:\Users\administrator.CLOUD>nslookup google.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.201.11

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

if i use my old domain IP it works fine, old domain 201.1 and new 201.11

C:\Users\administrator.CLOUD>nslookup
Default Server: dc.cloud.local
Address: 192.168.201.1

192.168.201.11

Server: dc.cloud.local
Address: 192.168.201.1

Name: ad2016.cloud.local
Address: 192.168.201.11

Hi,

The PTR you shared it in your last answer is for : 192.168.201.3

Create new PTR for 192.168.201.11.

Try to resolve a FQDN with local DNS suffix : nslookup dc.cloud.local to check if you get the same timeout

Please don't forget to mark this reply as answer if it help you to fix your issue

@DSPatrick

https://buzinessware-my.sharepoint.com/:f:/p/sabir/EoqULhOs4RFDo1NcpVanuhwBo_bptjnjZ0WnmoeOuz-hFA?e=qVqUgb

There is a time difference between the two domain controllers, this needs to be corrected. May need to look at the domain time service configuration. Looks like there are replication problems between the two. I'd check the event logs for more details of issues. Also check that problem clients are getting the ip address of new DC listed for DNS on connection properties.

--please don't forget to Accept as answer if the reply is helpful--

@SabirShibley-3818 Hi,

Thank you for posting in Q&A!

Please try to point the DNS server list to each other, rather than point to itself first.

If multiple DCs are configured as DNS servers, they should be configured to use each other for resolution first and themselves second. If the DC point to itself as the primary DNS server, it might cause some unexpected AD replication issue.

For more details, please refer to:
https://www.dell.com/support/article/en-sg/sln155801/best-practices-for-dns-configuration-in-an-active-directory-domain?lang=en

Hope you have a nice day : )
Gloria
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
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.
https://docs.microsoft.com/en-us/answers/articles/67444/email-notifications.html

Dear All,

Issue fixed as our firewall is blocking port 53, Thanks @Thameur-BOURBITA @DSPatrick @GloriaGu-MSFT