Thanks for posting in Q&A platform.
I have tested in my lab and found that this phenomenon was due to the order we configured DNS role and AD DS role.
If we add DNS role first, then add AD DS role and promote this server to a domain controller, then there will be 2 DNS server in DNS Manager. One is named with hostname and another on is with FQDN of this server.
If we directly add AD DS role on this server and specify this domain controller capabilities as Domain Name System (DNS) server, then there will be only 1 DNS server in DNS Manager named with FQDN of this server.
Normally, we recommend directly add AD DS role and configure this server as DNS server in AD DS configuration wizard. Or if the DNS resolution can work correctly, I would suggest you could just ignore this issue.
Best Regards,
Sunny
----------
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.