Project

General

Profile

Actions

Feature #2637

closed

Add ability to define dnsmasq cache size

Added by Chris Wadge over 12 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
DNS Forwarder
Target version:
-
Start date:
09/18/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Dnsmasq supports a maximum cache size of up to 10,000 records, but defaults to only 150. On most pfSense platforms, there will be more than enough memory to support the maximum cache size without negative consequences. Being able to set this value to zero would also be useful in those situations where the upstream DNS server(s) are already caching, where caching is not prudent, or where memory is severely limited. Thus, giving the end user the ability to define this value by hand would be desirable (and should be simple to implement).

-c, --cache-size=<cachesize>
Set the size of dnsmasq's cache. The default is 150 names. Setting the cache size to zero disables caching.

Actions #1

Updated by JohnPoz _ over 12 years ago

Just took a look at where dnsmasq is started in services

mwexec_bg("/usr/local/sbin/dnsmasq --local-ttl 86400 --all-servers {$dns_rebind} --dns-forward-max=5000 --cache-size=10000 {$args}");

Seems that already set to 10,000 records to me?

Actions #2

Updated by JohnPoz _ over 12 years ago

That line is not exactly what is default, I change my --local-ttl to something realistic for local static entries that never change vs 1 which is default.

Actions #3

Updated by Chris Buechler over 12 years ago

  • Priority changed from Normal to Low
  • Affected Version deleted (All)

it's already set to the maximum cache size, but is hard coded.

Actions #4

Updated by Chris Buechler over 10 years ago

  • Status changed from New to Closed

dnsmasq no longer used

Actions

Also available in: Atom PDF