On 7/9/2021 17:46, Geert Stappers via Dnsmasq-discuss wrote:
On Fri, Jul 09, 2021 at 02:35:29PM +0200, Petr Menšík wrote:
On 6/16/21 1:26 PM, Trey Sis wrote:
On 6/14/2021 1:43, Trey Sis wrote:
On 6/13/2021 22:01, Geert Stappers wrote:
warning: 1 line adds whitespace errors.
My bad! Fixed.
On Thu, Sep 02, 2021 at 10:32:01AM -0700, Michael wrote:
[snip earlier stuff]
> Hi Chris,
>
> I am sure there are some good guides out there for learning docker. I just
> learned by just picking a project that I wanted to try and set out to get it
> running. You could always run your primary
On Thu, Sep 02, 2021 at 10:44:48AM -0700, Michael wrote:
>
> However, if you are running DHCP and dnsmasq is updating/maintaining a list
> of host names of your local clients in the leases file, then only one of the
> dnsmasq instances is going to know about those. In this instance, I think
>
On 9/2/21 5:45 AM, Chris Green wrote:
I'm still ruminating on this problem! :-)
A number of people are using docker containers to manage this, one
live dnsmasq in a container is the default DNS/DHCP for the system and
another dnsmasq container is maintained to keep its files in sync with
the
On 9/2/21 6:58 AM, Kevin Tedder wrote:
Chris
You just need to update the /etc/resolv.conf file on each of your clients to
point them at both DNS's.
e.g
nameserver 192.168.1.2
nameserver 192.168.1.3
The client will now ask both DNS servers. It will get a response even if one
of them is
On 9/2/21 1:05 AM, Chris Green wrote:
On Wed, Sep 01, 2021 at 01:04:24PM -0700, Michael wrote:
Hi Chris,
This is a topic that has come up periodically over the years and I too have
watched with interest on how to best manage this.
I looked at using heartbeat and other failover service to
On 02/09/2021 15:30, Chris Green wrote:
> On Thu, Sep 02, 2021 at 02:58:44PM +0100, Kevin Tedder wrote:
>> Chris
>> You just need to update the /etc/resolv.conf file on each of your clients to
>> point them at both DNS's.
>>
>> e.g
>> nameserver 192.168.1.2
>> nameserver 192.168.1.3
>>
>> The
On Thu, Sep 02, 2021 at 02:58:44PM +0100, Kevin Tedder wrote:
> Chris
> You just need to update the /etc/resolv.conf file on each of your clients to
> point them at both DNS's.
>
> e.g
> nameserver 192.168.1.2
> nameserver 192.168.1.3
>
> The client will now ask both DNS servers. It will get a
Chris
You just need to update the /etc/resolv.conf file on each of your clients to
point them at both DNS's.
e.g
nameserver 192.168.1.2
nameserver 192.168.1.3
The client will now ask both DNS servers. It will get a response even if one
of them is off-line.
Your solution to move the SD card to
I'm still ruminating on this problem! :-)
A number of people are using docker containers to manage this, one
live dnsmasq in a container is the default DNS/DHCP for the system and
another dnsmasq container is maintained to keep its files in sync with
the running one.
So far so good.
What I
On alpine linux the installation contains:
https://pkgs.alpinelinux.org/contents?branch=edge=dnsmasq=x86=main
Eliezer
בתאריך יום ה׳, 2 בספט׳ 2021, 14:41, מאת Chris Green :
> Further to my recent question about providing some sort of backup if
> a system running dnsmasq fails, what files need
11 matches
Mail list logo
