The bug report here is likely inaccurate. I don't exactly know where the problem is.
I did some tcpdumps for port 53 traffic. I see that if I did a ping, it requests for the A records of the domain name and indeed the IP addresses are getting returned. However, weirdly, ping then requests for the A records of pod51041.outlook.com.lan. .lan is the search domain on my network as specified with /etc/resolv.conf automatically. Furthermore, if I disable ipv6, thunderbird and firefox can access the domain, but ping still cannot. So I don't think this bug report should be filed against systemd, but I don't really know where the problem lies. ** Description changed: 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 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 + 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 ** Summary changed: - systemd-resolved sends SERVFAIL to host/nslookup for pod51041.outlook.com + Cannot ping pod51041.outlook.com but can dig. -- 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: Cannot ping pod51041.outlook.com but can dig. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1731522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
