On Fri, Sep 03, 2021 at 02:32:06PM -0700, Michael wrote:
>
> > So the normal 'everything working' situation will be system A (say on
> > 192.168.1.2) is a DNS and DHCP server. System B (say on 192.168.1.3)
> > provides only DNS. System A's DHCP server will give out both
> > 192.168.1.2 and 192.1
On Fri, Sep 03, 2021 at 02:32:06PM -0700, Michael wrote:
> On 9/3/21 1:23 PM, Chris Green wrote:
> > If I have set dhcp-optsdir in /etc/dnsmasq.conf and add a file to the
> > directory it points to I assume any extra configuration in the added
> > file will 'just happen' without any restart or sign
On 04/09/2021 09:15, Chris Green wrote:
>> This works if your DHCP server only hands out static addressing so the host
>> names are all listed in the /etc/hosts or addn hosts location on both
>> machines. If the DHCP server is handing out addresses from a pool, then
>> only the DHCP dnsmasq inst
On Sat, Sep 04, 2021 at 11:29:32AM +0100, Ed W wrote:
> On 04/09/2021 09:15, Chris Green wrote:
>
> >> This works if your DHCP server only hands out static addressing so the host
> >> names are all listed in the /etc/hosts or addn hosts location on both
> >> machines. If the DHCP server is handi
On 03.09.21 17:13, Chris Green wrote:
I know there probably isn't a "right" way to do this but, while I've
been trying to sort out how to make my dns/dhcp more resilient, I have
looked at my existing dnsmasq running on a Pi and it looks a bit odd
to me.
It's a pretty standard, off the shelf Rasp
On 04/09/2021 12:07, Chris Green wrote:
> On Sat, Sep 04, 2021 at 11:29:32AM +0100, Ed W wrote:
>> On 04/09/2021 09:15, Chris Green wrote:
>>
>>> I was aiming to synchronise the lease file in /var between the two
>>> systems as well as the configuration.
>>>
>> Did you see my suggestion to cross po
When [re]starting dnsmasq I see the following in syslog:-
Sep 4 17:01:08 dns systemd[1]: dnsmasq.service: Succeeded.
Sep 4 17:01:08 dns systemd[1]: Stopped dnsmasq - A lightweight DHCP and
caching DNS server.
Sep 4 17:01:08 dns systemd[1]: Starting dnsmasq - A lightweight DHCP and
On Sat, Sep 04, 2021 at 04:33:10PM +0200, Matus UHLAR - fantomas via
Dnsmasq-discuss wrote:
> On 03.09.21 17:13, Chris Green wrote:
> > I know there probably isn't a "right" way to do this but, while I've
> > been trying to sort out how to make my dns/dhcp more resilient, I have
> > looked at my e
On 9/4/2021 6:14 PM, Chris Green wrote:
When [re]starting dnsmasq I see the following in syslog:-
Sep 4 17:01:08 dns systemd[1]: dnsmasq.service: Succeeded.
Sep 4 17:01:08 dns systemd[1]: Stopped dnsmasq - A lightweight DHCP and
caching DNS server.
Sep 4 17:01:08 dns systemd[1
Hey Masanari,
On Fri, 2021-09-03 at 19:26 +0900, Masanari Iida wrote:
> dnsmasq-2.85 (Fedora 33, x86_64)
> multiple upstream DNS servers in config file.
> No --strict-order, No --all-server setting .
>
> Symptom
> Explanation about --all-servers in dnsmasq(8) man page could
> be different from a
On Sat, Sep 04, 2021 at 03:34:59PM +0100, Ed W wrote:
> On 04/09/2021 12:07, Chris Green wrote:
> > On Sat, Sep 04, 2021 at 11:29:32AM +0100, Ed W wrote:
> >> On 04/09/2021 09:15, Chris Green wrote:
> >>
> >>> I was aiming to synchronise the lease file in /var between the two
> >>> systems as well
On Sat, Sep 04, 2021 at 07:09:30PM +0200, john doe wrote:
> On 9/4/2021 6:14 PM, Chris Green wrote:
> > When [re]starting dnsmasq I see the following in syslog:-
> >
> > Sep 4 17:01:08 dns systemd[1]: dnsmasq.service: Succeeded.
> > Sep 4 17:01:08 dns systemd[1]: Stopped dnsmasq - A lightwei
On Sat, Sep 04, 2021 at 08:16:44PM +0100, Chris Green wrote:
> On Sat, Sep 04, 2021 at 07:09:30PM +0200, john doe wrote:
> > On 9/4/2021 6:14 PM, Chris Green wrote:
> > > When [re]starting dnsmasq I see the following in syslog:-
> > >
> > > Sep 4 17:01:08 dns dnsmasq[18991]: started, version 2.80
On 04/09/2021 17:14, Chris Green wrote:
> When [re]starting dnsmasq I see the following in syslog:-
>
> Sep 4 17:01:08 dns systemd[1]: dnsmasq.service: Succeeded.
> Sep 4 17:01:08 dns systemd[1]: Stopped dnsmasq - A lightweight DHCP and
> caching DNS server.
> Sep 4 17:01:08 dns sy
On 04/09/2021 21:19, Geert Stappers via Dnsmasq-discuss wrote:
> On Sat, Sep 04, 2021 at 08:16:44PM +0100, Chris Green wrote:
>> On Sat, Sep 04, 2021 at 07:09:30PM +0200, john doe wrote:
>>> On 9/4/2021 6:14 PM, Chris Green wrote:
When [re]starting dnsmasq I see the following in syslog:-
I think if these go in now, we'd need to push back 2.86 for a week or
two for testing.
I've been through them and not found any show-stoppers, so I'm in a
quandary about delaying 2.86 or pushing them to 2.87.
Dominik, you were the one pushing for 2.86. Thoughts?
Simon.
On 03/09/2021 22:47,
On 02/09/2021 21:18, Trey Sis wrote:
> 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:
>>
On 03/09/2021 13:13, Dominik DL6ER wrote:
> Hey Simon,
>
> this small patch adds the DHCP options "posix-timezone" and "tzdb-
> timezone" as defined in RFC 4833, Section 2:
> https://datatracker.ietf.org/doc/html/rfc4833#section-2
>
> Examples for valid options are
>
>> dhcp-option = option:posi
18 matches
Mail list logo
