Hello,
I had a funny issue today - A user reported that he couldn’t get to a website that he knew wasn’t malfunctioning.
Curious, I tried a nslookup from my machine:
# nslookup domain.com
Server: 192.168.1.1
Address: 192.168.1.1#53
** server can't find domain.com: NXDOMAIN
The next thing I tried was using Google’s DNS:
nslookup domain.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: domain.com
Address: 208.113.134.XXX
Uhoh.. A problem with our ISP’s DNS server? Nope - our ISP’s DNS (the same DNS that is set in the Mikrotik router) returned the correct IP.
Next thing I tried was logging into our router, to see if there is a problem with DNS:
[admin@router] > /ip dns print
servers: 220.233.0.3,220.233.0.4
allow-remote-requests: yes
max-udp-packet-size: 4096
cache-size: 2048KiB
cache-max-ttl: 1w
cache-used: 2048KiB
Ah.. DNS servers are set to our ISP’s, so that is OK. But what is this ‘cache-used’? Surely the router wouldn’t stop serving DNS requests because the cache is fulll?
[admin@router] > /ip dns cache flush
Oh - now I can resolve the website. The Mikrotik’s cache was filled and so it decided to just stop doing DNS lookups.
- Is this normal/expected behaviour?
- What is the recommended DNS cache size?
RouterOS 5.12 on RB1100AH.
Thanks
Jeremy