Public bug reported: I noted it after back from suspend, but could happens on other conditions:
systemd-resolved stopped resolving. <code> $ host google.com 127.0.0.53 Using domain server: Name: 127.0.0.53 Address: 127.0.0.53#53 Aliases: Host google.com not found: 2(SERVFAIL) </code> But resolved service is active without problems. <pre> ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2018-03-27 09:27:46 CEST; 11min ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Main PID: 11822 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 4915) CGroup: /system.slice/systemd-resolved.service └─11822 /lib/systemd/systemd-resolved Mar 27 09:28:01 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:28:06 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:28:42 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:29:07 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:29:11 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:30:11 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:30:32 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:30:37 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:38:10 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:38:15 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. </pre> I checked the network traffic: <pre> 09:38:15.476106 IP 10.66.57.54.48901 > 127.0.0.53.53: 7013+ A? google.com. (28) 09:38:15.476205 IP 127.0.0.53.53 > 127.0.0.1.48901: 7013 ServFail [0q] 0/0/0 (12) </pre> And resolv service works fine: <pre> $ systemd-resolve google.com google.com: 216.58.214.174 -- Information acquired via protocol DNS in 7.2ms. -- Data is authenticated: no </pre> ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 27 09:34:21 2018 InstallationDate: Installed on 2018-02-16 (38 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Apple Inc. MacBookPro11,4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0177.B00.1708080033 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0177.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Description changed: I noted it after back from suspend, but could happens on other conditions: systemd-resolved stopped resolving. - - <pre> + <code> $ host google.com 127.0.0.53 Using domain server: Name: 127.0.0.53 Address: 127.0.0.53#53 - Aliases: + Aliases: Host google.com not found: 2(SERVFAIL) - </pre> + </code> But resolved service is active without problems. <pre> ● systemd-resolved.service - Network Name Resolution - Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) - Active: active (running) since Tue 2018-03-27 09:27:46 CEST; 11min ago - Docs: man:systemd-resolved.service(8) - https://www.freedesktop.org/wiki/Software/systemd/resolved - https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers - https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients - Main PID: 11822 (systemd-resolve) - Status: "Processing requests..." - Tasks: 1 (limit: 4915) - CGroup: /system.slice/systemd-resolved.service - └─11822 /lib/systemd/systemd-resolved + Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) + Active: active (running) since Tue 2018-03-27 09:27:46 CEST; 11min ago + Docs: man:systemd-resolved.service(8) + https://www.freedesktop.org/wiki/Software/systemd/resolved + https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers + https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients + Main PID: 11822 (systemd-resolve) + Status: "Processing requests..." + Tasks: 1 (limit: 4915) + CGroup: /system.slice/systemd-resolved.service + └─11822 /lib/systemd/systemd-resolved Mar 27 09:28:01 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:28:06 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:28:42 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:29:07 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:29:11 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:30:11 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:30:32 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:30:37 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:38:10 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:38:15 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. </pre> I checked the network traffic: <pre> 09:38:15.476106 IP 10.66.57.54.48901 > 127.0.0.53.53: 7013+ A? google.com. (28) 09:38:15.476205 IP 127.0.0.53.53 > 127.0.0.1.48901: 7013 ServFail [0q] 0/0/0 (12) </pre> And resolv service works fine: <pre> $ systemd-resolve google.com google.com: 216.58.214.174 -- Information acquired via protocol DNS in 7.2ms. -- Data is authenticated: no </pre> ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 27 09:34:21 2018 InstallationDate: Installed on 2018-02-16 (38 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Apple Inc. MacBookPro11,4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0177.B00.1708080033 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0177.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759150 Title: systemd stopped resolving after back from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
