[Bug 1681597] Re: DNS broken after >50m of uptime

lotuspsychje lotuspsychje at gmail.com
Mon May 15 02:33:20 UTC 2017 

*** This bug is a duplicate of bug 1682499 ***
    https://bugs.launchpad.net/bugs/1682499


Installed 17.10 64bit development branch on a daily .iso @ 14/5/2017

problem is solved after editing: /etc/systemd/resolved.conf DNSSEC=off
and reboot

tnx to answer #4

another duplicate:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1690605

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1681597

Title:
  DNS broken after >50m of uptime

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After about 50m of uptime news.ycombinator.com stops working in Chromium: news.ycombinator.com’s server's DNS address could not be found. DNS_PROBE_FINISHED_NXDOMAIN
  $ host news.ycombinator.com
  Host news.ycombinator.com not found: 2(SERVFAIL)

  This is a *regression* from Ubuntu 16.10, where DNS worked flawlessly.

  Workarounds:
   * 'systemctl restart systemd-resolved' solves the problem for another 50m
   * disable systemd-resolved and use the DNS server directly. This involves removing 'resolve [!UNAVAIL=return]' from nsswitch.conf, and disabling the systemd-resolved unit

  Logs show DNSSEC related errors, and DNSSEC getting disabled and reenabled:
  -- Logs begin at Mon 2017-04-10 23:10:59 BST, end at Tue 2017-04-11 00:11:14 BST. --
  Apr 10 23:11:01 bolt systemd[1]: Starting Network Name Resolution...
  Apr 10 23:11:01 bolt systemd-resolved[1351]: Positive Trust Anchors:
  Apr 10 23:11:01 bolt systemd-resolved[1351]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Apr 10 23:11:01 bolt systemd-resolved[1351]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Apr 10 23:11:01 bolt systemd-resolved[1351]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
  Apr 10 23:11:01 bolt systemd-resolved[1351]: Using system hostname 'bolt'.
  Apr 10 23:11:01 bolt systemd[1]: Started Network Name Resolution.
  Apr 10 23:11:05 bolt systemd-resolved[1351]: Switching to DNS server 194.168.4.100 for interface wlp3s0.
  Apr 10 23:11:06 bolt systemd-resolved[1351]: Using degraded feature set (UDP+EDNS0) for DNS server 194.168.4.100.
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question com IN SOA: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question ubuntu.com IN DS: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question ubuntu.com IN SOA: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN DS: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN SOA: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN A: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: Server 194.168.4.100 does not support DNSSEC, downgrading to non-DNSSEC mode.
  Apr 10 23:11:06 bolt systemd-resolved[1351]: Switching to DNS server 194.168.8.100 for interface wlp3s0.
  Apr 10 23:11:07 bolt systemd-resolved[1351]: Using degraded feature set (UDP+EDNS0) for DNS server 194.168.8.100.
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question clamav.net IN DS: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question clamav.net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question cvd.clamav.net IN DS: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question cvd.clamav.net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question current.cvd.clamav.net IN DS: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question current.cvd.clamav.net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question current.cvd.clamav.net IN TXT: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: Server 194.168.8.100 does not support DNSSEC, downgrading to non-DNSSEC mode.
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN A: failed-auxiliary
  Apr 10 23:11:52 bolt systemd[1]: Stopping Network Name Resolution...
  Apr 10 23:11:52 bolt systemd[1]: Stopped Network Name Resolution.
  Apr 10 23:11:52 bolt systemd[1]: Starting Network Name Resolution...
  Apr 10 23:11:52 bolt systemd-resolved[2868]: Positive Trust Anchors:
  Apr 10 23:11:52 bolt systemd-resolved[2868]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Apr 10 23:11:52 bolt systemd-resolved[2868]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Apr 10 23:11:52 bolt systemd-resolved[2868]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
  Apr 10 23:11:52 bolt systemd-resolved[2868]: Using system hostname 'bolt'.
  Apr 10 23:11:52 bolt systemd[1]: Started Network Name Resolution.
  Apr 10 23:11:54 bolt systemd-resolved[2868]: Switching to DNS server 194.168.4.100 for interface wlp3s0.
  Apr 10 23:11:54 bolt systemd-resolved[2868]: Using degraded feature set (UDP+EDNS0) for DNS server 194.168.4.100.
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question com IN SOA: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question ycombinator.com IN DS: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question ycombinator.com IN SOA: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question news.ycombinator.com IN A: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question google.com IN DS: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question google.com IN SOA: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question apis.google.com IN A: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question gstatic.com IN SOA: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question ssl.gstatic.com IN DS: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question ssl.gstatic.com IN SOA: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question ssl.gstatic.com IN A: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question www.gstatic.com IN DS: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question www.gstatic.com IN SOA: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question www.gstatic.com IN A: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: Server 194.168.4.100 does not support DNSSEC, downgrading to non-DNSSEC mode.
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question www.google.co.uk IN SOA: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question www.google.co.uk IN A: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question translate.googleapis.com IN SOA: failed-auxiliary
  Apr 10 23:11:54 bolt systemd-resolved[2868]: DNSSEC validation failed for question translate.googleapis.com IN A: failed-auxiliary
  Apr 10 23:11:58 bolt systemd[1]: Stopping Network Name Resolution...
  Apr 10 23:11:58 bolt systemd[1]: Stopped Network Name Resolution.
  Apr 10 23:11:58 bolt systemd[1]: Starting Network Name Resolution...
  Apr 10 23:11:58 bolt systemd-resolved[3034]: Positive Trust Anchors:
  Apr 10 23:11:58 bolt systemd-resolved[3034]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Apr 10 23:11:58 bolt systemd-resolved[3034]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Apr 10 23:11:58 bolt systemd-resolved[3034]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
  Apr 10 23:11:58 bolt systemd-resolved[3034]: Using system hostname 'bolt'.
  Apr 10 23:11:59 bolt systemd[1]: Started Network Name Resolution.
  Apr 10 23:12:01 bolt systemd-resolved[3034]: Switching to DNS server 194.168.4.100 for interface wlp3s0.
  Apr 10 23:12:01 bolt systemd-resolved[3034]: Using degraded feature set (UDP+EDNS0) for DNS server 194.168.4.100.
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question com IN SOA: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question google.com IN DS: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question google.com IN SOA: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question apis.google.com IN A: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question ycombinator.com IN DS: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question ycombinator.com IN SOA: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question news.ycombinator.com IN A: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question ssl.gstatic.com IN SOA: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question ssl.gstatic.com IN A: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question translate.googleapis.com IN SOA: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question translate.googleapis.com IN A: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: Server 194.168.4.100 does not support DNSSEC, downgrading to non-DNSSEC mode.
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question www.google.co.uk IN SOA: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question www.google.co.uk IN A: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question www.gstatic.com IN SOA: failed-auxiliary
  Apr 10 23:12:01 bolt systemd-resolved[3034]: DNSSEC validation failed for question www.gstatic.com IN A: failed-auxiliary
  Apr 10 23:12:16 bolt systemd[1]: Stopping Network Name Resolution...
  Apr 10 23:12:16 bolt systemd[1]: Stopped Network Name Resolution.
  Apr 10 23:12:16 bolt systemd[1]: Starting Network Name Resolution...
  Apr 10 23:12:17 bolt systemd-resolved[3292]: Positive Trust Anchors:
  Apr 10 23:12:17 bolt systemd-resolved[3292]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Apr 10 23:12:17 bolt systemd-resolved[3292]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Apr 10 23:12:17 bolt systemd-resolved[3292]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
  Apr 10 23:12:17 bolt systemd-resolved[3292]: Using system hostname 'bolt'.
  Apr 10 23:12:17 bolt systemd[1]: Started Network Name Resolution.
  Apr 10 23:22:38 bolt systemd-resolved[3292]: Switching to DNS server 194.168.4.100 for interface wlp3s0.
  Apr 10 23:22:38 bolt systemd-resolved[3292]: Using degraded feature set (UDP+EDNS0) for DNS server 194.168.4.100.
  Apr 10 23:22:38 bolt systemd-resolved[3292]: DNSSEC validation failed for question google.com IN DS: failed-auxiliary
  Apr 10 23:22:38 bolt systemd-resolved[3292]: DNSSEC validation failed for question google.com IN SOA: failed-auxiliary
  Apr 10 23:22:38 bolt systemd-resolved[3292]: DNSSEC validation failed for question apis.google.com IN A: failed-auxiliary
  Apr 10 23:22:38 bolt systemd-resolved[3292]: Server 194.168.4.100 does not support DNSSEC, downgrading to non-DNSSEC mode.
  Apr 10 23:22:38 bolt systemd-resolved[3292]: DNSSEC validation failed for question co.uk IN SOA: failed-auxiliary
  Apr 10 23:22:38 bolt systemd-resolved[3292]: DNSSEC validation failed for question www.google.co.uk IN SOA: failed-auxiliary
  Apr 10 23:22:38 bolt systemd-resolved[3292]: DNSSEC validation failed for question www.google.co.uk IN A: failed-auxiliary
  Apr 10 23:22:39 bolt systemd-resolved[3292]: Switching to DNS server 194.168.8.100 for interface wlp3s0.
  Apr 10 23:22:39 bolt systemd-resolved[3292]: Using degraded feature set (UDP+EDNS0) for DNS server 194.168.8.100.
  Apr 10 23:22:39 bolt systemd-resolved[3292]: DNSSEC validation failed for question com IN SOA: failed-auxiliary
  Apr 10 23:22:39 bolt systemd-resolved[3292]: DNSSEC validation failed for question gstatic.com IN DS: failed-auxiliary
  Apr 10 23:22:39 bolt systemd-resolved[3292]: DNSSEC validation failed for question gstatic.com IN SOA: failed-auxiliary
  Apr 10 23:22:39 bolt systemd-resolved[3292]: DNSSEC validation failed for question ssl.gstatic.com IN DS: failed-auxiliary
  Apr 10 23:22:39 bolt systemd-resolved[3292]: DNSSEC validation failed for question ssl.gstatic.com IN SOA: failed-auxiliary
  Apr 10 23:22:39 bolt systemd-resolved[3292]: DNSSEC validation failed for question ssl.gstatic.com IN A: failed-auxiliary
  Apr 10 23:22:39 bolt systemd-resolved[3292]: Server 194.168.8.100 does not support DNSSEC, downgrading to non-DNSSEC mode.
  Apr 10 23:54:29 bolt systemd-resolved[3292]: Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 194.168.8.100.
  Apr 11 00:01:24 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN DS: no-signature
  Apr 11 00:01:24 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN SOA: no-signature
  Apr 11 00:01:24 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN A: no-signature
  Apr 11 00:01:25 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN DS: no-signature
  Apr 11 00:01:25 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN SOA: no-signature
  Apr 11 00:01:25 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN A: no-signature
  Apr 11 00:01:30 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN DS: no-signature
  Apr 11 00:01:30 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN SOA: no-signature
  Apr 11 00:01:30 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN A: no-signature
  Apr 11 00:02:00 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN DS: no-signature
  Apr 11 00:02:00 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN SOA: no-signature
  Apr 11 00:02:00 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN A: no-signature
  Apr 11 00:03:00 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN DS: no-signature
  Apr 11 00:03:00 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN SOA: no-signature
  Apr 11 00:03:00 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN A: no-signature
  Apr 11 00:09:02 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN DS: no-signature
  Apr 11 00:09:02 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN SOA: no-signature
  Apr 11 00:09:02 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN A: no-signature
  Apr 11 00:09:03 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN DS: no-signature
  Apr 11 00:09:03 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN SOA: no-signature
  Apr 11 00:09:03 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN A: no-signature
  Apr 11 00:09:03 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN DS: no-signature
  Apr 11 00:09:03 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN SOA: no-signature
  Apr 11 00:09:03 bolt systemd-resolved[3292]: DNSSEC validation failed for question news.ycombinator.com.cdn.cloudflare.net IN A: no-signature

  
  I tried setting 'DNSSEC=allow-downgrade' in /etc/systemd/resolved.conf, but the problem happened again (although restarting systemd-resolved temporarily fixes the problem as shown above), so I set it back to default.

  The manpage of systemd-resolved.conf incorrectly claims that DNSSEC=
  defaults to off, I haven't confirmed whether turning off DNSSEC fixes
  the problem yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Apr 11 00:03:27 2017
  InstallationDate: Installed on 2017-03-25 (15 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99FX PRO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  mtime.conffile..etc.systemd.resolved.conf: 2017-04-10T23:09:03.981037

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1681597/+subscriptions

More information about the foundations-bugs mailing list