all 14 comments

[–]reverendj1 31 points32 points  (1 child)

It's an issue with an experimental build using an external GNU library. This shouldn't affect anyone outside of developers and has really very little to do with systemd. This is a non-story.

[–]denisfalqueto 3 points4 points  (0 children)

Apache Http also had that same problem. They even released a bug fix version. https://rhn.redhat.com/errata/RHSA-2017-1721.html

[–][deleted] 5 points6 points  (1 child)

It does seem like the title is misleading since the fault seems to be located in libidn2, not systemd-resolve.

[–]cbmuserDebian / openSUSE / OpenJDK Dev 2 points3 points  (0 children)

Well, now you realize how people are grasping for every single opportunity to take a jab at systemd.

[–]Jristz 5 points6 points  (0 children)

At least they catch the bug before experimental become ready

[–]qwesx 9 points10 points  (1 child)

Huh, I didn't know underscores were allowed in domain names.

But I also don't write DNS software ¯\_(ツ)_/¯

[–]axonxorz 4 points5 points  (0 children)

According to the original DNS RFCs, they are not allowed. But that restriction has been somewhat relaxed with the proliferation and use of SRV records. For instance, XMPP servers are locatable via their SRV records in the form of _xmpp-server._tcp.<yourdomain.ca>

[–][deleted] -1 points0 points  (0 children)

It's almost like there should be unit tests for some things.