| Denys Vlasenko | df65dc8 | 2018-03-30 20:49:16 +0200 | [diff] [blame] | 1 | keep-in-foreground |
| 2 | |
| 3 | # "-" is stderr: |
| 4 | log-facility=- |
| 5 | |
| 6 | # May also try log-queries=extra |
| 7 | log-queries |
| 8 | |
| 9 | # No param = pidfile disabled: |
| 10 | pid-file |
| 11 | |
| 12 | interface=lo |
| 13 | listen-address=127.0.0.1 |
| 14 | bind-interfaces |
| 15 | |
| 16 | cache-size=999 |
| 17 | |
| 18 | servers-file=/etc/dnsmasq_servers.conf |
| 19 | |
| 20 | # Don’t read /etc/resolv.conf and /etc/hosts: |
| 21 | no-resolv |
| 22 | #no-hosts |
| 23 | |
| 24 | # All reverse lookups for private IP ranges (ie 192.168.x.x, etc) |
| 25 | # which are not found in /etc/hosts or the DHCP leases file are |
| 26 | # answered with "no such domain" rather than being forwarded |
| 27 | # upstream. The set of prefixes affected is the list given in |
| 28 | # RFC6303. |
| 29 | #bogus-priv |
| 30 | |
| 31 | #−T, --local-ttl=<time> |
| 32 | # When replying with information from /etc/hosts or configuration |
| 33 | # or the DHCP leases file dnsmasq by default sets the time-to-live |
| 34 | # field to zero, meaning that the requester should not itself |
| 35 | # cache the information. This is the correct thing to do in almost |
| 36 | # all situations. This option allows a time-to-live (in seconds) |
| 37 | # to be given for these replies. This will reduce the load on the |
| 38 | # server at the expense of clients using stale data under some |
| 39 | # circumstances. |
| 40 | local-ttl=67 |
| 41 | |
| 42 | #--dhcp-ttl=<time> |
| 43 | # As for --local-ttl, but affects only replies with information |
| 44 | # from DHCP leases. If both are given, --dhcp-ttl applies for DHCP |
| 45 | # information, and --local-ttl for others. Setting this to zero |
| 46 | # eliminates the effect of --local-ttl for DHCP. |
| 47 | # |
| 48 | #--neg-ttl=<time> |
| 49 | # Negative replies from upstream servers normally contain time-to- |
| 50 | # live information in SOA records which dnsmasq uses for caching. |
| 51 | # If the replies from upstream servers omit this information, dns- |
| 52 | # masq does not cache the reply. This option gives a default value |
| 53 | # for time-to-live (in seconds) which dnsmasq uses to cache nega- |
| 54 | # tive replies even in the absence of an SOA record. |
| 55 | neg-ttl=67 |
| 56 | |
| 57 | #--max-ttl=<time> |
| 58 | # Set a maximum TTL value that will be handed out to clients. The |
| 59 | # specified maximum TTL will be given to clients instead of the |
| 60 | # true TTL value if it is lower. The true TTL value is however |
| 61 | # kept in the cache to avoid flooding the upstream DNS servers. |
| 62 | # |
| 63 | #--max-cache-ttl=<time> |
| 64 | # Set a maximum TTL value for entries in the cache. |
| 65 | # |
| 66 | #--min-cache-ttl=<time> |
| 67 | # Extend short TTL values to the time given when caching them. |
| 68 | # Note that artificially extending TTL values is in general a bad |
| 69 | # idea, do not do it unless you have a good reason, and understand |
| 70 | # what you are doing. Dnsmasq limits the value of this option to |
| 71 | # one hour, unless recompiled. |
| 72 | min-cache-ttl=67 |
| 73 | |
| 74 | #--auth-ttl=<time> |
| 75 | # Set the TTL value returned in answers from the authoritative |
| 76 | # server. |