Hi,
why does the Ping-tool resolve “www.cnn.com” to 151.101.1.67?
The router has no config, no IP, no route(s) and even no DNS server entry:
Perfectly resolved DNS in an IP…
And even more suspicious, a packet-sniffer shows nothing related to a DNS resolution…
How (and why) can the router resolve the DNS-name in an IP?
The host is resolved in Winbox on the client device..
Try this in Terminal:
[admin@MikroTik] > /ping [:resolve www.cnn.com]
failure: dns server failure
Have you cleared DNS cache?
Winbox is using your computer’s DNS settings.
resolve command in terminal is using the router’s DNS settings.
-Chris
Hi, thanks!
Is this somewhere documented? I searced prior this thread a lot, but found nothing regarding this behaviour…
Not really. It has been mentioned before on the forum.
http://forum.mikrotik.com/t/router-cant-resolve-address/94369/3
I just confirmed that Winbox 3.0 still has the behavior where typing a hostname into “Ping To” will use the client’s DNS resolver, and not the remote Mikrotik’s. I put a hostname into the ping tool, and the Mikrotik tried to ping to my office’s internal IP and not the public IP that external hosts would get from DNS.
Ive been checking DNS this way for a while but just came across this issue just now. I guess it makes sense if you think about it as the Winbox application resides on the PC not the router but this is very misleading IMO. Moving forward, Ill be testing DNS via address-list but I would consider this a bug. Are there any use cases where it would be needed? I guess if youre accessing a remote Mikrotk via DNS name, then yea, it would need to use the client DNS. But Im sure Mikrotik could code in the different scenarios. Maybe I should reach out to Mikrotik support?