It is likely to be an upstream problem. Given a zone with A/AAAA records with enough addresses, I can reproduce the problem.
Hacking in systemd source code, I could find those STR: - disable "resolve" in nsswitch.conf - add a resolution against a record with a lot of addresses in src/libsystemd/sd-resolve/test-resolve.c - build test-resolve tool - run ./test-resolve e.g.: > r = sd_resolve_getaddrinfo(resolve, &q2, "test.neteffmon.eu", NULL, &hints, > getaddrinfo_handler, NULL); Running this results in: > Assertion '*length <= maxlength' failed at > src/libsystemd/sd-resolve/sd-resolve.c:203, function serialize_addrinfo(). > Aborting. Changing BUFSIZE in src/libsystemd/sd-resolve/sd-resolve.c to something bigger (e.g. 65536U), rebuild and restart ./test-resolve, the resolution succeeds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665394 Title: DNS resolution of irc.freenode.net or chat.freenode.net fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
