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