104 and dnsmasq

Michael Tremer michael.tremer at ipfire.org
Tue Sep 13 16:30:14 CEST 2016


yes, I have been experiencing this issues with dnsmasq, too.

It is working most of the time, but sometimes getting a bit unreliable. After
all the trouble with DNSSEC, crashes and now this, we have decided to replace it
by unbound: https://www.unbound.net/

This has been recently merged into the next branch and should be released with
Core Update 105. It is in the nightly builds if you want to test. Please do :)


On Tue, 2016-09-13 at 02:25 -0500, R. W. Rodolico wrote:
> First, this may just be an issue with my firewall. I've used it for
> testing for a long time; I need to just back it up and rebuild from scratch.
> But, since upgrading to 104, I've had two instances when dnsmasq just
> stopped. I was part of the testing when this happened a while ago, so I
> recognize the situation and fix it pretty fast (log into firewall,
> /etc/init.d/dnsmasq start).
> As I said, this may not really be an issue with anything other than an
> firewall that has been used for testing for a while. But I thought I'd
> mention it and see if anyone else has a similar problem.
> Next time it happens, I'll get a log dump. Forgot to do it before.
> Rod
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ipfire.org/pipermail/development/attachments/20160913/b3f22a50/attachment.sig>

More information about the Development mailing list