How to cure DNS server?

Question

Domain Name System

Hello, I ask for help in this matter, there is an office in City A and an office in city B, an IPSEC tunnel is configured between them, in City A HV3E and HV4E servers are installed on them virtual machines are deployed (Terminal, 1C, AD and others) these servers are located in the hvd.local domain, the domain controller is also deployed to Wirth. car. There is a city B in which there are also servers whose hosts are also in the HVD.Local domain, the second controller is also deployed to Wirth. machine, for a certain time everything was fine, replication worked between the HVD3E, HVD4E and HV1V, HV2V servers, then the dns server in city B was bent, the service snap-in does not open, supposedly there are no rights to start, I found articles on the Internet about this error, made recommendations, but that's not the point. Tried to lower the second AD of the hvd domain. local but the system does not allow this, referring to the unavailability of the main one, I tried to raise a new second AD, but when entering credentials to enter a new server into the domain, the system swears at the wrong username and password, although 100% correct, (I drove the server into the domain from another account, but I'm sure that I'm entering it correctly, I changed the password to a simple one in the AD directory) but it was not possible to increase the role to AD, there are pings between the servers. I do not know where to start, maybe something does not work on the first AD? Replicas do not work due to the lack of DNS on the second AD of the hvd.local domain there are pings between servers. I do not know where to start, maybe something does not work on the first AD? Replicas do not work due to the lack of DNS on the second AD of the hvd.local domain there are pings between servers. I do not know where to start, maybe something does not work on the first AD? Replicas do not work due to the lack of DNS on the second AD of the hvd.local domain
All Terminal virtual machines, 1C server, they are in another domain, there is a domain for Hosts and a domain for Wirth machines.
nslookup command from second domain controller hvd
ip address of first controller 192.168.1.15
C:\Users\i.krivintsov>nslookup dc1hvd.hvd.local
╤хЁтхЁ: UnKnown
Address: 192.168.1.15
*** UnKnown could not find dc1hvd.hvd.local : Non-existent domain

Answer 1

initially incorrect configuration. in city B, you must have a child domain on a separate subnet and in a separate site.
for example, CO - hvd.local, Default-first-site, subnet 10.10.10.0/24. city ​​B - B.hvd.local, second-site, subnet 10.10.11.0/24.
in this case, check from the domain controller nslookup <контроллер домена города Б>
from this we will dance further.
I assume that nothing has changed in routing, otherwise you need to start with this.