Winbox dns resolving depends on workstation's dns? Or is it a bug?

RouterOS General
1

From central (that has internet connection working) I can log into any of my routers with winbox and test internet connectivity with traceroute or ping tool to see if that unit has access. I test with an url (www.anypage.xxx) and after the dns resolution traceroute finds its way to the server of test… If it does, that unit has succesful internet access.

Now, if I am at a location where my laptop is connected to my network but it gets local IP only valid in my network (so laptop cannot go to the internet, no src-nat takes place for this local IP), I can still log into any of my routers of the network with winbox. BUT, from within winbox in a router ICANNOT run traceroute tool or ping to url!
I can only do such test if IP is already given. But dns does not take place!

At the same time login to same router from central (where we have internet) the tool resolves url and works fine…

Conclusion; dns resolving done in winbox session depends on internet accessibility from the machine (laptop, pc)?

This is not good. (Or is it a bug?)
Performing tools/test from within router should be like it is the router itself that performs the test…

2

Winbox uses your locally configured DNS server. To my knowledge, this is known and expected behavior.

3

“expected”? Why? If I have no internet access with my laptop but access to my router, how can I now know if dns works in the router or not? Sometimes the laptop is just mac connected or gets an IP that only works local…
I find it very weird.

4

It’s not expected and it’s not good but it is known and it is how it is. If you would like to use dns of the device you have to open a terminal…

5

hmm, so it works on terminal. In other words; me, winbox adept, am discriminated compared to the nerds that can only think and work in code… pff :frowning:

6

I had a discussion with mikrotik about this long time ago. They did not accepted that this behaviour is confusing.