Hello,
I need to setup DNS on my mikrotik (RB1100). The interface between mikrotik and my pc is :
Mikrotik : 192.168.0.113/30
PC : 192.168.0.114/30
I want to setup my mikrotik such that mikrotik resolves the DNS and keep the entry in the cache from future use. I want to use open dns 208.67.220.220.
I have tried doing the following :
IP → DNS → Setting
Server : 208.67.220.220 and Allow Remote Requests.
Then when in my pc, i put the address 192.168.0.113 for dns server then dns is not resolving.
What am i doing wrong or what else needs to be done for this to work.
@inertia setting up dns service on mikrotik is a pretty straight forward configuration, from what I understood there should not be a problem with your configuration, what I suspect there might be a problem with other setting.
can you ping 208.67.220.220 from mikrotik..?
does your internet connection is properly set up..? test by doing ping to 8.8.8.8 (google dns), check your IP Route setting, make sure there’s a route to 0.0.0.0/0 via the default gateway
have you forgot to masquerade/src-nat your local network 192.168.0.113/30 so that private ip address can be resolved to your public ip address
i have strange problem also with DNS from last 3-4 days
i use Mikrotik routerboard 493 mikrotik version 5.2
and all is good, but now not..
my problem is.. SLOW opening web page, when i resolve DNS VIA mikrotik os, and when is DIRECT on modem.. speed is good
Download is good 4 Mbit via mikrotik or direct, that is not problem, but only in DNS
i try restore backup from last mount.. nothing ???
PC is on MS windows 7 x64
only if i downgrade back to 4.x routeros ? but i dont understand.. all is working just fine, and now i have these problem, and i am nothing modified is mikrotik v5.2.
I too have noticed this problem with v5.2 (and 5.1) and my 493G. Whenever DNS resolve is handled by RouterOS own DNS the target website loading time increases a lot. It doesn’t occur always though. Sometimes everything works fine but after a while lag reappears; Sometimes it even timeouts before resolving DNS request. Configuring clients to directly use ISP DNS fix this delay issue thus I assume RouterOS cause it.
I’ve also noticed similar problem with DNS (ROS 5.2).
IMHO problem is with DNS cache, when it contains hundreds of records.
Try to increase cache size and decrease max. TTL, my current settings are:
/ip dns
set allow-remote-requests=yes cache-max-ttl=1h cache-size=8192KiB max-udp-packet-size=8192 servers=208.67.222.222,208.67.220.220
With these settings everything works good, no problems with DNS at all, when previously customers complained that DNS doesn’t work properly.
I don’t want to revert back my DNS settings on production routers.
Maybe someone with affected router is able to generate supout.rif and send to MT support.
also, if possible, you could try to time how fast resolve happens and weather there is difference - entry is in the cache or not. Is there difference if you do that through IPv6 or IPv4?
doing digs against test-bed RB800 router
first resolution:
$ time dig cnn.com @mt
[boring part of dns info ommited]
real 0m0.127s
user 0m0.000s
sys 0m0.000s
already cached
$ time dig cnn.com @mt
real 0m0.008s
user 0m0.000s
sys 0m0.000s
@janisk
There was a problem with RB450G/ROS 5.2, complete DNS lock-up, no response to requests from LAN.
Cache was over 800 records and unfortunately there was no time to make some diagnostics.
Router was accessible and was restarted to let people work.
I’ve changed DNS settings to keep cache as small as possible and now it works good.
I am also having the same problem, But mostly with static dns names.
I have added 2 static dns names so that i don’t have to type the ip address of my web server, and when using the mikrotik it takes up to 2-5 seconds to resolve the dns name.
I have reverted to just updating the host file on my OS.
Running RB751G-2HnD with RoS 5.23
Cache Size: 2048
Cache Used: 178
I only have 4 static entries on the dns, so this cant be due to large volumes.
I have a similar problem with DNS delay and routeros 5.23.
I need a few static addresses for an internal web server.
After a few minutes (not exacly sure how many, maybe 10+) when I ping one of the static names the first ICMP reply gets no response (presumably timedout). The following few pings work fine. Also several minutes later it all works fine. Then after the time internet (10min) the same happens the first ICMP ping fails.
This causes a problem with a web app we’re building as the browser prompts to refresh thinking the name cannot be resolved.
I’ve tried changing the cache size and the TTL but neither seems to help.
I would ditch the routerOS DNS for a Linux host albeit the hotspot DNS names are published so using raw addresses would be a step back. (i.e. people would need to login to the hotspot for the DNS traffic to get through).
Anyone got a fix for routerOS or workarounds?
Thanks
Running across the exact same issue on v6.4.
2 static rules, one of them is regexp based (but switching to just the non-regexp one doesn’t change things much).
Sometimes it works fine, sometimes it takes 4-5 seconds for resolution.
Curiously, for partial matches to the regexp static rule, Chrome reports the DNS entries in its cache as expired the moment they get resolved. As if TTL was 0. The TTL for the static rules on the router are set to 1d.
Edit: Scratch that, i’ve just had it happen with static rules disabled.
Edit2: If, however, i simply don’t use Router OS DNS at all, things behave normally and resolution is fast. So something is definitely bonkers with Mikrotik’s DNS.
Same here with 3 RB450G’s (running v6.11, 6.12 and v6.13). When the cache holds a lot of records (hundreds), it starts to fail resolving random names. After a while it will work again, or after manually flushing the cache. Using the dns server directly (bypassing the routers) it works fine.
> ip dns export
# may/28/2014 20:47:37 by RouterOS 6.11
#
/ip dns
set allow-remote-requests=yes cache-size=32768KiB servers=10.0.0.1,10.0.0.2,10.2.0.1,10.1.0.1