No direct zone _msdcs.my.domain, how to add?

Question

Domain Name System

Purpose: Adding a second Win2012r2 domain controller.
Situation: Before adding a backup DC to the network, you need to run dcdiag tests . There were no problems, that is, in all tests there was a pass check.
But in Win2012r2 there is a Best Practices Analyzer, and in it I found this entry.

I immediately went to dns to confirm this fact.
As it turned out, there really is no such zone.

But there is no-ip.biz for ddns. Used for rdp connection by name.
My next steps:On the test bench, I set up a domain network on the same Win2012r2 distribution and specifically deleted the _msdcs.my.domain zone, rebooted a couple of times and ran dcdiag, and surprisingly I got errors.

The question immediately arises. Why doesn't the same thing happen on a DC in a production network? What I missed
Steps to restore the zone:
1. Stop the dns service, net stop dns.
2. I rename the netlogon.dnb and netlogon.dns files.
3. Creation of a direct zone. Main -> _msdcs.my.domain
4. Restart services: net stop netlogon & net start netlogon.
On the test bench, it started up and worked.
Noticed some differences in the structures.
In the working domain in the my.domain direct zone, there are different containers and entries in the (roughly) _msdcs folder.

I also decided to compare on the test bench and was again surprised.

In the direct entry m.local
Just a top-level entry _msdcs
Since there were many questions and unclear situations, I decided not to implement a new DC so far, so that there would be no problems with dns and ad replication.
I would be very grateful for any advice! Thank you!

Answer 1

I did not catch the essence of the question, but:
create a direct zone entry of the form: _msdcs.MY.DOMAIN
and create another direct zone entry: MY.DOMAIN
After that, run netdiag / fix
and then:
ipconfig / registerdns