From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: dnsmasq 2.75, including latest patches from 2015-12-24
Date: Mon, 04 Jan 2016 23:12:59 +0100 [thread overview]
Message-ID: <568AEE6B.20109@ipfire.org> (raw)
In-Reply-To: <568AD259.3090904@dailydata.net>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
Hi,
(I just "replied", list is now included.)
Just for testing I think it would be worth a try with the suggested
nameservers.
Best,
Matthias
On 04.01.2016 21:13, R. W. Rodolico wrote:
> Did you intend to do this off list?
> Anyway, yes, I changed my nameservers. Previously, I used
> 209.244.0.3
> 8.8.4.4
>
> Which are level3.net and google, respectively. I didn't realize I was
> using them :(
>
> Rod
>
> On 01/04/2016 11:24 AM, Matthias Fischer wrote:
>> Hi,
>>
>> On 03.01.2016 11:45, R. W. Rodolico wrote:
>>> I just had it break on me. It lasted longer than the last time, but
>>> dnsmasq just broke on me.
>>
>> [****!]
>>
>>
>>> Basically, the same error message. This is dnsmasq_275_2015_12_24 which
>>> I got from Matthias, I think.
>>
>> Yep. The exact same version is running here without any problems...
>>
>> I couldn't reproduce these crashes. Not even once. Right now I'm testing
>> the next patches (sad to say, they won't compile).
>>
>> Would you mind to test this version with different nameservers from
>> germany? I'm using the DNS Servers from https://dns.watch/index and
>> never had any problems since then...
>>
>> Best,
>> Matthias
>>
>
next parent reply other threads:[~2016-01-04 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <568AD259.3090904@dailydata.net>
2016-01-04 22:12 ` Matthias Fischer [this message]
2015-12-24 13:57 Matthias Fischer
2015-12-25 1:49 ` R. W. Rodolico
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=568AEE6B.20109@ipfire.org \
--to=matthias.fischer@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