RouterOS is a closed system. You can’t “install” any 3rd party tool. You could use MetaRouter, which allows you to run other OS “inside” routeros, like a virtual machine.
Thanks. I clicked on that, and then tried to ping devices who’s names are known to the router. But now my devices think that all host names have the IP address 92.242.140.2 instead of something in the 192.168.1.0 range.
92.242.140.2 belongs to some “Barefruit Ltd”. There are threads on this address on the internet.
May this be some kind of misconfiguration on your client?
Your dns settings should point to your mikrotik.
Depending on your OS, try a command like “nslookup” or “dig”.
They should report which dns is answering your request.
If it is not your mikrotik, check the dns settings on your client.
Are you saying that I should I add 192.168.1.1 (the router’s LAN IP address) in “servers:”? (I think you are, but want to be sure before cocking something up…)
cat /etc/resolv.conf
#
# This file is automatically generated.
#
nameserver 192.168.88.1
where 192.168.88.1 is the mikrotik router.
In this way, when I ping names statically assigned by my router’s dhcp server, they are resolved by the router, and only if unknown to it they will be passed to the outside dns servers.
On your client pc/server (that is, not from the router)
nslookup router
Server: 192.168.88.1
Address: 192.168.88.1#53 <<<---- this is the dns resolving the name, the mikrotik router
Non-authoritative answer:
Name: router
Address: 192.168.88.1
If I change the dns settings (i.e.: 8.8.8.8) on the client, and I get:
It does, along with my ISP’s name servers (presumably because the router DNS has “allow-remote-requests: yes”.
$ nslookup router
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
Name: router
Address: 192.168.1.1
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.1
nameserver 68.105.28.11
nameserver 68.105.29.11