From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: 104 and dnsmasq
Date: Tue, 13 Sep 2016 15:30:14 +0100 [thread overview]
Message-ID: <1473777014.2757.145.camel@ipfire.org> (raw)
In-Reply-To: <57D7A9E5.4050606@dailydata.net>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
Hi,
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 :)
Best,
-Michael
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-09-13 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 7:25 R. W. Rodolico
2016-09-13 14:30 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1473777014.2757.145.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox