Why Windows Server 2012 in the branch is not registered in the DNS Central office?

Hello.
Deployed in the branch domain controller, in case of loss of communication with the centre.
The Central office network 192.168.1.0/24 (the address of the dc is 192.168.1.1)
The branch network 10.0.0.0/24 (the Address of the client 10.0.0.10)
The server is not registered in DNS domain controller of the Central office.
Ping in both directions over IP.
(The IP settings of the customer FILIAL manually set the first dns 192.168.1.1)
Between the branch and the center of the OpenVPN tunnel.
nslookup from the server of the branch:
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 a 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 gateway branch
 2 105 ms 105 ms 105 ms 10.8.0.1 - OpenVPN
 3 107 ms 107 ms 120 ms 192.168.1.1 controller of the Central office.

Trace complete.

In the logs of the client error not found. In the settings of the network adapter are show - register in dns and registered dns suffix.
September 26th 19 at 11:49
3 answers
September 26th 19 at 11:51
well on this server the dns is lifted ?
in the settings of tcp/ipv4 first DNS should be 127.0.0.1 the second SP of the second controller
September 26th 19 at 11:53
oia
The second domain controller yet. because the computer branch is not registered in the dns Central office, and in domain enter it I can't. Without entering the computer into the domain controller it does not deploy?

UPD:
Why the dns server of the Central office can ping, but dns requests not responding.
If you leave the dns server of the Central office, it loses the connection with the domain.
Whether this restriction to give a bunch of OpenVPN?
if there is no DC on the server and not in domain then he should not get in the DNS server and to create an entry , look at the settings of DNS zones that someone there can update - verona_Dibbert90 commented on September 26th 19 at 11:56
September 26th 19 at 11:55
Without entering the computer into the domain controller it does not deploy?

Not deploy.
1. On a future CD of the branch configure DNS 192.168.1.1 + 10.0.0.10
2. Check ping availability of the Central CD
3. Raise the role of AD in the branch + the role of DNS + DHCP (if needed)
4. When all will rise on CD branch, run the command repadmin /showrepl
5. If there are no errors, synchronization between controllers began.
Thanks for the advice, but didn't work.
DNS Central server is not available. (nslookup to it, too, cannot be referenced).
Banchmark checked DNS - no dns access from the Central office. - verona_Dibbert90 commented on September 26th 19 at 11:58

Find more questions by tags Domain name systemWindows Server