While we were not seeing any issues with the dnsmasq from 2016-01-08, I have switched our testing system to the 2016-01-14 version. If no issues show up, then we will generally deploy it and report back. We are using 8.8.8.8, and 8.8.4.4 for external DNS.

Best regards, Fred

-----Original Message----- From: Matthias Fischer [mailto:matthias.fischer@ipfire.org] Sent: Thursday, January 14, 2016 12:42 PM To: R. W. Rodolico Cc: IPFire: Development-List Subject: Re: dnsmasq 2.75, including latest patches from 2016-01-08

Hi,

(I added the development@lists.ipfire.org, perhaps others like to participate)

On 14.01.2016 07:47, R. W. Rodolico wrote:

FYI, almost a week and no issues.

Sounds good...

I also changed my upstream DNS servers to the ones recommended. Do you

think I should change them back for a real test?

Simple question - simple answer: yes, *I* would do that.

Best, Matthias

P.S.: BTW, next version including new patches (045-048) is online:

Download: http://people.ipfire.org/~mfischer/dnsmasq_275_2016_01_14 MD5: a47e090fe132c155f2d041ab4272c52b

For new patches included, see: http://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=0e5e221f9...

This is the compiled binary, nothing more is needed.

- Copy to '/usr/sbin' - Stop 'dnsmasq' (/etc/init.d/dnsmasq stop) - Rename (don't forget backing up the *old* version!) - Start 'dnsmasq' (/etc/init.d/dnsmasq start).