We would like to extend a huge debt of gratitude for Mikrotik’s rapid and appropriate response to the issues we recently had related to a new updated version of RouterOS and changes that were made to the way the OS handles static DNS entries.
We were a bit surprised when we were forced to make changes to the format, and in doing so, had discovered that RouterOS needed some optimizations, which Mikrotik software engineers were happy to work with us, and roll out an update to RouterOS that optimizes the import speed of large blacklists on Mikrotik RouterOS.
They also were generous and advised us on how to appropriately eliminate an issue we were having with our dns blacklist format. I would like to thank the members of the Mikrotik public forum for help getting the regex format corrected.
We have retooled our backend logic which has had a dramatic impact on the size and contents of our blacklists, just another reason for us to retest the RouterBoards we have available to see which blacklists are able to run on them and which ones cannot. We posted the results of our findings in the following chart.
We also added two new routers to the chart, the map2n and 951G-2HnD. Which we recently received for testing. We have prepared a compatibility chart for your review.
Mikrotik compatible conversions of our blacklists are available to all subscribers in .rsc import script formats for both Mikrotik Web Proxy Access Blacklist and Mikrotik DNS Access Blacklist. Subscribe Now.
Test it for yourself! Download this sample Mikrotik Web Proxy blacklist tik-ads.rsc
Subscribe Today – Paypal or Credit Card Accepted.
Flat rate subscription. Select a membership option & subscribe.