hide-sensitive is a working export command for me on 7.9.2 and 7.10rc5. Is it just not needed anymore?
Yes, the unvalidated unique value is max concurrent queries, setting it to 0, DNS no longer responds…
But it is a setting that is only done manually, it is not the default one, it is a user error that does not know what he does …
RouterOS can’t prevent all user errors…
Which is strength and weakness of ros…
RouterOS is not a training program...
I agree with you that such parameter values, unless they have some special meaning that is useful (like “infinity” or “not checked”), should
not be allowed.
As I wrote before, it happened to me too, way back in 6.3x somewhere, that after an upgrade (I think) these parameters were set to zero.
Maybe it can be explained by some race condition or other error during the upgrade processing?
Anyway, when 0 is not a useful value the code should replace it with the default when it encounters it, and refuse it when the user tries it.
+1
maybe should change title to 7.10 stable,
http://forum.mikrotik.com/t/v7-10-7-10-1-and-more-stable-are-released/167423/1
I think it’s same issue.
I have many forward-to rule in dns-static.
it works on 7.9.2, but random lost happen on 7.10 stable.
Moreover, I have conducted tests and found that if no rules are configured in dns-static, it does not cause this issue.
It seems that the DNS resolver is crashing.
- This thread is about RC3. If you have problem with Stable make a new thread.
- What has MT written about your SUP?
- Title of this thread is just stupid. This version may work for 99% or more of the user out there.
Example tiltle.
Take care, if you have this or that, it may break, so test before upgrade.
Have you use Netinstall and started from a clean configuration? No backup/restore/upgrade?
It’s really a random serious problem and I can’t catch any useful logs, so I think maybe the DNS server crashed before print logs
MT has written nothing
I don’t use Netinstall and started from a clean configuration because just downgrade to 7.9.2 or an early version without any problem. I think if there is a problem appears, just reinstalling the system will never find the reason.
There is no export, but at least you have deigned, not like other fools, to give a minimum of explanations and do some tests.
Thank you.
As a potential workaround block access to dns resolver from WAN port and do not flush dns cache on every ppp reconnect.
I assume you read about its configuration somewhere, or is it the classic generic rule of not opening DNS to the world?
Thanks, I try it
Is a RouterOS instruction (?) or is the habit of some ISP?
(see, it always works… 
)
Looking forward to @mrz’s kind reply…
So if a user disables the firewall that is there by default,
(or doesn’t configure it correctly, since the model was never specified)
allowing the whole world to use the RouterBOARD as a DNS server (and optionally, a DDoS amplifier),
and moreover it sets in the ppp profile that at each reconnection it must unnecessarily delete the DNS cache…
DNS hangs.
I don’t think it happens on RouterOS 7.10x only, and that’s why so far there has only been 1 (or 2 if the problem is the same) report…
Boys … ROS connects people … try to get calm
i know one case with a ccr1036 and ccr2004 with a similar problem starting with 7.9.2, persist after upgrading to 7.10, was escalated to support, waiting for answer
I’m deeply dissatisfied that the forum deleted my reply. On the contrary, the perpetrators’ rudeness guys were not punished, In the future, I will not give feedback on any BUG and slowly replace hundreds of devices of Mikrotik in my company including switch. I will no longer promote this brand to my customer. In the end, this serious problem from the first 7.10 beta version including the developed version of 7.10appha44-7.10appha236 lasted until the stable version. Congratulations to @rextended and @anav for their great contribution to Mikrotik in the future.