<div dir="ltr">Greetings again all,<div><br></div><div>I'm having an issue where unbound isn't writing anything to the log-file I'm specifying. </div><div>My end game is doing a short log of each query (for informational purposes and testing)</div>
<div><br></div><div>my truncated config as it stands is this : </div><div><br></div><div>I've been reading the man pages and the documentation on the website and I believe this is the proper method to create a specific log.</div>
<div><br></div><div>verbosity: 3 * for queries*</div><div>logfile: "/etc/unbound/unboundLog.txt"<br></div><div>log-queries: yes<br></div><div><br></div><div>Is there something I'm missing? I've also taken ownership of the file through chown for the unbound user.</div>
<div><br></div><div>Thank you in advance ,</div><div><br></div><div>here is the full truncated config for perusing:</div><div><br></div><div><br></div><div><div> # whitespace is not necessary, but looks cleaner.</div>
<div><br></div><div> # verbosity number, 0 is least verbose. 1 is default.</div><div> verbosity: 3</div><div><br></div><div> # print statistics to the log (for every thread) every N seconds.</div><div>
# Set to "" or 0 to disable. Default is disabled.</div><div> # Needed for munin plugin</div><div> statistics-interval: 0</div><div><br></div><div> # enable cumulative statistics, without clearing them after printing.</div>
<div> # Needed for munin plugin</div><div> statistics-cumulative: no</div><div><br></div><div> # enable extended statistics (query types, answer codes, status)</div><div> # printed from unbound-control. default off, because of speed.</div>
<div> # Needed for munin plugin</div><div> extended-statistics: yes</div><div><br></div><div> # number of threads to create. 1 disables threading.</div><div> num-threads: 2</div><div><br></div>
<div> # specify the interfaces to answer queries from by ip-address.</div><div> # The default is to listen to localhost (127.0.0.1 and ::1).</div><div> # specify 0.0.0.0 and ::0 to bind to all available interfaces.</div>
<div> # specify every interface on a new 'interface:' labelled line.</div><div> # The listen interfaces are not changed on reload, only on restart.</div><div> </div><div> **TRUNCATED**</div>
<div> # interface: ::0</div><div> # interface: 192.0.2.153</div><div> # interface: 192.0.2.154</div><div> # interface: 2001:DB8::5</div><div> #</div><div> # for dns over tls and raw dns over port 80</div>
<div> # interface: 0.0.0.0@443</div><div> # interface: ::0@443</div><div> # interface: 0.0.0.0@80</div><div> # interface: ::0@80</div><div><br></div><div> # enable this feature to copy the source address of queries to reply.</div>
<div> # Socket options are not supported on all platforms. experimental.</div><div> # interface-automatic: yes</div><div> #</div><div> # NOTE: Enable this option when specifying interface 0.0.0.0 or ::0</div>
<div> # NOTE: Disabled per Fedora policy not to listen to * on default install</div><div> # NOTE: If deploying on non-default port, eg 80/443, this needs to be disabled</div><div> interface-automatic: no</div>
<div><br></div><div> # port to answer queries from</div><div> # port: 53</div><div><br></div><div> # specify the interfaces to send outgoing queries to authoritative</div><div> # server from by ip-address. If none, the default (all) interface</div>
<div> # is used. Specify every interface on a outgoing-interface:' line.</div><div> </div><div> # outgoing-interface: 2001:470:c49a:10::0246</div><div> # outgoing-interface: 192.0.2.153</div>
<div> # outgoing-interface: 2001:DB8::5</div><div> # outgoing-interface: 2001:DB8::6</div><div><br></div><div> # number of ports to allocate per thread, determines the size of the</div><div> # port range that can be open simultaneously.</div>
<div> # outgoing-range: 4096</div><div><br></div><div> # permit unbound to use this port number or port range for</div><div> # making outgoing queries, using an outgoing interface.</div><div> # outgoing-port-permit: 32768</div>
<div><br></div><div> # deny unbound the use this of port number or port range for</div><div> # making outgoing queries, using an outgoing interface.</div><div> # Use this to make sure unbound does not grab a UDP port that some</div>
<div> # other server on this computer needs. The default is to avoid</div><div> # IANA-assigned port numbers.</div><div> # outgoing-port-avoid: "3200-3208"</div><div><br></div><div> # number of outgoing simultaneous tcp buffers to hold per thread.</div>
<div> # outgoing-num-tcp: 10</div><div><br></div><div> # number of incoming simultaneous tcp buffers to hold per thread.</div><div> # incoming-num-tcp: 10</div><div><br></div><div> # buffer size for UDP port 53 incoming (SO_RCVBUF socket option).</div>
<div> # 0 is system default. Use 4m to catch query spikes for busy servers.</div><div> # so-rcvbuf: 0</div><div><br></div><div> # buffer size for UDP port 53 outgoing (SO_SNDBUF socket option).</div>
<div> # 0 is system default. Use 4m to handle spikes on very busy servers.</div><div> # so-sndbuf: 0</div><div><br></div><div> # EDNS reassembly buffer to advertise to UDP peers (the actual buffer</div>
<div> # is set with msg-buffer-size). 1480 can solve fragmentation (timeouts).</div><div> # edns-buffer-size: 4096</div><div><br></div><div> # buffer size for handling DNS data. No messages larger than this</div>
<div> # size can be sent or received, by UDP or TCP. In bytes.</div><div> # msg-buffer-size: 65552</div><div><br></div><div> # the amount of memory to use for the message cache.</div><div> # plain value in bytes or you can append k, m or G. default is "4Mb".</div>
<div> # msg-cache-size: 4m</div><div><br></div><div> # the number of slabs to use for the message cache.</div><div> # the number of slabs must be a power of 2.</div><div> # more slabs reduce lock contention, but fragment memory usage.</div>
<div> # msg-cache-slabs: 4</div><div><br></div><div> # the number of queries that a thread gets to service.</div><div> # num-queries-per-thread: 1024</div><div><br></div><div> # if very busy, 50% queries run to completion, 50% get timeout in msec</div>
<div> # jostle-timeout: 200</div><div><br></div><div> # the amount of memory to use for the RRset cache.</div><div> # plain value in bytes or you can append k, m or G. default is "4Mb".</div>
<div> # rrset-cache-size: 4m</div><div><br></div><div> # the number of slabs to use for the RRset cache.</div><div> # the number of slabs must be a power of 2.</div><div> # more slabs reduce lock contention, but fragment memory usage.</div>
<div> # rrset-cache-slabs: 4</div><div><br></div><div> # the time to live (TTL) value lower bound, in seconds. Default 0.</div><div> # If more than an hour could easily give trouble due to stale data.</div>
<div> # cache-min-ttl: 0</div><div><br></div><div> # the time to live (TTL) value cap for RRsets and messages in the</div><div> # cache. Items are not cached for longer. In seconds.</div><div> # cache-max-ttl: 86400</div>
<div><br></div><div> # the time to live (TTL) value for cached roundtrip times, lameness</div><div> # and EDNS version information for hosts. In seconds.</div><div> # infra-host-ttl: 900</div><div><br>
</div><div> # the number of slabs to use for the Infrastructure cache.</div><div> # the number of slabs must be a power of 2.</div><div> # more slabs reduce lock contention, but fragment memory usage.</div>
<div> # infra-cache-slabs: 4</div><div><br></div><div> # the maximum number of hosts that are cached (roundtrip, EDNS, lame).</div><div> # infra-cache-numhosts: 10000</div><div><br></div><div> # Enable IPv4, "yes" or "no".</div>
<div> # do-ip4: yes</div><div><br></div><div> # Enable IPv6, "yes" or "no".</div><div> do-ip6: yes</div><div><br></div><div> # Enable UDP, "yes" or "no".</div>
<div> # NOTE: if setting up an unbound on tls443 for public use, you might want to</div><div> # disable UDP to avoid being used in DNS amplification attacks.</div><div> # do-udp: yes</div><div><br></div>
<div> # Enable TCP, "yes" or "no".</div><div> # do-tcp: yes</div><div><br></div><div> # upstream connections use TCP only (and no UDP), "yes" or "no"</div><div>
# useful for tunneling scenarios, default no.</div><div> # tcp-upstream: no</div><div><br></div><div> # Detach from the terminal, run in background, "yes" or "no".</div><div> # do-daemonize: yes</div>
<div><br></div><div> # control which clients are allowed to make (recursive) queries</div><div> # to this server. Specify classless netblocks with /size and action.</div><div> # By default everything is refused, except for localhost.</div>
<div> # Choose deny (drop message), refuse (polite error reply),</div><div> # allow (recursive ok), allow_snoop (recursive and nonrecursive ok)</div><div><br></div><div><span class="" style="white-space:pre"> </span>****TRUNCATED*****</div>
<div><br></div><div> # if given, a chroot(2) is done to the given directory.</div><div> # i.e. you can chroot to the working directory, for example,</div><div> # for extra security, but make sure all files are in that directory.</div>
<div> #</div><div> # If chroot is enabled, you should pass the configfile (from the</div><div> # commandline) as a full path from the original root. After the</div><div> # chroot has been performed the now defunct portion of the config</div>
<div> # file path is removed to be able to reread the config after a reload.</div><div> #</div><div> # All other file paths (working dir, logfile, roothints, and</div><div> # key files) can be specified in several ways:</div>
<div> # o as an absolute path relative to the new root.</div><div> # o as a relative path to the working directory.</div><div> # o as an absolute path relative to the original root.</div>
<div> # In the last case the path is adjusted to remove the unused portion.</div><div> #</div><div> # The pid file can be absolute and outside of the chroot, it is</div><div> # written just prior to performing the chroot and dropping permissions.</div>
<div> #</div><div> # Additionally, unbound may need to access /dev/random (for entropy).</div><div> # How to do this is specific to your OS.</div><div> #</div><div> # If you give "" no chroot is performed. The path must not end in a /.</div>
<div> # chroot: "/var/lib/unbound"</div><div> chroot: ""</div><div><br></div><div> # if given, user privileges are dropped (after binding port),</div><div> # and the given username is assumed. Default is user "unbound".</div>
<div> # If you give "" no privileges are dropped.</div><div> username: "unbound"</div><div><br></div><div> # the working directory. The relative files in this config are</div><div>
# relative to this directory. If you give "" the working directory</div><div> # is not changed.</div><div> directory: "/etc/unbound"</div><div><br></div><div> # the log file, "" means log to stderr.</div>
<div> # Use of this option sets use-syslog to "no".</div><div> </div><div><span class="" style="white-space:pre"> </span> logfile: "/etc/unbound/unboundLog.txt"</div><div><br></div><div>
# Log to syslog(3) if yes. The log facility LOG_DAEMON is used to</div><div> # log to, with identity "unbound". If yes, it overrides the logfile.</div><div> # use-syslog: yes</div><div><br>
</div><div> # print UTC timestamp in ascii to logfile, default is epoch in seconds.</div><div> log-time-ascii: yes</div><div> </div><div> log-queries: yes</div><div><br></div><div> # the pid file. Can be an absolute path outside of chroot/work dir.</div>
<div> pidfile: "/var/run/unbound/unbound.pid"</div><div><br></div><div> # file to read root hints from.</div><div> # get one from <a href="ftp://FTP.INTERNIC.NET/domain/named.cache">ftp://FTP.INTERNIC.NET/domain/named.cache</a></div>
<div> root-hints: "/etc/unbound/named.cache"</div><div><br></div><div> # enable to not answer id.server and hostname.bind queries.</div><div> # hide-identity: no</div><div><br></div><div> # enable to not answer version.server and version.bind queries.</div>
<div> # hide-version: no</div><div><br></div><div> # the identity to report. Leave "" or default to return hostname.</div><div> # identity: ""</div><div><br></div><div> # the version to report. Leave "" or default to return package version.</div>
<div> # version: ""</div><div><br></div><div> # the target fetch policy.</div><div> # series of integers describing the policy per dependency depth.</div><div> # The number of values in the list determines the maximum dependency</div>
<div> # depth the recursor will pursue before giving up. Each integer means:</div><div> # -1 : fetch all targets opportunistically,</div><div> # 0: fetch on demand,</div><div> # positive value: fetch that many targets opportunistically.</div>
<div> # Enclose the list of numbers between quotes ("").</div><div> # target-fetch-policy: "3 2 1 0 0"</div><div><br></div><div> # Harden against very small EDNS buffer sizes.</div>
<div> # harden-short-bufsize: no</div><div><br></div><div> # Harden against unseemly large queries.</div><div> # harden-large-queries: no</div><div><br></div><div> # Harden against out of zone rrsets, to avoid spoofing attempts.</div>
<div> harden-glue: yes</div><div><br></div><div> # Harden against receiving dnssec-stripped data. If you turn it</div><div> # off, failing to validate dnskey data for a trustanchor will</div><div> # trigger insecure mode for that zone (like without a trustanchor).</div>
<div> # Default on, which insists on dnssec data for trust-anchored zones.</div><div> harden-dnssec-stripped: yes</div><div><br></div><div> # Harden against queries that fall under dnssec-signed nxdomain names.</div>
<div> harden-below-nxdomain: yes</div><div><br></div><div> # Harden the referral path by performing additional queries for</div><div> # infrastructure data. Validates the replies (if possible).</div>
<div> # Default off, because the lookups burden the server. Experimental</div><div> # implementation of draft-wijngaards-dnsext-resolver-side-mitigation.</div><div> harden-referral-path: yes</div><div>
<br></div><div> # Use 0x20-encoded random bits in the query to foil spoof attempts.</div><div> # This feature is an experimental implementation of draft dns-0x20.</div><div> # (this now fails on all GoDaddy customer domains, so disabled)</div>
<div> use-caps-for-id: no</div><div><br></div><div> # Enforce privacy of these addresses. Strips them away from answers.</div><div> # It may cause DNSSEC validation to additionally mark it as bogus.</div>
<div> # Protects against 'DNS Rebinding' (uses browser as network proxy).</div><div> # Only 'private-domain' and 'local-data' names are allowed to have</div><div> # these private addresses. No default.</div>
<div> # private-address: <a href="http://10.0.0.0/8">10.0.0.0/8</a></div><div> # private-address: <a href="http://172.16.0.0/12">172.16.0.0/12</a></div><div> # private-address: <a href="http://192.168.0.0/16">192.168.0.0/16</a></div>
<div> # private-address: <a href="http://192.254.0.0/16">192.254.0.0/16</a></div><div> # private-address: fd00::/8</div><div> # private-address: fe80::/10</div><div><br></div><div> # Allow the domain (and its subdomains) to contain private addresses.</div>
<div> # local-data statements are allowed to contain private addresses too.</div><div> # private-domain: "<a href="http://example.com">example.com</a>"</div><div><br></div><div> # If nonzero, unwanted replies are not only reported in statistics,</div>
<div> # but also a running total is kept per thread. If it reaches the</div><div> # threshold, a warning is printed and a defensive action is taken,</div><div> # the cache is cleared to flush potential poison out of it.</div>
<div> # A suggested value is 10000000, the default is 0 (turned off).</div><div> unwanted-reply-threshold: 10000000</div><div><br></div><div> # Do not query the following addresses. No DNS queries are sent there.</div>
<div> # List one address per entry. List classless netblocks with /size,</div><div> # do-not-query-address: <a href="http://127.0.0.1/8">127.0.0.1/8</a></div><div> # do-not-query-address: ::1</div><div>
<br></div><div> # if yes, the above default do-not-query-address entries are present.</div><div> # if no, localhost can be queried (for testing and debugging).</div><div> # do-not-query-localhost: yes</div>
<div><br></div><div> # if yes, perform prefetching of almost expired message cache entries.</div><div> prefetch: yes</div><div><br></div><div> # if yes, perform key lookups adjacent to normal lookups.</div>
<div> prefetch-key: yes</div><div><br></div><div> # if yes, Unbound rotates RRSet order in response.</div><div> # rrset-roundrobin: no</div><div><br></div><div> # if yes, Unbound doesn't insert authority/additional sections</div>
<div> # into response messages when those sections are not required.</div><div> # minimal-responses: no</div><div><br></div><div> # module configuration of the server. A string with identifiers</div><div>
# separated by spaces. "iterator" or "validator iterator"</div><div> # module-config: "validator iterator"</div><div><br></div><div> # File with DLV trusted keys. Same format as trust-anchor-file.</div>
<div> # There can be only one DLV configured, it is trusted from root down.</div><div> # Downloaded from <a href="https://secure.isc.org/ops/dlv/dlv.isc.org.key">https://secure.isc.org/ops/dlv/dlv.isc.org.key</a></div>
<div> dlv-anchor-file: "/etc/unbound/dlv.isc.org.key"</div><div><br></div><div> # File with trusted keys for validation. Specify more than one file</div><div> # with several entries, one file per entry.</div>
<div> # Zone file format, with DS and DNSKEY entries.</div><div> # trust-anchor-file: ""</div><div><br></div><div> # File with trusted keys, kept uptodate using RFC5011 probes,</div><div> # initial file like trust-anchor-file, then it stores metadata.</div>
<div> # Use several entries, one per domain name, to track multiple zones.</div><div> # auto-trust-anchor-file: ""</div><div><br></div><div> # Trusted key for validation. DS or DNSKEY. specify the RR on a</div>
<div> # single line, surrounded by "". TTL is ignored. class is IN default.</div><div> # (These examples are from August 2007 and may not be valid anymore).</div><div> # trust-anchor: "<a href="http://nlnetlabs.nl">nlnetlabs.nl</a>. DNSKEY 257 3 5 AQPzzTWMz8qSWIQlfRnPckx2BiVmkVN6LPupO3mbz7FhLSnm26n6iG9N Lby97Ji453aWZY3M5/xJBSOS2vWtco2t8C0+xeO1bc/d6ZTy32DHchpW 6rDH1vp86Ll+ha0tmwyy9QP7y2bVw5zSbFCrefk8qCUBgfHm9bHzMG1U BYtEIQ=="</div>
<div> # trust-anchor: "<a href="http://jelte.nlnetlabs.nl">jelte.nlnetlabs.nl</a>. DS 42860 5 1 14D739EB566D2B1A5E216A0BA4D17FA9B038BE4A"</div><div><br></div><div> # File with trusted keys for validation. Specify more than one file</div>
<div> # with several entries, one file per entry. Like trust-anchor-file</div><div> # but has a different file format. Format is BIND-9 style format,</div><div> # the trusted-keys { name flag proto algo "key"; }; clauses are read.</div>
<div> # trusted-keys-file: ""</div><div> #</div><div> # trusted-keys-file: /etc/unbound/rootkey.bind</div><div> trusted-keys-file: /etc/unbound/keys.d/*.key</div><div> auto-trust-anchor-file: "/etc/unbound/root.anchor"</div>
<div><br></div><div> # Ignore chain of trust. Domain is treated as insecure.</div><div> # domain-insecure: "<a href="http://example.com">example.com</a>"</div><div><br></div><div> # Override the date for validation with a specific fixed date.</div>
<div> # Do not set this unless you are debugging signature inception</div><div> # and expiration. "" or "0" turns the feature off.</div><div> # val-override-date: ""</div>
<div><br></div><div> # The time to live for bogus data, rrsets and messages. This avoids</div><div> # some of the revalidation, until the time interval expires. in secs.</div><div> # val-bogus-ttl: 60</div>
<div><br></div><div> # The signature inception and expiration dates are allowed to be off</div><div> # by 10% of the lifetime of the signature from our local clock.</div><div> # This leeway is capped with a minimum and a maximum. In seconds.</div>
<div> # val-sig-skew-min: 3600</div><div> # val-sig-skew-max: 86400</div><div><br></div><div> # Should additional section of secure message also be kept clean of</div><div> # unsecure data. Useful to shield the users of this validator from</div>
<div> # potential bogus data in the additional section. All unsigned data</div><div> # in the additional section is removed from secure messages.</div><div> val-clean-additional: yes</div><div><br></div>
<div> # Turn permissive mode on to permit bogus messages. Thus, messages</div><div> # for which security checks failed will be returned to clients,</div><div> # instead of SERVFAIL. It still performs the security checks, which</div>
<div> # result in interesting log files and possibly the AD bit in</div><div> # replies if the message is found secure. The default is off.</div><div> # NOTE: TURNING THIS ON DISABLES ALL DNSSEC SECURITY</div>
<div> val-permissive-mode: no</div><div><br></div><div> # Have the validator log failed validations for your diagnosis.</div><div> # 0: off. 1: A line per failed user query. 2: With reason and bad IP.</div>
<div> val-log-level: 1</div><div><br></div><div> # It is possible to configure NSEC3 maximum iteration counts per</div><div> # keysize. Keep this table very short, as linear search is done.</div><div>
# A message with an NSEC3 with larger count is marked insecure.</div><div> # List in ascending order the keysize and count values.</div><div> # val-nsec3-keysize-iterations: "1024 150 2048 500 4096 2500"</div>
<div><br></div><div> # instruct the auto-trust-anchor-file probing to add anchors after ttl.</div><div> # add-holddown: 2592000 # 30 days</div><div><br></div><div> # instruct the auto-trust-anchor-file probing to del anchors after ttl.</div>
<div> # del-holddown: 2592000 # 30 days</div><div><br></div><div> # auto-trust-anchor-file probing removes missing anchors after ttl.</div><div> # If the value 0 is given, missing anchors are not removed.</div>
<div> # keep-missing: 31622400 # 366 days</div><div><br></div><div> # the amount of memory to use for the key cache.</div><div> # plain value in bytes or you can append k, m or G. default is "4Mb".</div>
<div> # key-cache-size: 4m</div><div><br></div><div> # the number of slabs to use for the key cache.</div><div> # the number of slabs must be a power of 2.</div><div> # more slabs reduce lock contention, but fragment memory usage.</div>
<div> # key-cache-slabs: 4</div><div><br></div><div> # the amount of memory to use for the negative cache (used for DLV).</div><div> # plain value in bytes or you can append k, m or G. default is "1Mb".</div>
<div> # neg-cache-size: 1m</div><div><br></div><div> # a number of locally served zones can be configured.</div><div> # local-zone: <zone> <type></div><div> # local-data: "<resource record string>"</div>
<div> # o deny serves local data (if any), else, drops queries.</div><div> # o refuse serves local data (if any), else, replies with error.</div><div> # o static serves local data, else, nxdomain or nodata answer.</div>
<div> # o transparent serves local data, but resolves normally for other names</div><div> # o redirect serves the zone data for any subdomain in the zone.</div><div> # o nodefault can be used to normally resolve AS112 zones.</div>
<div> # o typetransparent resolves normally for other types and other names</div><div> #</div><div> # defaults are localhost address, reverse for 127.0.0.1 and ::1</div><div> # and nxdomain for AS112 zones. If you configure one of these zones</div>
<div> # the default content is omitted, or you can omit it with 'nodefault'.</div><div> #</div><div> # If you configure local-data without specifying local-zone, by</div><div> # default a transparent local-zone is created for the data.</div>
<div> #</div><div> # You can add locally served data with</div><div> local-zone: "mankatonetworks.local." static</div><div> local-data: "mankatonetworks.local. IN A 192.168.10.246"</div>
<div> # local-data: 'mytext.local TXT "content of text record"'</div><div> #</div><div> # You can override certain queries with</div><div> # local-data: "<a href="http://adserver.example.com">adserver.example.com</a> A 127.0.0.1"</div>
<div> #</div><div> # You can redirect a domain to a fixed address with</div><div> # (this makes <a href="http://example.com">example.com</a>, <a href="http://www.example.com">www.example.com</a>, etc, all go to 192.0.2.3)</div>
<div> # local-zone: "<a href="http://example.com">example.com</a>" redirect</div><div> # local-data: "<a href="http://example.com">example.com</a> A 192.0.2.3"</div><div> #</div><div>
# Shorthand to make PTR records, "IPv4 name" or "IPv6 name".</div><div> # You can also add PTR records using local-data directly, but then</div><div> # you need to do the reverse notation yourself.</div>
<div> # local-data-ptr: "192.0.2.3 <a href="http://www.example.com">www.example.com</a>"</div><div><br></div><div> include: /etc/unbound/local.d/*.conf</div><div><br></div><div> # service clients over SSL (on the TCP sockets), with plain DNS inside</div>
<div> # the SSL stream. Give the certificate to use and private key.</div><div> # default is "" (disabled). requires restart to take effect.</div><div> # ssl-service-key: "/etc/unbound/unbound_server.key"</div>
<div> # ssl-service-pem: "/etc/unbound/unbound_server.pem"</div><div> # ssl-port: 443</div><div><br></div><div> # request upstream over SSL (with plain DNS inside the SSL stream).</div><div>
# Default is no. Can be turned on and off with unbound-control.</div><div> # ssl-upstream: no</div><div><br></div><div>## Python config section. To enable:</div><div>## o use --with-pythonmodule to configure before compiling.</div>
<div>## o list python in the module-config string (above) to enable.</div><div>## o and give a python-script to run.</div><div>#python:</div><div># # Script file to load</div><div># # python-script: "/etc/unbound/ubmodule-tst.py"</div>
<div><br></div><div><br></div><div># Remote control config section.</div><div>remote-control:</div><div> # Enable remote control with unbound-control(8) here.</div><div> # set up the keys and certificates with unbound-control-setup.</div>
<div> # Note: required for unbound-munin package</div><div> control-enable: yes</div><div><br></div><div> # what interfaces are listened to for remote control.</div><div> # give 0.0.0.0 and ::0 to listen to all interfaces.</div>
<div> # control-interface: 127.0.0.1</div><div> # control-interface: ::1</div><div><br></div><div> # port number for remote control operations.</div><div> # control-port: 953</div><div><br></div>
<div> # unbound server key file.</div><div> server-key-file: "/etc/unbound/unbound_server.key"</div><div><br></div><div> # unbound server certificate file.</div><div> server-cert-file: "/etc/unbound/unbound_server.pem"</div>
<div><br></div><div> # unbound-control key file.</div><div> control-key-file: "/etc/unbound/unbound_control.key"</div><div><br></div><div> # unbound-control certificate file.</div><div> control-cert-file: "/etc/unbound/unbound_control.pem"</div>
<div><br></div><div># Stub and Forward zones</div><div><br></div><div>include: /etc/unbound/conf.d/*.conf</div><div><br></div><div># Stub zones.</div><div># Create entries like below, to make all queries for '<a href="http://example.com">example.com</a>' and</div>
<div># '<a href="http://example.org">example.org</a>' go to the given list of nameservers. list zero or more</div><div># nameservers by hostname or by ipaddress. If you set stub-prime to yes,</div><div># the list is treated as priming hints (default is no).</div>
<div># stub-zone:</div><div># name: "<a href="http://example.com">example.com</a>"</div><div># stub-addr: 192.0.2.68</div><div># stub-prime: "no"</div><div># stub-zone:</div><div># name: "<a href="http://example.org">example.org</a>"</div>
<div># stub-host: <a href="http://ns.example.com">ns.example.com</a>.</div><div># You can now also dynamically create and delete stub-zone's using</div><div># unbound-control stub_add <a href="http://domain.com">domain.com</a> 1.2.3.4 5.6.7.8</div>
<div># unbound-control stub_remove <a href="http://domain.com">domain.com</a> 1.2.3.4 5.6.7.8</div><div><br></div><div># Forward zones</div><div># Create entries like below, to make all queries for '<a href="http://example.com">example.com</a>' and</div>
<div># '<a href="http://example.org">example.org</a>' go to the given list of servers. These servers have to handle</div><div># recursion to other nameservers. List zero or more nameservers by hostname</div><div># or by ipaddress. Use an entry with name "." to forward all queries.</div>
<div># If you enable forward-first, it attempts without the forward if it fails.</div><div># forward-zone:</div><div># name: "<a href="http://example.com">example.com</a>"</div><div># forward-addr: 192.168.100.200 #LOCAL CACHED DNS</div>
<div># forward-addr: 8.8.8.8 #Google Public DNS</div><div># forward-addr: 66.244.62.20 #OpenNIC Indiana, US</div><div># forward-first: no</div><div># forward-zone:</div><div># name: "<a href="http://example.org">example.org</a>"</div>
<div># forward-host: <a href="http://fwd.example.com">fwd.example.com</a></div><div>#</div><div># You can now also dynamically create and delete forward-zone's using</div><div># unbound-control forward_add <a href="http://domain.com">domain.com</a> 1.2.3.4 5.6.7.8</div>
<div># unbound-control forward_remove <a href="http://domain.com">domain.com</a> 1.2.3.4 5.6.7.8</div></div><div><br></div><div><br></div><div><br clear="all"><div><div dir="ltr"><br></div></div>
</div></div>