On 31/03/2023 14:28, Petr Menšík wrote:
I agree with Dominik.
--cache-rr=!TXT,!DNSKEY,!DS or maybe just --no-cache-rr=TXT,DNSKEY,DS
would be more useful.
For my own preference it would be more useful to cache ANY record by
default, maybe with exceptions of explicitly listed records. I
On 31/03/2023 08:25, Dominik Derigs wrote:
Hey Simon,
On Thu, 2023-03-30 at 18:28 +0100, Simon Kelley wrote:
I just merged the branch I've been working on for the last week which
includes this patch, but much modified because the surrounding code has
changed. The function is unaltered.
The
On 30/03/2023 22:00, 0zl wrote:
Greetings,
I believe this might be a bug in dnsmasq. When using the shorthand
`domain=mydomain.com,local` and `dhcp-fqdn`, dnsmasq fails with:
`there must be a default domain when --dhcp-fqdn is set`
I'm not sure if this is intended behavior or not, but
You technically don’t need a zone transfer, you can use a conditional forwarder
on the Active Directory DNS. Setup a conditional forwarder for casa.lan and
point it to the IP of your router where dnsmasq is running. After that, when AD
DNS receives a query for anything in the casa.lan domain,
El vie, 31 mar 2023 a las 17:29, Andrew Miskell ()
escribió:
> You technically don’t need a zone transfer, you can use a conditional
> forwarder on the Active Directory DNS. Setup a conditional forwarder for
> casa.lan and point it to the IP of your router where dnsmasq is running.
> After that,
El vie, 31 mar 2023 a las 2:45, Andrew Miskell ()
escribió:
> What exactly are you trying to accomplish? Your windows clients to be able
> to resolve the clients on your router’s domain (casa.lan) via DNS?
> Yes, this is what I need, but I'm unable to list the clients from the
> dominio.lab
I agree with Dominik.
--cache-rr=!TXT,!DNSKEY,!DS or maybe just --no-cache-rr=TXT,DNSKEY,DS
would be more useful.
For my own preference it would be more useful to cache ANY record by
default, maybe with exceptions of explicitly listed records. I think it
would be nice to specify maximal
Hey Simon,
On Thu, 2023-03-30 at 18:28 +0100, Simon Kelley wrote:
> I just merged the branch I've been working on for the last week which
> includes this patch, but much modified because the surrounding code has
> changed. The function is unaltered.
>
> The other changes are adding the ability
