Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: From the Dnsmasq-discuss: I just noticed that 2.64 contains a nasty regression: it doesn't actually cache DNS queries at all. An oversight in the max-cache-ttl patch means that the cached TTL was always set to zero. I've pushed version 2.65 which fixes this and the other two bugs found since the 2.64 but no other changes. version 2.65 Fix regression which broke forwarding of queries sent via TCP which are not for A and AAAA and which were directed to non-default servers. Thanks to Niax for the bug report. Fix failure to build with DHCP support excluded. Thanks to Gustavo Zacarias for the patch. Fix nasty regression in 2.64 which completely broke cacheing. Sorry guys.
dnsmasq-2.65-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2012-18542/dnsmasq-2.65-1.fc17
dnsmasq-2.65-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/dnsmasq-2.65-1.fc18
Thank you.
No problem. Fixed bugs are really bad ones, so the sooner it gets into Fedora the better.
Package dnsmasq-2.65-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dnsmasq-2.65-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20463/dnsmasq-2.65-1.fc18 then log in and leave karma (feedback).
dnsmasq-2.65-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
dnsmasq-2.65-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.