Why is the Windows Server 2012 in the branch office not registering in the DNS of the central office?

Question

Domain Name System

Hello.
It is necessary to deploy a domain controller in the branch, in case of a break in communication with the center.
Central office network 192.168.1.0/24 (dc address 192.168.1.1)
Branch office network 10.0.0.0/24 (Client address 10.0.0.10)
The server is not registered in the DNS of the central office domain controller.
Ping - in both directions over IP.
(IP settings for the branch client are set manually, the first dns is 192.168.1.1)
There is a tunnel between the branch and the OpenVPN center.
nslookup from the branch server:

PS C:\Users\admin> nslookup
DNS request timed out.
    timeout was 2 seconds.
Default Server:  UnKnown
Address:  192.168.1.1

> dc.company.local
Server:  UnKnown
Address:  192.168.1.1

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

Tracert to the domain controller.

PS C:\Users\admin> tracert -d 192.168.1.1

Tracing route to 192.168.1.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  10.0.0.1 - шлюз филиала
  2   105 ms   105 ms   105 ms  10.8.0.1 - OpenVPN
  3   107 ms   107 ms   120 ms  192.168.1.1 - контроллер центрального офиса.

Trace complete.

I did not find any errors in the client logs. In the settings of the network adapter there are checkboxes - register in dns and the dns suffix is ​​registered.

Answer 1

it is good on this server the dns service is lifted?
in the tcp / ipv4 protocol settings, the first dns should be 127.0.0.1 the second ip of the second controller

Answer 2

oia
There is no second domain controller yet. because the branch computer is not registered in the dns of the central office, then I cannot enter it into the domain either. Without entering the computer into the domain, the controller cannot be deployed on it?
Why is the central office dns server pinging, but not responding to dns requests.
If you leave only the dns server of the central office, then the connection with the domain is lost.
Can such a restriction be provided by a link with OpenVPN?

Answer 3

Without entering the computer into the domain, the controller cannot be deployed on it?

Do not expand.
1. On the future branch CD, configure DNS 192.168.1.1 + 10.0.0.10
2. Ping the availability of the central CD
3. Raise the AD role in the branch + DNS + DHCP role (if necessary)
4. When everything rises on the branch CD, run the command repadmin / showrepl
5. If there are no errors, synchronization between the controllers has begun.