On Sat, Oct 19, 2019 at 10:21:21PM +0200, Geert Stappers wrote:
> On Sat, Oct 19, 2019 at 09:02:19PM +0100, Chris Green wrote:
> > > >
> > > > I've suddenly lost the ability to resolve local machine names without
> > > > a domain suffix, e.g.:-
> > > >
> > > > ... and on a Linux machine on the LA
On Sat, Oct 19, 2019 at 09:02:19PM +0100, Chris Green wrote:
> On Sat, Oct 19, 2019 at 09:00:27PM +0200, Geert Stappers wrote:
> > On Sat, Oct 19, 2019 at 07:31:49PM +0100, Chris Green wrote:
> > > I've run dnsmasq for several years on my small home LAN. I'm running
> > > dnsmasq on a raspberry-pi
On Sat, Oct 19, 2019 at 09:00:27PM +0200, Geert Stappers wrote:
> On Sat, Oct 19, 2019 at 07:31:49PM +0100, Chris Green wrote:
> > I've run dnsmasq for several years on my small home LAN. I'm running
> > dnsmasq on a raspberry-pi and most of the client machines on the LAN
> > are linux (xubuntu).
On Sat, Oct 19, 2019 at 07:31:49PM +0100, Chris Green wrote:
> I've run dnsmasq for several years on my small home LAN. I'm running
> dnsmasq on a raspberry-pi and most of the client machines on the LAN
> are linux (xubuntu).
>
> I've suddenly lost the ability to resolve local machine names witho
I've run dnsmasq for several years on my small home LAN. I'm running
dnsmasq on a raspberry-pi and most of the client machines on the LAN
are linux (xubuntu).
I've suddenly lost the ability to resolve local machine names without
a domain suffix, e.g.:-
On the Raspberry Pi itself:-
chris
On Sat, Oct 19, 2019, at 6:16 AM, Simon Kelley wrote:
> The restriction still applies. indeed the patch relies on it.
>
> The origin of this is that, for architectural reasons, dnsmasq can only
> supply a reply which originates completely from locally known data, or
> completely from a reply from
On Fri, Oct 18, 2019 at 03:25:36PM -0500, Carl Karsten wrote:
> On Mon, Oct 14, 2019 at 2:13 AM Geert Stappers wrote:
> > On Fri, Oct 04, 2019 at 08:37:03AM +0200, john doe wrote:
> > > On 10/4/2019 1:25 AM, Geert Stappers wrote:
> > > > On Thu, Oct 03, 2019 at 06:01:17PM -0500, Carl Karsten wrote:
The restriction still applies. indeed the patch relies on it.
The origin of this is that, for architectural reasons, dnsmasq can only
supply a reply which originates completely from locally known data, or
completely from a reply from upstream. Since a local CNAME to a target
in the public DNS nece
