Yes, there is small possibility, that problem could be on x86 routers. Anyone who is experiencing the problem with DNS in the same way, as Nando_lavras described in the first post, it would be great you can do small test. Set the configuration to your router, /system hardware set multi-cpu=no /syst...
The problem I had in version 3.x. The problem is only on a quad Xeon server where it is connected to more than 1,000 users. Simply fails to Table of so many demands and time to go mental and tables where the same set DNS are 0.0.0.0.