As far as I know, there is no technical or security reason why a Dnsmasq-like
server would *need* this limitation, but Dnsmasq has it due to design
limitiations.
Dnsmasq either responds to a request entirely locally (using /etc/hosts,
records from the config file, and records from DHCP) or
There are much smarter people than me here, but if I might chime in:
Two basic assumptions in networking are that no two separate devices will
share the same MAC address, and a device's MAC address doesn't change after
it's manufactured. Obviously there are practical exceptions (spoofing, privacy
On Mon, Mar 22, 2021, at 2:07 PM, dnsmasqlist2...@rscubed.com wrote:
>
> On Mon, 22 Mar 2021, Geert Stappers via Dnsmasq-discuss wrote:
>
> > On Mon, Mar 22, 2021 at 03:19:00AM +, dnsmasqlist2...@rscubed.com wrote:
> >>
> >> Hi,
> >>
> >> I am trying to do some CNAME filtering but it is not
On Thu, Mar 18, 2021, at 4:52 AM, Geert Stappers via Dnsmasq-discuss wrote:
> On Sun, Feb 21, 2021 at 10:40:37PM +0100, Geert Stappers via
> Dnsmasq-discuss wrote:
> > On Sun, Feb 21, 2021 at 08:39:28PM +, Simon Kelley wrote:
> > > On 19/02/2021 12:35, Matus UHLAR - fantomas wrote:
> > > > On
There's also SIGHUP:
"When it receives a SIGHUP, dnsmasq clears its cache and then re-loads
/etc/hosts and /etc/ethers and any file given by --dhcp-hostsfile,
--dhcp-hostsdir, --dhcp-optsfile, --dhcp-optsdir, --addn-hosts or --hostsdir.
The DHCP lease change script is called for all existing
On Wed, Sep 16, 2020, at 1:36 AM, Geert Stappers wrote:
> > > I was a little surprised this one worked since the previous one
> > > didn't, but I suspect systemd-resolved is falling back to the
> > > FallbackDNS servers (which are hardcoded in if not set explicitly).
>
> > What's the FallbackDNS
On Tue, Sep 15, 2020, at 9:47 AM, Hongyi Zhao wrote:
> On Tue, Sep 15, 2020 at 11:09 AM Dominick C. Pastore
> wrote:
> >
> > On Mon, Sep 14, 2020, at 8:03 PM, Hongyi Zhao wrote:
> > > I run dnsmasq as following:
> > >
> > > $ /usr/local/sbin/dnsm
On Mon, Sep 14, 2020, at 8:03 PM, Hongyi Zhao wrote:
> I run dnsmasq as following:
>
> $ /usr/local/sbin/dnsmasq --port=53 -c10240 --server=127.0.0.1#6053
> --conf-dir=/home/werner/Public/anti-gfw/dns/dnsmasq/conf/conf-dir,*.conf
> -C /home/werner/Public/anti-gfw/dns/dnsmasq/conf/dnsmasq.conf
>
> > Personally, I am not a fan of Netplan for reasons like this. It's supposed
> > to abstract away the details of NetworkManager or systemd-networkd, but it
> > doesn't do a great job of it. You end up having to refer to the
> > NetworkManager or systemd-networkd documentation anyway, and
no efficient way to find such records. The fix is to
>>> insert empty (none of F_IPV4, F_IPV6 F_CNAME set) records for each
>>> non-terminal.
>>>
>>> The same considerations apply in auth mode, and the same basic mechanism
>>> is used there
On Sun, Sep 13, 2020, at 10:44 PM, Hongyi Zhao wrote:
> On Mon, Sep 14, 2020 at 9:02 AM Neal P. Murphy
> wrote:
> >
> > On Mon, 14 Sep 2020 06:52:49 +0800
> > Hongyi Zhao wrote:
> >
> > > On Mon, Sep 14, 2020 at 4:26 AM Geert Stappers
> > > wrote:
> > > >
> > > > On Sun, Sep 13, 2020 at
On Fri, Oct 25, 2019, at 4:48 PM, Simon Kelley wrote:
> On 20/10/2019 17:55, Dominick C. Pastore wrote:
> > I apologize for continuing the discussion on this. The patch (applied on
> > top of 2.80-1 provided by Debian Buster) completely solved the issues I was
> > hav
I have no complaints about a new thread.
On Sun, Oct 20, 2019, at 6:47 PM, Kurt H Maier wrote:
> On Sun, Oct 20, 2019 at 12:55:44PM -0400, Dominick C. Pastore wrote:
> > 2. In fact, Dnsmasq never follows a CNAME for MX or TXT requests, even
> > when the CNAME does point to a hos
ms in my case, but I suspect this
isn't intended behavior either, so it seemed worth mentioning.
Nick
On Sat, Oct 19, 2019, at 12:19 PM, Dominick C. Pastore wrote:
> On Sat, Oct 19, 2019, at 6:16 AM, Simon Kelley wrote:
> > The restriction still applies. indeed the patch relies on it.
>
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 7:41 AM, Simon Kelley wrote:
> I can see a strong argument that a query for a name which is configured
> as a CNAME in dnsmaq, but for a type which is not known to dnsmasq,
> should return a NODATA reply.
>
> In fact I can't see a downside to that.
>
> Anybody else?
>
>
Hello,
I'm having a bit of a problem with the "cname" option in Dnsmasq. I have some
configuration options like these in dnsmasq.conf, where "host1" and "host2"
have IPv4 addresses from DHCP:
domain=philadelphia.example.com
local=/philadelphia.example.com/
dcpx.org and an A record for
> host.cityname.dcpx.org from /etc/hosts.
>
>
> Cheers,
>
> Simon.
>
>
>
> On 24/08/18 21:14, Dominick C. Pastore wrote:
> > Hello,
> >
> > I would like to to configure Dnsmasq so that when it receives a CNAME
Hello,
I would like to to configure Dnsmasq so that when it receives a CNAME record,
if the target is in /etc/hosts, it overrides whatever else the public DNS
server says about that target and uses /etc/hosts instead. Is this possible?
After studying the manual, it seems like not, but I'm
19 matches
Mail list logo
