[Dnsmasq-discuss] override public records
richardvoigt at gmail.com
richardvoigt at gmail.com
Sun Jun 14 03:05:48 BST 2009
> Yap it works, when dnsmasq overrides from /etc/hosts, it should attrib
some
> TTL to the it, it stays with zero TTL.
> Just to avoid this:
> ---
> Peixe:~# host -v -t a mail.domain.pt
> Query about mail.domain.pt for record types A
> Trying mail.domain.pt ...
> Query done, 1 answer, authoritative status: no error
> mail.decimal.pt 0 IN A 192.168.1.222
> !!! mail.domain.pt A record has zero ttl
> Peixe:~#
> ---
And now you DO get pointed to the man page:
-T, --local-ttl=<time>
When replying with information* **from /etc/hosts* or the DHCP leases file
dnsmasq *by default sets the time-to-live field to zero*, meaning that the
requestor 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.
http://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20090613/d7929a57/attachment.htm
More information about the Dnsmasq-discuss
mailing list