Package: dnsmasq Version: 1.23 Severity: important Hi,
the version of dnsmasq I use on my router is 1.23. I think positive results for anything *.dyndns.org, *.no-ip.com and other such dynDNS service providers are kept for too long. IMHO they should not be cached at all or maybe only for a minute or so. In the last couple of days I frequently had to restart dnsmasq to reach a computer accessible via dyndns.org because even one hour after the IP update dnsmasq still returned the old IP. DNS servers at dyndns.org had long since been updated and after the restart of dnsmasq, which I assume flushes the cache, everything worked just fine. Maybe it would be a good idea to have this configurable just like bogus-nxdomain so the user can add from the myriad of providers out there after the release of dnsmasq. I do not know too much about DNS but isn't there a setting for TTL? Does dnsmasq honor that and is it really dyndns.org who is the culprit for having set that value too high? Best regards Rolf Leggewie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
