Hi,
On 22/11/2022 07:00:26; Simon Kelley via Dnsmasq-discuss wrote:
> This behaviour arises from the way dnsmasq works. It doesn't attempt to
> completely parse the reply packet, it just sends it bit-for-bit to the
> original requestor. This has the advantage dnsmasq as a DNS forwarder is
> tra
Great! I tried comparing the implementation of GOST to bind or unbound,
which I have seen before. But found they both lack any implementation of
GOST. Anyway, It seems working fine. Tried it on my Fedora 36 and in
CentOS 8 container. Centos as expected resolves GOST related algorithms
without A
This behaviour arises from the way dnsmasq works. It doesn't attempt to
completely parse the reply packet, it just sends it bit-for-bit to the
original requestor. This has the advantage dnsmasq as a DNS forwarder is
transparent: new packet formats or data types that it doesn't understand
are st
Thanks for this. It was in my mind that vary large number of domains
would be --local=/domain/ or --address=/domain/, not forwarding to servers.
I've applied something that looks very like your patch, but with
cosmetic code changes.
Cheers,
Simon.
On 20/11/2022 05:50, Ye Zhou wrote:
Hi al
