<br>> Yap it works, when dnsmasq overrides from /etc/hosts, it should attrib some<br>> TTL to the it, it stays with zero TTL.<br>> Just to avoid this:<br>> ---<br>> Peixe:~# host -v -t a <a href="http://mail.domain.pt">mail.domain.pt</a><br>
> Query about <a href="http://mail.domain.pt">mail.domain.pt</a> for record types A<br>> Trying <a href="http://mail.domain.pt">mail.domain.pt</a> ...<br>> Query done, 1 answer, authoritative status: no error<br>
> <a href="http://mail.decimal.pt">mail.decimal.pt</a> 0 IN A 192.168.1.222<br>> !!! <a href="http://mail.domain.pt">mail.domain.pt</a> A record has zero ttl<br>> Peixe:~#<br>> ---<br>
<br><br>And now you DO get pointed to the man page:<br><br>-T, --local-ttl=<time><br>When replying with information<i> </i><b><i>from /etc/hosts</i></b> or the DHCP leases file dnsmasq <b><i>by default sets the time-to-live field to zero</i></b>, meaning that the requestor should not itself cache the information. This is the correct thing to do in almost all situations. <b><i>This option allows a time-to-live (in seconds) to be given for these replies</i></b>. This will reduce the load on the server at the expense of clients using stale data under some circumstances.<br>
<br><div><a href="http://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html">http://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html</a></div><div><br><br></div>