I have a cAP ac and a cAP lite both on version 6.47.10. When I try to search for updates I get the following error: could not resolve dns name. I also can’t ping from either of them (/ping google.com or /ping 8.8.8.8 ), but I have internet access and can ping normally from devices connected to them. I searched the forum and found similar cases, but unfortunately none of them solved my problem.
Usually when I see this, I know something is wrong with local DNS on the device where it happens.
Your devices seem to get IP via DHCP, so the problem is most likely there.
Check on the main router where IP leases are being distributed if DNS server is specified in Network.
Devices obtaining a leases, should also get the DNS server to look for.
Shortcut:
On those 2 devices, use this on terminal or via Winbox (but I prefer to solve the problem at the source):
/ip dns set servers=8.8.8.8 (or IP of your router)
I’ve been afflicted with the same issue. Setting the DNS server on the router doesn’t solve the problem. I can access the download site through RouterOS but not from RouterOS. I even added a static DNS address for the download server. Still no luck.
I tried doing as you said, but the problem still occurs. I set the DNS as 8.8.8.8 and tried pinging it right after and I still get timeout. I had set static DNS on them before (my router 192.168.1.1 and 8.8.8.. I don’t underst why the devices connected directly to the router and also connected to the MikroTik AP’s have no apparent problem connecting to the internet, I can for example ping from any of them just fine.
I tested pinging my router (192.168.1.1) and I get timeout, but when pinging the other AP (192.168.1.101) or another host (192.168.1. it works. So far I couldn’t ping any internet IP. Could there be something preventing the AP from “talking” to the router?
They are both cap device under control of capsman ?
You can also upgrade them via capsman manager, i think.
Or reset again to caps mode ? There is no config waisted.
I didn’t use the Quick Set mode to configure them, but on the cAP ac I set up CAPsMAN and both of them are provisioned(?) as CAP’s. If I access the Quick Set option it shows that on the ac it is in Home Mesh mode and the lite is on CAP mode. I actually upgraded the ac by uploading the package and rebooting it (it’s now on v7.10.2), but that’s just working around the problem, I still can’t ping the internet from it. I can try resetting them later when there’s less people using them, but if I remember correctly even after resetting I couldn’t search for upgrades.
I have seen this happen as well, but never was able to find the root cause.
Even on routers where the DNS clearly is configured correctly, i.e. you see resolved names in the cache, it still can fail for RouterOS upgrade.
It also seems to cache error status somewhere, because when you change the DNS config it just shows the same error.
Sometimes it can be fixed by rebooting the device before attempting the upgrade.
Something is definitely goofed up. Rebooting, upgrading, nothing removes the error. I can resolve www.mikrotik.com from tools/ping/ in RouterOS, so I know DNS is working.
I can see download.mikrotik.com in the cache.
I know how frustrating it is. Several times I have just downloaded the required .npk files manually and uploaded them to the router for an upgrade, which then of course worked OK.
But it is unclear what is failing and why. Certainly it is not a network issue or a DNS settings issue.
I can manually upgrade without issues. However, @holvoetn is correct, pings won’t resolve from the terminal. Now I can’t rest until the problem reveals itself.
One guess off what it may be: at some point I noticed that Cloudflare DNS mangles the names returned from DNS requests.
E.g. when you request mikrotik.com it will return results for mikrotik.cOm
Maybe in this specific case that is not matched to the query and the resolve fails.
That would affect you when you use 1.1.1.1 or 1.0.0.1 as DNS resolver.
(I have not attempted to reproduce the issue with that setup, but I removed 1.1.1.1 and 1.0.0.1 as DNS server after noticing this, and I guess it may have been the reason for my problem in the past)
I never use, or used, CAPSMAN. RouterOS went from successfully updating packages to spawning an error after anupgrade (I can’t recall which one). There were NO configurations changes. I’m using the same configuration I’ve been using for a few years.
Do you use 1.1.1.1 or 1.0.0.1 as a resolver? It may be the reason.
I just tried to upgrade a router that has 1.1.1.1 and 8.8.8.8 as resolvers, with log enabled on the outgoing DNS request.
I saw it first try 1.1.1.1, then a second later try 8.8.8.8, and then it succeeded.
So my suspicion that it does not like the replies from 1.1.1.1 (posted above) seems to be confirmed.
Now the error has changed. No update, no configuration change, and same check for updates button. It no longer give an ERROR: could not resolve dns name message. Now I get the message: ERROR: connection timed out
Hi, not sure this topic is still open or resolved somewhere. I had the same problem of DNS error issues trying to upgrade my Mikrotik router. Seems the Firewall config was causing my issue, there is a standard rule that states don’t accept anything not from LAN. If your router is using a subnet not defined in the LAN subnet the packets will be dropped, hence the DNS request will not pass.
Hope this helps others resolve this “issue”.
Hello, could you be a little clearer in your explanation? I have the same problem, but my router only accepts connections when “general drop” is deactivated. I wanted another way to update without having to disable this rule.
. I don’t underst why the devices connected directly to the router and also connected to the MikroTik AP’s have no apparent problem connecting to the internet, I can for example ping from any of them just fine.