Sorry - the last paragraph about the "workaround" does not make any sense,
please discard it.
The issue would indeed to be fixed at the response level.
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.
Hello everyone
I noticed that my dnsmasq server is sending an NXDOMAIN instead of a NODATA
when I query it for records it does not have.
This is, I believe, not the correct behaviour (
https://datatracker.ietf.org/doc/html/rfc2308 - see 1 Terminology → NODATA)
and that response breaks querie
Am 03.08.21 um 12:43 schrieb Greg Wickham:
>
>
>
> Hi,
>
>
>
> I inadvertently left a “tag:” off a “dhcp-boot=“ line which resulted
> in dnsmasq crashing.
>
>
>
> This was the line that caused Dnsmasq to crash:
>
>
>
> dhcp-boot=tag:ww3001,UEFI,/ipxe.efi,10.109.0.1,10.109.0.1
>
>
>
> The
Hi,
how does this help to block something? If responses are dnssec signed,
changing replies would make verification failing.
What is the point of blocking base on IP level in DNS? If you want
blocking target addresses, why just firewall is not used at the router?
What is advantage of using DNS in
