Those hostnames are invalid. No host can start or end with -. Double or
triple does not matter.
Host like 7cjyxsb--.micpn.com should be refused. But I admit it might be
useful to be able to block such invalid names from going forward. For
example with --local=/7cjyxsb--.micpn.com/ might be able
Hi,
I finally managed to understand the problem.
What had happened is that I had updated dnsmasq from the official debian
repository and this time it was compiled with the IDN2 option (which makes
it compliant with domain name rules)
I have downloaded the latest version from source and
Hello and Thanks for the answers
I am a bit confused because I also have a ramips router with dnsmasq 2.85
for openwrt and that problem does not occur.
I was using an excerpt from Dan's full list to explain the problem but with
DeveloperDan's full list
On 23/04/2022 13:14, mito mito wrote:
Hello Friends,
I would appreciate your help on this problem.
I have been using dnsmasq for a couple of years as an home ad/track blocker and in the latest update available for
debian bullseye *dnsmasq-base/stable,now 2.85-1 armhf* *dnsmasq/stable, now
