Activity log for bug #1731522

Date Who What changed Old value New value Message
2017-11-10 18:14:41 Shuhao bug added bug
2017-11-28 05:28:08 Shuhao description Trying to resolve pod51041.outlook.com's domain name seems to fail for applications: $ nslookup > host pod51041.outlook.com Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find host: SERVFAIL $ ping pod51041.outlook.com ping: pod51041.outlook.com: Temporary failure in name resolution (Also can't access via thunderbird). However, it seems to work directly via systemd-resolve: $ systemd-resolve pod51041.outlook.com pod51041.outlook.com: 40.97.160.2 40.97.126.50 132.245.38.194 40.97.147.194 132.245.41.34 40.97.176.2 40.97.150.242 40.97.85.114 40.97.120.50 40.97.85.2 40.97.176.34 40.97.138.242 40.97.166.18 40.97.120.162 40.97.119.82 40.97.176.18 40.97.85.98 40.97.134.34 40.97.84.18 -- Information acquired via protocol DNS in 2.5ms. -- Data is authenticated: no Not quite sure why this is the case, I've spotted this issue upstream that looks similar: https://github.com/systemd/systemd/issues/6520. However, I'm not familiar enough with DNS to tell if it is the same issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Fri Nov 10 13:10:02 2017 InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 2324BB9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA6WW (2.66 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324BB9 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324BB9 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO Trying to resolve pod51041.outlook.com's domain name seems to fail for applications: $ ping pod51041.outlook.com ping: pod51041.outlook.com: Temporary failure in name resolution (Also can't access via thunderbird). However, it seems to work directly via systemd-resolve: $ systemd-resolve pod51041.outlook.com pod51041.outlook.com: 40.97.160.2                       40.97.126.50                       132.245.38.194                       40.97.147.194                       132.245.41.34                       40.97.176.2                       40.97.150.242                       40.97.85.114                       40.97.120.50                       40.97.85.2                       40.97.176.34                       40.97.138.242                       40.97.166.18                       40.97.120.162                       40.97.119.82                       40.97.176.18                       40.97.85.98                       40.97.134.34                       40.97.84.18 -- Information acquired via protocol DNS in 2.5ms. -- Data is authenticated: no It also works with dig and nslookup. Not quite sure why this is the case, I've spotted this issue upstream that looks similar: https://github.com/systemd/systemd/issues/6520. However, I'm not familiar enough with DNS to tell if it is the same issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Fri Nov 10 13:10:02 2017 InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 2324BB9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA6WW (2.66 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324BB9 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324BB9 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO
2017-11-28 05:30:27 Shuhao summary systemd-resolved sends SERVFAIL to host/nslookup for pod51041.outlook.com Cannot ping pod51041.outlook.com but can dig.
2017-12-04 00:43:58 Shuhao systemd (Ubuntu): status New Invalid
2017-12-04 00:44:12 Shuhao systemd (Ubuntu): status Invalid New
2017-12-04 01:44:48 EliCoten bug added subscriber EliCoten
2017-12-04 01:44:51 Launchpad Janitor systemd (Ubuntu): status New Confirmed
2018-01-26 19:38:31 Steve Langasek summary Cannot ping pod51041.outlook.com but can dig. systemd-resolved fails to fall back to TCP for large records (Cannot ping pod51041.outlook.com but can dig.)
2018-01-26 19:48:29 Steve Langasek systemd (Ubuntu): importance Undecided High
2018-01-26 19:48:29 Steve Langasek systemd (Ubuntu): status Confirmed Triaged
2018-01-26 19:48:59 Steve Langasek summary systemd-resolved fails to fall back to TCP for large records (Cannot ping pod51041.outlook.com but can dig.) systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)
2018-01-26 19:59:15 Steve Langasek bug watch added https://github.com/systemd/systemd/issues/6520
2018-01-26 19:59:15 Steve Langasek bug task added systemd
2018-01-26 21:34:16 Bug Watch Updater systemd: status Unknown Fix Released
2018-04-05 06:05:56 Daniel Richard G. bug added subscriber Daniel Richard G.
2018-04-05 07:57:49 Dimitri John Ledkov systemd (Ubuntu): assignee Dimitri John Ledkov (xnox)
2018-04-05 07:57:56 Dimitri John Ledkov systemd (Ubuntu): milestone ubuntu-18.04
2018-04-05 08:02:56 Dimitri John Ledkov nominated for series Ubuntu Bionic
2018-04-05 08:02:56 Dimitri John Ledkov bug task added systemd (Ubuntu Bionic)
2018-04-05 08:02:56 Dimitri John Ledkov nominated for series Ubuntu Artful
2018-04-05 08:02:56 Dimitri John Ledkov bug task added systemd (Ubuntu Artful)
2018-04-05 08:03:01 Dimitri John Ledkov systemd (Ubuntu Artful): assignee Dimitri John Ledkov (xnox)
2018-04-05 08:03:03 Dimitri John Ledkov systemd (Ubuntu Artful): milestone artful-updates
2018-04-05 08:03:05 Dimitri John Ledkov systemd (Ubuntu Artful): status New Triaged
2018-04-05 08:03:08 Dimitri John Ledkov systemd (Ubuntu Artful): importance Undecided High
2018-04-06 14:05:30 Dimitri John Ledkov description Trying to resolve pod51041.outlook.com's domain name seems to fail for applications: $ ping pod51041.outlook.com ping: pod51041.outlook.com: Temporary failure in name resolution (Also can't access via thunderbird). However, it seems to work directly via systemd-resolve: $ systemd-resolve pod51041.outlook.com pod51041.outlook.com: 40.97.160.2                       40.97.126.50                       132.245.38.194                       40.97.147.194                       132.245.41.34                       40.97.176.2                       40.97.150.242                       40.97.85.114                       40.97.120.50                       40.97.85.2                       40.97.176.34                       40.97.138.242                       40.97.166.18                       40.97.120.162                       40.97.119.82                       40.97.176.18                       40.97.85.98                       40.97.134.34                       40.97.84.18 -- Information acquired via protocol DNS in 2.5ms. -- Data is authenticated: no It also works with dig and nslookup. Not quite sure why this is the case, I've spotted this issue upstream that looks similar: https://github.com/systemd/systemd/issues/6520. However, I'm not familiar enough with DNS to tell if it is the same issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Fri Nov 10 13:10:02 2017 InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 2324BB9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA6WW (2.66 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324BB9 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324BB9 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO [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] * nslookup -q=aaaa pod51041.outlook.com 127.0.0.53 Should work and return a bunch of ipv6 answers. Note, this expects that the upstream DNS server used by resolved is "a sensitble" one, e.g. my default ISP/router did not work, whilst forcing 8.8.8.8 via network manager for this connection made it work. [Regression Potential] * Given that resolved will now bind to a TCP port 53, this may result in a conflict with deployed DNS servers which do not correctly take over port 53 or bind to everything. * In those cases the software should be fixed to not bind to all interfaces and/or to not bind on 127.0.0.53, or change resolved to have DNSStubListener set to 'udp'. [Other Info] * Original bug report === Trying to resolve pod51041.outlook.com's domain name seems to fail for applications: $ ping pod51041.outlook.com ping: pod51041.outlook.com: Temporary failure in name resolution (Also can't access via thunderbird). However, it seems to work directly via systemd-resolve: $ systemd-resolve pod51041.outlook.com pod51041.outlook.com: 40.97.160.2                       40.97.126.50                       132.245.38.194                       40.97.147.194                       132.245.41.34                       40.97.176.2                       40.97.150.242                       40.97.85.114                       40.97.120.50                       40.97.85.2                       40.97.176.34                       40.97.138.242                       40.97.166.18                       40.97.120.162                       40.97.119.82                       40.97.176.18                       40.97.85.98                       40.97.134.34                       40.97.84.18 -- Information acquired via protocol DNS in 2.5ms. -- Data is authenticated: no It also works with dig and nslookup. Not quite sure why this is the case, I've spotted this issue upstream that looks similar: https://github.com/systemd/systemd/issues/6520. However, I'm not familiar enough with DNS to tell if it is the same issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Fri Nov 10 13:10:02 2017 InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 2324BB9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA6WW (2.66 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324BB9 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324BB9 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO
2018-04-06 14:05:44 Dimitri John Ledkov description [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] * nslookup -q=aaaa pod51041.outlook.com 127.0.0.53 Should work and return a bunch of ipv6 answers. Note, this expects that the upstream DNS server used by resolved is "a sensitble" one, e.g. my default ISP/router did not work, whilst forcing 8.8.8.8 via network manager for this connection made it work. [Regression Potential] * Given that resolved will now bind to a TCP port 53, this may result in a conflict with deployed DNS servers which do not correctly take over port 53 or bind to everything. * In those cases the software should be fixed to not bind to all interfaces and/or to not bind on 127.0.0.53, or change resolved to have DNSStubListener set to 'udp'. [Other Info] * Original bug report === Trying to resolve pod51041.outlook.com's domain name seems to fail for applications: $ ping pod51041.outlook.com ping: pod51041.outlook.com: Temporary failure in name resolution (Also can't access via thunderbird). However, it seems to work directly via systemd-resolve: $ systemd-resolve pod51041.outlook.com pod51041.outlook.com: 40.97.160.2                       40.97.126.50                       132.245.38.194                       40.97.147.194                       132.245.41.34                       40.97.176.2                       40.97.150.242                       40.97.85.114                       40.97.120.50                       40.97.85.2                       40.97.176.34                       40.97.138.242                       40.97.166.18                       40.97.120.162                       40.97.119.82                       40.97.176.18                       40.97.85.98                       40.97.134.34                       40.97.84.18 -- Information acquired via protocol DNS in 2.5ms. -- Data is authenticated: no It also works with dig and nslookup. Not quite sure why this is the case, I've spotted this issue upstream that looks similar: https://github.com/systemd/systemd/issues/6520. However, I'm not familiar enough with DNS to tell if it is the same issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Fri Nov 10 13:10:02 2017 InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 2324BB9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA6WW (2.66 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324BB9 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324BB9 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO [Impact]  * Ubuntu hosts unable to perform queries against certain domains that respond with too big responses 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]  * nslookup -q=aaaa pod51041.outlook.com 127.0.0.53 Should work and return a bunch of ipv6 answers. Note, this expects that the upstream DNS server used by resolved is "a sensitble" one, e.g. my default ISP/router did not work, whilst forcing 8.8.8.8 via network manager for this connection made it work. [Regression Potential]  * Given that resolved will now bind to a TCP port 53, this may result in a conflict with deployed DNS servers which do not correctly take over port 53 or bind to everything.  * In those cases the software should be fixed to not bind to all interfaces and/or to not bind on 127.0.0.53, or change resolved to have DNSStubListener set to 'udp'. [Other Info]  * Original bug report === Trying to resolve pod51041.outlook.com's domain name seems to fail for applications: $ ping pod51041.outlook.com ping: pod51041.outlook.com: Temporary failure in name resolution (Also can't access via thunderbird). However, it seems to work directly via systemd-resolve: $ systemd-resolve pod51041.outlook.com pod51041.outlook.com: 40.97.160.2                       40.97.126.50                       132.245.38.194                       40.97.147.194                       132.245.41.34                       40.97.176.2                       40.97.150.242                       40.97.85.114                       40.97.120.50                       40.97.85.2                       40.97.176.34                       40.97.138.242                       40.97.166.18                       40.97.120.162                       40.97.119.82                       40.97.176.18                       40.97.85.98                       40.97.134.34                       40.97.84.18 -- Information acquired via protocol DNS in 2.5ms. -- Data is authenticated: no It also works with dig and nslookup. Not quite sure why this is the case, I've spotted this issue upstream that looks similar: https://github.com/systemd/systemd/issues/6520. However, I'm not familiar enough with DNS to tell if it is the same issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Fri Nov 10 13:10:02 2017 InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 2324BB9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA6WW (2.66 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324BB9 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324BB9 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO
2018-04-06 14:12:21 Dimitri John Ledkov systemd (Ubuntu Bionic): status Triaged Fix Committed
2018-04-13 11:24:24 Launchpad Janitor systemd (Ubuntu Bionic): status Fix Committed Fix Released