[Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

This bug was fixed in the package systemd - 237-3ubuntu8 --- systemd (237-3ubuntu8) bionic; urgency=medium * Workaround captive portals not responding to EDNS0 queries (DVE-2018-0001). (LP: #1727237) * resolved: Listen on both TCP and UDP by default. (LP: #1731522) *

[Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

** Description changed: + [Impact] + + * Ubuntu hosts unable to perform queries against certain domains that respond with too big reponses that do not fit over UDP protocol. + * Solution is to enable local cachine DNS server to listen on both UDP and TCP by default + + [Test Case] + + *

[Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

Thanks Dimitri, greatly appreciated. I haven't found many problems in my testing of Bionic, but this is the juiciest one 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/1731522 Title:

[Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

This has totally slipped my radar, I'm sorry. I will ensure this lands into bionic 18.04.0. ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-18.04 ** Also affects: systemd (Ubuntu Bionic)

[Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

Steve, Bionic still has the default (commented-out) #DNSStubListener=udp in /etc/systemd/resolved.conf . I've noticed that this breaks Kerberos KDC lookup at a large site, because the reply is quite large: # host -t SRV _kerberos._udp.xxx.example.com ;; Connection to

[Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731522 Title: systemd-resolved does not listen on TCP port, cannot serve large records

[Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

According to https://github.com/systemd/systemd/issues/6520 this can be worked around by setting DNSStubListener=yes in /etc/systemd/resolved.conf. This is disabled by default due to . It is not ideal to have systemd-resolved conflict with other