![]() ![]() After the historic information has been imported from the database, we start the DNS/DHCP resolver. We extend the already existing multi-threading in FTL to provide an even faster experience. On startup, it launches a number of threads, each dedicated for specific tasks. FTL v4.0 has always been multi-threaded for speed and efficiency. We implement dnsmasq into our code using the modular nature of the C language. Instead of a “must have”, the log file will become an “opt-in” feature! Due to the direct integration into the resolver (using “FTL hooks”), we can compute statistics without any need for a log file.We can provide stats on cache usage and probably much more, which has been previously unavailable.Processing will be much faster since we interact directly with the resolver instead of periodically parsing a log file.Upstream updates to dnsmasq can easily be integrated into our code since we don’t modify its code heavily.No more dnsmasq version compatibility issues since we develop and provide the DNS resolver and FTL together.The Non-technical Details FTLDNS has many benefits for you as user: Get your hands on this sweet mug to help spread the word. One of the many ways to support us is purchasing from our Swag Store. So we’re officially announcing FTLDNS™ and you can find it right here. as the author of the modification ftl remastered stopped any further work above his modification for a long time ago, and the continuation of the work is not foreseen, it was decided to adapt the above mod to the current version of the ftl game. We have a proof-of-concept implementation of FTL already developed and running. The obvious choice for this is, of course, to base it on dnsmasq. Each OS distribution provides a different version of dnsmasq and this can prevent users for getting a flawless Pi-hole experienceĪll these problems lead us to the idea of actually integrating a DNS resolver directly into FTL.There are some details of the DNS server we do not have access to (like cache usage) through the log file alone.If a user chooses to disable logging, we’re unable to compute any statistics at all. ![]() While this works, doing it through a middleman (a log file) is obviously quite inefficient With FTL, we generate a variety of statistics by interpreting dnsmasq‘s log file.However, as the project has grown and evolved, we reached a point where we started looking into providing our own powerful resolver for a few reasons: We have used dnsmasq as our DNS/DHCP server since Pi-hole began. We bring the two pieces of software closer together while maintaining maximum compatibility with any updates Simon adds to dnsmasq. In a sentence, FTLDNS™ is dnsmasq blended with Pi-hole’s special sauce. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |