Replies: 2 comments 2 replies
-
Thanks for the post. Loading block list in memory is done for two reasons, first is performance and second is to avoid dependency issues in core DNS server. Like for example, if you have DNS server running on an old Ubuntu 18.04, the Sqlite support for it has stopped and so the Query Logs (Sqlite) app will fail to work on it. If it was used in core DNS server then the DNS server would have stopped working and you would be forced to upgrade OS with unplanned downtime. Having mysql dependency means that you will need to administer a DB server too which adds another task for installing and maintaining the DNS server. It still possible to have a DNS App that uses a database backend and provide blocking feature. But it depends on the use-case since in most cases, there is sufficient RAM available on the server to have a reasonably large block list loaded in memory. |
Beta Was this translation helpful? Give feedback.
-
Well you can make it optional. Ofc it would be slight slower than memory. I dunno if sqlite is fast enough for this job or it would better to use MySQL but currently my DNS Server is using 2GB of memory due the blocking lists. Anyhow please consider it for a future release sometimes it's needed to do a restart of our servers. Thank you |
Beta Was this translation helpful? Give feedback.
-
Hello,
Would be possible instead of loading all the blocking lists into the memory to use a disk database ? (sqlite or mysql etc)
Thank you
Beta Was this translation helpful? Give feedback.
All reactions