This patch extends the `--address` option to accept two new special
address, `!A` and `!`, which will cause the server to block A or
queries for the specified domain(s), respectively. This can be
useful in situations where IPv6 connectivity is broken, but only to
certain domains.
Signed-o
On Wed, 18 Jan 2023, Buck Horn wrote:
This patch extends the `--address` option to accept two new special
address, `!4` and `!6`, which will cause the server to block A or
queries for the specified domain(s), respectively.
I may be a bit late, but somehow, naming the options '!4' and '!6'
On Thu, Jan 19, 2023 at 02:03:18PM +, Craig Wright via Dnsmasq-discuss
wrote:
> Hi,I am trying to allocate all hosts that join my network with a
> hostname beginning 'MB' to a specific DHCP range.
How did the does devices a hostname beginnen with 'MB'?
Could those devices get a "VendorID" in
Hi,I am trying to allocate all hosts that join my network with a hostname
beginning 'MB' to a specific DHCP range.After much internet research I can't
find if there is a solution.So far I have got:
dhcp-range=tag:mbdevices,192.168.0.50,192.168.0.60,255.255.255.0,12h
and have trieddhcp-host=MB*,se
On 19/01/2023 10:53, Simon Kelley wrote:
From a quick scan of the draft, this is not trivial.
It looks like one form of the record is effectively a re-implementation
of CNAME, and all replies have lots of extra processing. It's not simply
a case of adding the ability to store a new RRtype i
From a quick scan of the draft, this is not trivial.
It looks like one form of the record is effectively a re-implementation
of CNAME, and all replies have lots of extra processing. It's not simply
a case of adding the ability to store a new RRtype in the cache; replies
to queries for that typ
