I.e. if I enter 192.168.10.1 as DNS at the branch office, you can surf and call up the static DNS entries. But the domain ctroller query doesn’t work properly.
If I enter the DNS 192.168.2.10 (domain controller) at the branch office, everything works immediately. However, only as long as the VPN exists. If the VPN breaks off, everything is at the branch office.
What better way to solve this?
I have already tested Wireguard and L2TP/IPSEC as VPN.
It wouldn’t as AD DNS contains various special subdomains. At the remote site use the Mikrotik as the DNS server and add a static DNS FWD entry for your AD domain pointing to the AD server.
Yes. Historically something like:
/ip dns static add regexp=“your\.domain$” forward-to=192.168.2.10
but in newer versions the following is more efficient:
/ip dns static add type=FWD name=your.domain match-subdomain=yes forward-to=192.168.2.10