Project

General

Profile

Feature #6230

Increase Unbound Host Cache

Added by Clinton Cory over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Category:
DNS Resolver
Target version:
Start date:
04/21/2016
Due date:
% Done:

0%

Estimated time:

Description

Versions 2.* have a drop-down option under DNS Resolver -> Advanced:
"Number of Hosts to cache"

The maximum number of hosts presented is 50,000. This value is updated in /var/unbound/unbound.conf:
infra-cache-numhosts: 50000

Several of our servers appear to be exceeding this:
msg.cache.count=96942

The server referenced above is an R320 with a 10gig NIC. It frequently passes over 1Gb of traffic with several thousand clients.

Additionally, several tuning guides recommend increasing this value to 100,000. Here is one of them:
https://calomel.org/unbound_dns.html

Rather than hacking something outside of the webGUI I feel it'd be of value to add 100,000 as an option in the drop-down.

Associated revisions

Revision 102446a2 (diff)
Added by Phillip Davis over 3 years ago

Feature #6230 Increase Unbound Host Cache

This is very easy to do, if people are happy to have 100,000 as an option.

Revision c676c472 (diff)
Added by Phillip Davis over 3 years ago

Feature #6230 Increase Unbound Host Cache

This is very easy to do, if people are happy to have 100,000 as an option.

Revision b1966925 (diff)
Added by Chris Buechler over 3 years ago

Add 200000 to max cache while we're at it. Ticket #6230

Revision 2f5b3dcd (diff)
Added by Chris Buechler over 3 years ago

Add 200000 to max cache while we're at it. Ticket #6230

History

#1 Updated by Phillip Davis over 3 years ago

It is very easy to add 100,000 as an option.
PR https://github.com/pfsense/pfsense/pull/2897

#2 Updated by Chris Buechler over 3 years ago

  • Category set to DNS Resolver
  • Status changed from New to Resolved
  • Assignee set to Chris Buechler
  • Target version set to 2.3.1

Thanks Phil, merged. While we're at it, I added 200000 to the list as well.

#3 Updated by Phillip Davis over 3 years ago

The code here (and in other places around the system) has lots of repeated stuff (e.g. that array of known values appears the same 3 times), which is a recipe for maintenance errors. One day (not for this feature) all that should be cleaned up, defining constant objects somewhere central that can be referenced by anything that needs them (display code, validation code, implementation code...).

Also available in: Atom PDF