I would upgrade, but this problem seems unsolvable since 2007???

This exact issue was fixed in ROS 6.11 after my report to Mikrotik Support.

It has also been discussed here: https://www.linkedin.com/groups/1616717 ... 6799951874

I want to bump this thread again. It's still a problem. Tried with different public DNS servers (ISP, Yandex, Google DNS). Ping from client side: xeron@macbook:~$ ping assets.cld.me ping: cannot resolve assets.cld.me: Unknown host tcpdump from client side: 00:28:51.213841 IP (tos 0x0, ttl 255, id 29...

I see this issue again after 6.4 update (there were no issues since 6.0rc).

I never saw this issue from latest 5 and 6rc versions. So for me it looks fixed.

Got this problem with tcpdump running on client machine. Sorry for big copypaste. Tried to go to some http://cl.ly/ link 22:13:31.696467 IP 192.168.88.104.53065 > mikrotik.lan.domain: 44437+ A? crl.thawte.com. (32) 22:13:31.915154 IP mikrotik.lan.domain > 192.168.88.104.53065: 44437 2/0/0 CNAME crl....

As for me, problem fixed after 5.17.

My problem was described at http://forum.mikrotik.com/viewtopic.php ... 43#p307422.

UPD: After update from 5.17 to 5.18 problem returned.

Oh sorry for bumping old thread, I think it's related to http://forum.mikrotik.com/viewtopic.php?f=2&t=58243

I have problem with random resolve issues since 5.x version too, I can't remember, but it's about 5.10, may be earlier. And it's strange, browser, curl/wget and any other software can't resolve name, but nslookup works without problems. So usually I have: xeron@macbook:~$ wget — can't resolve xeron@...

I have problem with random resolve issues since 5.x version too, I can't remember, but it's about 5.10, may be earlier. And it's strange, browser, curl/wget and any other software can't resolve name, but nslookup works without problems. So usually I have: xeron@macbook:~$ wget — can't resolve xeron@...