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 to accept even invalid names and report them with just a warning. But defining an address served by dnsmasq should be still forbidden on invalid hostnames. On 5/2/22 16:11, mito mito wrote: > 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 commented out the > IDN2 related lines and no longer have any problems. > > I will refrain from using IDN2 until the entire internet complies with > these rules. > > Greetings > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemen...@redhat.com PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
_______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
