Для того, чтобы из офиса одного разрешались имена внутренней сети домена в другом офисе, помогла следующая подсказка. На микротике настраивалось. Офис соединен по L2TP с серверной, и теперь видит внутренние имена серверов.
Mikrotik site-to-site L2TP + Split DNS
So I got sick and tired of adding hostnames for each and every internal server’s IP address at my home…
I finally came up with a few MikroTik firewall rules that would allow you to resolve and reverse DNS lookup internal names from your office’s DNS server, while performing ALL other DNS queries from your default (ISP) DNS servers.
For example, my setup looks as follow:
- My office is using the *.mydomain.co.za domain name for all our servers
- Most of our servers share public IP addresses, but each one of them have unique internal IP addresses (192.168.*.*). I need access to the internal IP addresses, because SSH is only enabled from inside
- The DNS server is hosted on 192.168.0.1
My primary DNS server on my home MikroTik is Google’s DNS server: 220.127.116.11
For instance if I’ll try and lookup www.kalahari.net, then my MikroTik will query it from 18.104.22.168
Whenever I try to lookup anything.mydomain.co.za, then the Layer-7 regular expression matches and then the DNS query is forwarded to my office’s DNS server, which will respond with like 192.168.0.2 IP address. Without the rule, I would’ve gotten something like 22.214.171.124 and then not be able to get SSH access to anything.mydomain.co.za.
The regular expression would also match the reverse DNS lookups (192.168.*.* — please take note that the IP range is in reverse in the regular expression), like when I would lookup 192.168.0.3, it would also forward the DNS lookup to my office’s DNS server and reply with like myhost.mydomain.co.za, instead of ‘Non-existent domain’ that 126.96.36.199 would give me.
/ip firewall layer7-protocol add name="MyDomain DNS" regexp=\ "mydomain.co.za|[0-9]+.[0-9]+.168.192.in-addr.arpa" /ip firewall nat add action=masquerade chain=srcnat comment="NAT to MyDomain DNS" disabled=no dst-address=192.168.0.1/32 dst-port=53 \ protocol=udp add action=dst-nat chain=dstnat disabled=no dst-address-type=local dst-port=53 layer7-protocol="MyDomain DNS port forward" \ protocol=udp to-addresses=192.168.0.1 to-ports=53
If you’re using those rules, please remember to change:
- the mydomain.co.za, with your own office’s internal hostnames/domain.
- the 192.168.0.1 IP address with your DNS server address of your office
- [0-9]+.[0-9]+.168.192 part of the regular expression with the reverse of your office’s internal IP range. Like [0-9]+.[0-9]+.168.192 is the reverse of 192.168.[0-9]+.[0-9] aka 192.168.*.*
I hope this is useful to some of you guys out there who are using VPN connections to your office
We have Neotel Neobroadband 5Mbps Fiber at our office, but we had endless issues with it, where a reset of the Cisco router fixed it. Luckily the colleague of mine had a network diagram (with the VLAN tags), so we simply removed our Cisco router (that Neotel gave us) and plugged it in directly on our MikroTik RB1100 and now our Internet is pumping again.