From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: dnsmasq 2.75, including latest patches from 2016-01-08
Date: Thu, 14 Jan 2016 12:42:29 -0600 [thread overview]
Message-ID: <5697EC15.8030501@dailydata.net> (raw)
In-Reply-To: <5697DE05.1020402@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
done and done. However, I saved the other DNS servers recommended and
will change them back later. I like them more. But we'll test with
209.244.0.3 and 8.8.4.4
Rod
On 01/14/2016 11:42 AM, Matthias Fischer wrote:
> Hi,
>
> (I added the development(a)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=0e5e221f940471c173a780be402e2812adf380f3
>
>
> 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).
--
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net
next prev parent reply other threads:[~2016-01-14 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5697447D.4060701@dailydata.net>
2016-01-14 17:42 ` Matthias Fischer
2016-01-14 18:42 ` R. W. Rodolico [this message]
2016-01-14 22:50 ` Kienker, Fred
2016-01-08 21:06 Matthias Fischer
2016-01-09 18:24 ` Kienker, Fred
2016-01-09 19:35 ` Matthias Fischer
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=5697EC15.8030501@dailydata.net \
--to=rodo@dailydata.net \
--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