Services: Unbound DNS Forwarder: Advanced Settings

Unbound is a validating, recursive, and caching DNS resolver. unbound_advanced 1.4.8 Services: Unbound DNS Forwarder: Advanced Settings /usr/local/pkg/unbound.inc Unbound DNS Setup Unbound specific settings

Services

pkg_edit.php?xml=unbound.xml&id=0 unbound unbound.sh unbound Unbound is a validating, recursive, and caching DNS resolver. Unbound DNS Settings /pkg_edit.php?xml=unbound.xml&id=0 Unbound DNS Advanced Settings /pkg_edit.php?xml=unbound_advanced.xml&id=0 Unbound DNS ACLs /pkg.php?xml=unbound_acls.xml Unbound DNS Status /unbound_status.php Advanced Settings listtopic hide_id Hide Identity If enabled, id.server and hostname.bind queries are refused. Default is disabled. checkbox off hide_version Hide Version If enabled, version.server and version.bind queries are refused. Default is disabled. checkbox off prefetch Prefetch Support If enabled, the message cache elements are prefetched before they expire to keep the cache up to date. Enabling this option causes an increase of about 10 percent more traffic and load on the server, but popular items do not expire form the cache. Default is disabled. checkbox off prefetch_key Prefetch Key Support If enabled, DNSKEY's are fetched earlier in the validation process when a <a href="http://en.wikipedia.org/wiki/List_of_DNS_record_types">DS</a> is encountered. This helps lower the latency of requests but does utilize a little more CPU. Default is disabled. checkbox off harden_glue Harden Glue If enabled, Unbound will only trust glue if it is within the servers authority. Default is enabled. checkbox on harden_dnssec_stripped Harden DNSSEC data If enabled, DNSSEC data is required for trust-anchored zones. If such data is absent, the zone is becomes bogus. If disabled then and no DNSSEC data is received, then the zone is made insecure. The default is enabled. checkbox on unbound_verbosity Log level verbosity Select the logging verbosity. The different levels are described as follows: Level 0: No verbosity, only errors are logged. Level 1: Provides operational information. Level 2: Provides detailed operational information. Level 3: Gives query level information and output per query. Level 4: Gives algorithm level information. Level 5: Logs client identification for cache misses. select 1 msg_cache_size Message Cache Size Size of the message cache. The message cache stores DNS rcodes and validation statuses. The RRSet cache will automatically be set to twice this amount. The RRSet cache contains the RR data. The default is 4 megabytes. select 4 Outgoing TCP Buffers outgoing_num_tcp The number of outgoing TCP buffers to allocate per thread. The default value is 10. If 0 is selected then no TCP queries, to authoritative servers, are done. select 10 Incoming TCP Buffers incoming_num_tcp The number of incoming TCP buffers to allocate per thread. The default value is 10. If 0 is selected then no TCP queries, from clients, are accepted. select 10 EDNS Buffer Size edns_buffer_size Number of bytes size to advertise as the EDNS reassembly buffer size. This is the value that is used in UDP datagrams sent to peers. RFC recommendation is 4096 (which is the default). If you have fragmentation reassemble problems, usually seen as timeouts, then a value of 1480 should help. The 512 value bypasses most MTU path problems, but it can generate an excessive amount of TCP fallback. select 4096 Number of queries per thread num_queries_per_thread The number of queries that every thread will service simultaneously. If more queries arrive that need to be serviced, and no queries can be jostled, then these queries are dropped. select 1024 Jostle Timeout jostle_timeout This timeout is used for when the server is very busy. The default value is 200 milliseconds. select 200 Maximum TTL for RRsets and messages cache_max_ttl Configure a maximum Time to live for RRsets and messages in the cache. The default is 86400 seconds (1 day). When the internal TTL expires the cache item is expired. This can be configured to force the resolver to query for data more often and not trust (very large) TTL values. input 86400 Minimum TTL for RRsets and messages cache_min_ttl Configure a minimum Time to live for RRsets and messages in the cache. The default is 0 seconds. If the minimum value kicks in, the data is cached for longer than the domain owner intended, and thus less queries are made to look up the data. The 0 value ensures the data in the cache is as the domain owner intended. High values can lead to trouble as the data in the cache might not match up with the actual data anymore. input 5 0 TTL for Host cache entries infra_host_ttl Time to live for entries in the host cache. The host cache contains roundtrip timing and EDNS support information. The default is 900 seconds. input 5 900 TTL for lame delegation infra_lame_ttl Time to live for when a delegation is considered to be lame. The default is 900 seconds. input 5 900 Number of Hosts to cache infra_cache_numhosts Number of hosts for which information is cached. The default is 10,000. input 5 10000 Unwanted Reply Threshold unwanted_reply_threshold If enabled, a total number of unwanted replies is kept track of in every thread. When it reaches the threshold, a defensive action is taken and a warning is printed to the log file. This defensive action is to clear the RRSet and message caches, hopefully flushing away any poison. The default is disabled, but if enabled a a value of 10 million is suggested. select 0 Custom Options custom_options You can put your own custom options here, separated by semi-colons (;). These configurations options will then be added to the configuration file. Note: They need to be Unbound native configuration options, otherwise Unbound will not work. textarea 65 5 unbound_validate($_POST, "advanced"); unbound_reconfigure(); unbound_install(); unbound_uninstall();