Bug 220521 - dns/dnsmasq: SRV Records served incorrectly with IDN / NLS options set, needs dns/libidn2 MFH to 2017Q3
Summary: dns/dnsmasq: SRV Records served incorrectly with IDN / NLS options set, needs...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Many People
Assignee: Matthias Andree
URL: https://svnweb.freebsd.org/ports/head...
Keywords: easy, regression
Depends on:
Reported: 2017-07-06 15:53 UTC by Chris
Modified: 2017-08-17 18:34 UTC (History)
1 user (show)

See Also:
mandree: maintainer-feedback+
mandree: merge-quarterly+


Note You need to log in before you can comment on or make changes to this bug.
Description Chris 2017-07-06 15:53:09 UTC
After upgrading dns/dnsmasq (2.76,1 -> 2.77_1,1), I found that SRV records related to my local XMPP server were not being served.

dnsmasq configuration:

When querying '_xmpp-server._tcp.domain.com' there is no result.

I found that querying 'xmpp-server.tcp.domain.com' I got the result I was expecting, so somewhere the underscores are being removed.

This only happens when the IDN or NLS options are set. If no IDN support is enabled, dnsmasq works properly.
Comment 1 Matthias Andree freebsd_committer 2017-07-06 20:53:54 UTC
...with a relevant change being the move from libidn to libidn2. 

I have little time to debug this and have just forwarded it to the the developer's mailing list, dnsmasq-discuss, see http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss and in particular http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2017q3/011620.html
Comment 2 Matthias Andree freebsd_committer 2017-08-12 11:25:51 UTC
This has been overcome by events, the consumed libidn2 library, as of its release 2.0.3, fixes this issue: 
* http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2017q3/011676.html
* https://gitlab.com/libidn/libidn2/raw/8c3d4f81f99ca5b235cbf9e03aede43702e54f9c/NEWS

I will seek ports-secteam@'s permission to MFH the libidn2 update
Comment 3 Matthias Andree freebsd_committer 2017-08-12 11:28:24 UTC
The upgrade of 2.76 to 2.77 is not to blame, I made the switch from libidn to libidn2 at the same time when updating dnsmasq and thus inherited libidn's regression between the 1.x and 2.0.2 that was current at the time this report got filed.
Comment 4 Matthias Andree freebsd_committer 2017-08-12 11:34:25 UTC
Need to MFH 446595 and 447146 of dns/libidn2 to 2017Q3
Comment 5 Matthias Andree freebsd_committer 2017-08-17 18:33:59 UTC
MFH'd to 2017Q3 as r448147: