I don't have much info about the server. It's on an enterprise intranet. No doubt something ancient.
> I did wonder if this might happen. In an ideal world an option wouldn't > be necessary, but you've shown that it is. > > Can you share with us what the misbehaving server is? > > I guess some logging suggesting the option when this occurs would be > useful too. > > Cheers, > > Simon. > > > On 03/02/2025 17:27, wornandrew via Dnsmasq-discuss wrote: > > > Hi. > > I've ran into a misbehaving server which doesn't preserve case in replies. > > (e.g. if query is exAMPLE.Com then the response is example.com) > > This causes dnsmasq to drop the replies as malicious. > > > > This was not noticeable before 0x20 encoding was implemented in 2.91 > > as clients only ever sent lowercase queries. But now dnsmasq mangles > > the case of all forwarded names with no apparent way to avoid this. > > > > It would be nice to have an option to bypass 0x20 encoding for forwarded > > queries and instead send them as is. > > > > _______________________________________________ > > Dnsmasq-discuss mailing listve > > Dnsmasq-discuss@lists.thekelleys.org.uk > > https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss > > > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss