*** This bug is a duplicate of bug 1731522 ***
https://bugs.launchpad.net/bugs/1731522
** This bug has been marked a duplicate of bug 1731522
systemd-resolved does not listen on TCP port, cannot serve large records
(Cannot ping pod51041.outlook.com but can dig.)
--
You received this bug
It is likely to be an upstream problem. Given a zone with A/ 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
So, comment #5 is somehow invalid, I got the whole story on why it
started to work again: Schiggn (comment #4) contacted some Freenode
staff, and they changed the DNS records to expose less addresses. This
indeed proved to workaround the issue.
--
You received this bug notification because you
Adding back "[NOTFOUND=return] resolve" to /etc/nsswitch.conf, setting
DNSSEC=no in /etc/systemd/resolved.conf, restarting systemd-resolved process
and then:
> $ getent ahosts irc.freenode.net
Gives proper list of hosts
Commenting again the DNSSEC line of resolved.conf, restarting the
service,
iputils/ping was wrong.
On machines with this bug a "getent hosts chat.freenode.net" results in
no output! Perhaps we have to look at getaddrinfo()!
Thanks to the french ubuntu-channel #ubuntu-fr for this hint :)
** No longer affects: iputils (Ubuntu)
--
You received this bug notification
Perhaps this is an issue in iputils/ping if the response is to big. You
can try this with normal ping command too.
ping c1 chat.freeenode.net results in a "ping: chat.freenode.net:
Temporary failure in name resolution"
Using expicit -4 or -6 does work instead.
Workaround as mentioned above:
A workaround is to remove "[NOTFOUND=return] resolve" from
/etc/nsswitch.conf, though it may break other things (but nothing
visible so far).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665394
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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:
