@@ -60,7 +60,7 @@ in the same way as for DHCP-derived names. Note that this does not
...
@@ -60,7 +60,7 @@ in the same way as for DHCP-derived names. Note that this does not
apply to domain names in cnames, PTR records, TXT records etc.
apply to domain names in cnames, PTR records, TXT records etc.
.TP
.TP
.B \-T, --local-ttl=<time>
.B \-T, --local-ttl=<time>
When replying with information from /etc/hosts or the DHCP leases
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
file dnsmasq by default sets the time-to-live field to zero, meaning
that the requester should not itself cache the information. This is
that the requester should not itself cache the information. This is
the correct thing to do in almost all situations. This option allows a
the correct thing to do in almost all situations. This option allows a
...
@@ -68,6 +68,9 @@ time-to-live (in seconds) to be given for these replies. This will
...
@@ -68,6 +68,9 @@ 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
reduce the load on the server at the expense of clients using stale
data under some circumstances.
data under some circumstances.
.TP
.TP
.B --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.
.TP
.B --neg-ttl=<time>
.B --neg-ttl=<time>
Negative replies from upstream servers normally contain time-to-live
Negative replies from upstream servers normally contain time-to-live
information in SOA records which dnsmasq uses for caching. If the
information in SOA records which dnsmasq uses for caching. If the