[Dnsmasq-discuss] Dnsmasq won't load configfile

[Ruben]

Hi Petr,

Thank you for your feedback.

Tried omitting the ""'s, no difference.

I can confirm that the issue is specific to that line, if I remove it, 
dnsmasq loads the rest of the file just fine.

I did not know about "idn2", thank you for pointing that out. I checked 
the rest of the configfile, that line was not the only line not 
conforming to the check command you showed, just the only one that 
triggers the error. The other non-idn2 compatible domains in the same 
configfile are :


www.xn--eureinkaufsgutscheinehttpam-6jc3d4490n.com.de
idn2: toAscii: string contains a disallowed character: No error: 0
Issue with :
www.xn--mn8hzgsi.ml
idn2: toAscii: string contains a disallowed character: No error: 0
xn--7ib-4y3b.adnxs.com
idn2: toAscii: string contains a disallowed character: No error: 0
Issue with :
xn--eureinkaufsgutscheinehttpam-6jc3d4490n.com.de
idn2: toAscii: string contains a disallowed character: No error: 0
Issue with :
xn--h12srv-vj0c.adk2.com
idn2: toAscii: string contains a disallowed character: No error: 0
Issue with :
xn--izgaa.xvides.com
idn2: toAscii: string contains a disallowed character: No error: 0
Issue with :
xn--mn8hzgsi.ml
idn2: toAscii: string contains a disallowed character: No error: 0
Issue with :
xn--nda-1da.adledge.com
idn2: toAscii: string contains a disallowed character: No error: 0
Issue with :
xn--pixel-2qa5727cj0a.onaudience.com
idn2: toAscii: string contains a disallowed character: No error: 0
Issue with :
xn--rihy934p.ws
idn2: toAscii: string contains a disallowed character: No error: 0
Issue with :
xn--v4-rp0a.moatads.com
idn2: toAscii: string has forbidden bi-directional properties: No error: 0
Issue with :
xn--www-rze3o.xmediaserve.com
idn2: toAscii: string contains a disallowed character: No error: 0
Issue with :
xn--y0h.co.cc

Since a couple of scripts I use generate the configfiles these non-idn2 
conformant domains show up in, I can work around this issue by making 
sure non-idn2 compatible lines will be omitted (which sounds like a 
sensible addition to those scripts anyway).

Since idn2 does not seem to be the (only?) culprit I could perform some 
more debugging to get to the root cause of this issue...

Any - additional :) - ideas?

Kind regards,

Ruben

On 11/5/20 2:28 PM, Petr Menšík wrote:
> I think those quotes should not be there in a config file. Quotes might
> be required for shell on command line, but they are not necessary inside
> config. When you put them away, would it be fixed?
> 
> It seems xn--www-rze3o.xmediaserve.com is not valid, according to idn2.
> 
> idn2 xn--www-rze3o.xmediaserve.com
> idn2: toAscii: string has forbidden bi-directional properties
> 
> but it passes with idn(1):
> idn xn--www-rze3o.xmediaserve.com
> xn--www-rze3o.xmediaserve.com
> 
> But your dnsmasq seems to omit idn support, so it should not be the issue.

stuff snipped