systemd-resolved not starting on bootHow do I debug “Temporary failure in name resolution” error after upgrading to Xubuntu 19.04 desktop?Ubuntu 17.04 systemd-resolved configurationsystemd-resolved does not query dns server for local domainDNS over TLS with systemd-resolvedsystemd-resolved not resolving specific domainsWhy is dhclient + systemd-resolved restarting frequently?

I'm from Mumbai, India. I want to travel to Europe as a tourist but my salary is low ( €190/month). I have described my situation in the body

Coordinate entry in QGIS 3

My mysterious "ruins" wander around and change on their own, what'd be a rational way for them to do that?

Making sense of possessed dolls: how could they actually kill people?

At what point in time would humans notice a 21st century satellite observing them?

Equality operator does not get defined for a custom spaceship operator implementation in C++20

Black powder machine gun in an airplane

Using footnotes in fiction: children's book which can be enjoyed by adults

Object Oriented Programming - how to avoid duplication in processes that differ slightly depending on a variable

How to avoid after work hours team dinner?

Where is a warlock's soul?

How does sudo handle $HOME differently since 19.10?

Identify the Eeveelutions

Bo Derek in texbook.tex?

Average Two Letters

How did we arrive at Major/Minor tonality, and why did we settle on it?

Linearity assumption of linear regression

Offensive/negative meaning of 雑草

Is it possible to get reverse life insurance?

Which were the reasons/need for Israel's "Freedom Of Occupation" Basic Laws?

How to reduce distance between two line of Vert?

Horizontally mirror a brainflak program

Impact wrench on spark plugs?

What is my volume?



systemd-resolved not starting on boot


How do I debug “Temporary failure in name resolution” error after upgrading to Xubuntu 19.04 desktop?Ubuntu 17.04 systemd-resolved configurationsystemd-resolved does not query dns server for local domainDNS over TLS with systemd-resolvedsystemd-resolved not resolving specific domainsWhy is dhclient + systemd-resolved restarting frequently?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









3

















When I boot my Ubuntu server, DNS resolving does not work. You can most easily see this by looking at resolv.conf:



~ # cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.


I then enable the resolved service:



~ # systemctl enable systemd-resolved.service


And things work as expected:



~ # cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53


Config



  • Ubuntu 19.04

  • 5.0.0-23-generic

Related packages installed:



~ # cat /etc/resodpkg -l |grep systemd
ii libnss-resolve:amd64 240-6ubuntu5.2 amd64 nss module to resolve names via systemd-resolved
ii libnss-systemd:amd64 240-6ubuntu5.2 amd64 nss module providing dynamic user and group name resolution
ii libpam-systemd:amd64 240-6ubuntu5.2 amd64 system and service manager - PAM module
ii libsystemd0:amd64 240-6ubuntu5.2 amd64 systemd utility library
ii networkd-dispatcher 2.0-2 all Dispatcher service for systemd-networkd connection status changes
ii python3-systemd 234-2build2 amd64 Python 3 bindings for systemd
ii systemd 240-6ubuntu5.2 amd64 system and service manager
ii systemd-sysv 240-6ubuntu5.2 amd64 system and service manager - SysV links
~ # dpkg -l |grepdpkg -l |grep resolv
ii libc-ares2:amd64 1.14.0-1 amd64 asynchronous name resolver
ii libgeoip1:amd64 1.6.12-1 amd64 non-DNS IP-to-country resolver library
ii libnss-resolve:amd64 240-6ubuntu5.2 amd64 nss module to resolve names via systemd-resolved
ii resolvconf 1.79ubuntu13 all name server information handler


Name resolution worked on boot prior to updating to 19.04.



No apparent errors in syslog. Related excerpt:



Aug 3 11:41:16 green systemd[1]: Starting Network Name Resolution...
Aug 3 11:41:16 green systemd-resolved[807]: Positive Trust Anchors:
Aug 3 11:41:16 green systemd-resolved[807]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 3 11:41:16 green systemd-resolved[807]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 3 11:41:16 green systemd-resolved[807]: 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.arp
Aug 3 11:41:16 green systemd[1]: Started Network Name Resolution.


Status before reboot (with nameserver listed in /etc/resolv.conf):



~ # systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
 Active: active (running) since Sat 2019-08-03 11:39:32 EDT; 2 days 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: 807 (systemd-resolve)
 Status: "Processing requests..."
 Tasks: 1 (limit: 4915)
 Memory: 7.9M
 CGroup: /system.slice/systemd-resolved.service
 └─807 /lib/systemd/systemd-resolved

Aug 06 10:00:38 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:15:53 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature


Status before reboot (with nothing listed in /etc/resolv.conf):



~ # systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
 Active: active (running) since Tue 2019-08-06 10:23:53 EDT; 1min 9s 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: 798 (systemd-resolve)
 Status: "Processing requests..."
 Tasks: 1 (limit: 4915)
 Memory: 7.8M
 CGroup: /system.slice/systemd-resolved.service
 └─798 /lib/systemd/systemd-resolved

Aug 06 10:23:51 green systemd[1]: Starting Network Name Resolution...
Aug 06 10:23:52 green systemd-resolved[798]: Positive Trust Anchors:
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 06 10:23:52 green systemd-resolved[798]: 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.
Aug 06 10:23:52 green systemd-resolved[798]: Using system hostname 'green'.
Aug 06 10:23:53 green systemd[1]: Started Network Name Resolution.

~ # systemd-resolve --status
Global
 LLMNR setting: no
MulticastDNS setting: no
 DNSOverTLS setting: no
 DNSSEC setting: no
 DNSSEC supported: no
 Current DNS Server: 8.8.8.8
 DNS Servers: 8.8.8.8
 8.8.4.4
 DNSSEC NTA: 10.in-addr.arpa
 16.172.in-addr.arpa
 168.192.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
 corp
 d.f.ip6.arpa
 home
 internal
 intranet
 lan
 local
 private
 test

Link 3 (eno2)
 Current Scopes: none
DefaultRoute setting: no
 LLMNR setting: yes
MulticastDNS setting: no
 DNSOverTLS setting: no
 DNSSEC setting: no
 DNSSEC supported: no

Link 2 (eno1)
 Current Scopes: none
DefaultRoute setting: no
 LLMNR setting: yes
MulticastDNS setting: no
 DNSOverTLS setting: no
 DNSSEC setting: no
 DNSSEC supported: no


After systemctl enable systemd-resolved.service(with nameserver listed in /etc/resolv.conf):



~ # systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
 Active: active (running) since Tue 2019-08-06 10:23:53 EDT; 3min 47s 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: 798 (systemd-resolve)
 Status: "Processing requests..."
 Tasks: 1 (limit: 4915)
 Memory: 7.9M
 CGroup: /system.slice/systemd-resolved.service
 └─798 /lib/systemd/systemd-resolved

Aug 06 10:23:52 green systemd-resolved[798]: Positive Trust Anchors:
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 06 10:23:52 green systemd-resolved[798]: 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.
Aug 06 10:23:52 green systemd-resolved[798]: Using system hostname 'green'.
Aug 06 10:23:53 green systemd[1]: Started Network Name Resolution.
Aug 06 10:27:32 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:27:35 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:27:35 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:27:35 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature


systemd-resolve --status shows the same as before.






networking dns 19.04







share|improve this question




























  • Try systemctl enable and an implicit systemctl start.

    – heynnema
    Aug 3 at 16:17











  • you have to run systemctl enable... every time you reboot?

    – Joshua Besneatte
    Aug 3 at 16:23











  • @heynnema As you can see, I've tried systemctl enable. Unfortunately, it only starts the resolver, but doesn't keep it running after a reboot.

    – Paul Schreiber
    Aug 3 at 20:18






  • 1





    Are you using sudo?

    – heynnema
    Aug 3 at 20:19






  • 1





    I've seen some commands... like fsck not work from a # prompt without the use of sudo. Try sudo systemctl enable... and sudo systemctl start... and see if it makes any difference.

    – heynnema
    Aug 3 at 23:54

















3

















When I boot my Ubuntu server, DNS resolving does not work. You can most easily see this by looking at resolv.conf:



~ # cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.


I then enable the resolved service:



~ # systemctl enable systemd-resolved.service


And things work as expected:



~ # cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53


Config



  • Ubuntu 19.04

  • 5.0.0-23-generic

Related packages installed:



~ # cat /etc/resodpkg -l |grep systemd
ii libnss-resolve:amd64 240-6ubuntu5.2 amd64 nss module to resolve names via systemd-resolved
ii libnss-systemd:amd64 240-6ubuntu5.2 amd64 nss module providing dynamic user and group name resolution
ii libpam-systemd:amd64 240-6ubuntu5.2 amd64 system and service manager - PAM module
ii libsystemd0:amd64 240-6ubuntu5.2 amd64 systemd utility library
ii networkd-dispatcher 2.0-2 all Dispatcher service for systemd-networkd connection status changes
ii python3-systemd 234-2build2 amd64 Python 3 bindings for systemd
ii systemd 240-6ubuntu5.2 amd64 system and service manager
ii systemd-sysv 240-6ubuntu5.2 amd64 system and service manager - SysV links
~ # dpkg -l |grepdpkg -l |grep resolv
ii libc-ares2:amd64 1.14.0-1 amd64 asynchronous name resolver
ii libgeoip1:amd64 1.6.12-1 amd64 non-DNS IP-to-country resolver library
ii libnss-resolve:amd64 240-6ubuntu5.2 amd64 nss module to resolve names via systemd-resolved
ii resolvconf 1.79ubuntu13 all name server information handler


Name resolution worked on boot prior to updating to 19.04.



No apparent errors in syslog. Related excerpt:



Aug 3 11:41:16 green systemd[1]: Starting Network Name Resolution...
Aug 3 11:41:16 green systemd-resolved[807]: Positive Trust Anchors:
Aug 3 11:41:16 green systemd-resolved[807]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 3 11:41:16 green systemd-resolved[807]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 3 11:41:16 green systemd-resolved[807]: 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.arp
Aug 3 11:41:16 green systemd[1]: Started Network Name Resolution.


Status before reboot (with nameserver listed in /etc/resolv.conf):



~ # systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
 Active: active (running) since Sat 2019-08-03 11:39:32 EDT; 2 days 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: 807 (systemd-resolve)
 Status: "Processing requests..."
 Tasks: 1 (limit: 4915)
 Memory: 7.9M
 CGroup: /system.slice/systemd-resolved.service
 └─807 /lib/systemd/systemd-resolved

Aug 06 10:00:38 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:15:53 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature


Status before reboot (with nothing listed in /etc/resolv.conf):



~ # systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
 Active: active (running) since Tue 2019-08-06 10:23:53 EDT; 1min 9s 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: 798 (systemd-resolve)
 Status: "Processing requests..."
 Tasks: 1 (limit: 4915)
 Memory: 7.8M
 CGroup: /system.slice/systemd-resolved.service
 └─798 /lib/systemd/systemd-resolved

Aug 06 10:23:51 green systemd[1]: Starting Network Name Resolution...
Aug 06 10:23:52 green systemd-resolved[798]: Positive Trust Anchors:
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 06 10:23:52 green systemd-resolved[798]: 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.
Aug 06 10:23:52 green systemd-resolved[798]: Using system hostname 'green'.
Aug 06 10:23:53 green systemd[1]: Started Network Name Resolution.

~ # systemd-resolve --status
Global
 LLMNR setting: no
MulticastDNS setting: no
 DNSOverTLS setting: no
 DNSSEC setting: no
 DNSSEC supported: no
 Current DNS Server: 8.8.8.8
 DNS Servers: 8.8.8.8
 8.8.4.4
 DNSSEC NTA: 10.in-addr.arpa
 16.172.in-addr.arpa
 168.192.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
 corp
 d.f.ip6.arpa
 home
 internal
 intranet
 lan
 local
 private
 test

Link 3 (eno2)
 Current Scopes: none
DefaultRoute setting: no
 LLMNR setting: yes
MulticastDNS setting: no
 DNSOverTLS setting: no
 DNSSEC setting: no
 DNSSEC supported: no

Link 2 (eno1)
 Current Scopes: none
DefaultRoute setting: no
 LLMNR setting: yes
MulticastDNS setting: no
 DNSOverTLS setting: no
 DNSSEC setting: no
 DNSSEC supported: no


After systemctl enable systemd-resolved.service(with nameserver listed in /etc/resolv.conf):



~ # systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
 Active: active (running) since Tue 2019-08-06 10:23:53 EDT; 3min 47s 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: 798 (systemd-resolve)
 Status: "Processing requests..."
 Tasks: 1 (limit: 4915)
 Memory: 7.9M
 CGroup: /system.slice/systemd-resolved.service
 └─798 /lib/systemd/systemd-resolved

Aug 06 10:23:52 green systemd-resolved[798]: Positive Trust Anchors:
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 06 10:23:52 green systemd-resolved[798]: 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.
Aug 06 10:23:52 green systemd-resolved[798]: Using system hostname 'green'.
Aug 06 10:23:53 green systemd[1]: Started Network Name Resolution.
Aug 06 10:27:32 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:27:35 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:27:35 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:27:35 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature


systemd-resolve --status shows the same as before.






networking dns 19.04







share|improve this question




























  • Try systemctl enable and an implicit systemctl start.

    – heynnema
    Aug 3 at 16:17











  • you have to run systemctl enable... every time you reboot?

    – Joshua Besneatte
    Aug 3 at 16:23











  • @heynnema As you can see, I've tried systemctl enable. Unfortunately, it only starts the resolver, but doesn't keep it running after a reboot.

    – Paul Schreiber
    Aug 3 at 20:18






  • 1





    Are you using sudo?

    – heynnema
    Aug 3 at 20:19






  • 1





    I've seen some commands... like fsck not work from a # prompt without the use of sudo. Try sudo systemctl enable... and sudo systemctl start... and see if it makes any difference.

    – heynnema
    Aug 3 at 23:54













3












3








3








When I boot my Ubuntu server, DNS resolving does not work. You can most easily see this by looking at resolv.conf:



~ # cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.


I then enable the resolved service:



~ # systemctl enable systemd-resolved.service


And things work as expected:



~ # cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53


Config



  • Ubuntu 19.04

  • 5.0.0-23-generic

Related packages installed:



~ # cat /etc/resodpkg -l |grep systemd
ii libnss-resolve:amd64 240-6ubuntu5.2 amd64 nss module to resolve names via systemd-resolved
ii libnss-systemd:amd64 240-6ubuntu5.2 amd64 nss module providing dynamic user and group name resolution
ii libpam-systemd:amd64 240-6ubuntu5.2 amd64 system and service manager - PAM module
ii libsystemd0:amd64 240-6ubuntu5.2 amd64 systemd utility library
ii networkd-dispatcher 2.0-2 all Dispatcher service for systemd-networkd connection status changes
ii python3-systemd 234-2build2 amd64 Python 3 bindings for systemd
ii systemd 240-6ubuntu5.2 amd64 system and service manager
ii systemd-sysv 240-6ubuntu5.2 amd64 system and service manager - SysV links
~ # dpkg -l |grepdpkg -l |grep resolv
ii libc-ares2:amd64 1.14.0-1 amd64 asynchronous name resolver
ii libgeoip1:amd64 1.6.12-1 amd64 non-DNS IP-to-country resolver library
ii libnss-resolve:amd64 240-6ubuntu5.2 amd64 nss module to resolve names via systemd-resolved
ii resolvconf 1.79ubuntu13 all name server information handler


Name resolution worked on boot prior to updating to 19.04.



No apparent errors in syslog. Related excerpt:



Aug 3 11:41:16 green systemd[1]: Starting Network Name Resolution...
Aug 3 11:41:16 green systemd-resolved[807]: Positive Trust Anchors:
Aug 3 11:41:16 green systemd-resolved[807]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 3 11:41:16 green systemd-resolved[807]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 3 11:41:16 green systemd-resolved[807]: 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.arp
Aug 3 11:41:16 green systemd[1]: Started Network Name Resolution.


Status before reboot (with nameserver listed in /etc/resolv.conf):



~ # systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
 Active: active (running) since Sat 2019-08-03 11:39:32 EDT; 2 days 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: 807 (systemd-resolve)
 Status: "Processing requests..."
 Tasks: 1 (limit: 4915)
 Memory: 7.9M
 CGroup: /system.slice/systemd-resolved.service
 └─807 /lib/systemd/systemd-resolved

Aug 06 10:00:38 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:15:53 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature


Status before reboot (with nothing listed in /etc/resolv.conf):



~ # systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
 Active: active (running) since Tue 2019-08-06 10:23:53 EDT; 1min 9s 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: 798 (systemd-resolve)
 Status: "Processing requests..."
 Tasks: 1 (limit: 4915)
 Memory: 7.8M
 CGroup: /system.slice/systemd-resolved.service
 └─798 /lib/systemd/systemd-resolved

Aug 06 10:23:51 green systemd[1]: Starting Network Name Resolution...
Aug 06 10:23:52 green systemd-resolved[798]: Positive Trust Anchors:
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 06 10:23:52 green systemd-resolved[798]: 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.
Aug 06 10:23:52 green systemd-resolved[798]: Using system hostname 'green'.
Aug 06 10:23:53 green systemd[1]: Started Network Name Resolution.

~ # systemd-resolve --status
Global
 LLMNR setting: no
MulticastDNS setting: no
 DNSOverTLS setting: no
 DNSSEC setting: no
 DNSSEC supported: no
 Current DNS Server: 8.8.8.8
 DNS Servers: 8.8.8.8
 8.8.4.4
 DNSSEC NTA: 10.in-addr.arpa
 16.172.in-addr.arpa
 168.192.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
 corp
 d.f.ip6.arpa
 home
 internal
 intranet
 lan
 local
 private
 test

Link 3 (eno2)
 Current Scopes: none
DefaultRoute setting: no
 LLMNR setting: yes
MulticastDNS setting: no
 DNSOverTLS setting: no
 DNSSEC setting: no
 DNSSEC supported: no

Link 2 (eno1)
 Current Scopes: none
DefaultRoute setting: no
 LLMNR setting: yes
MulticastDNS setting: no
 DNSOverTLS setting: no
 DNSSEC setting: no
 DNSSEC supported: no


After systemctl enable systemd-resolved.service(with nameserver listed in /etc/resolv.conf):



~ # systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
 Active: active (running) since Tue 2019-08-06 10:23:53 EDT; 3min 47s 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: 798 (systemd-resolve)
 Status: "Processing requests..."
 Tasks: 1 (limit: 4915)
 Memory: 7.9M
 CGroup: /system.slice/systemd-resolved.service
 └─798 /lib/systemd/systemd-resolved

Aug 06 10:23:52 green systemd-resolved[798]: Positive Trust Anchors:
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 06 10:23:52 green systemd-resolved[798]: 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.
Aug 06 10:23:52 green systemd-resolved[798]: Using system hostname 'green'.
Aug 06 10:23:53 green systemd[1]: Started Network Name Resolution.
Aug 06 10:27:32 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:27:35 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:27:35 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:27:35 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature


systemd-resolve --status shows the same as before.






networking dns 19.04







share|improve this question

















When I boot my Ubuntu server, DNS resolving does not work. You can most easily see this by looking at resolv.conf:



~ # cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.


I then enable the resolved service:



~ # systemctl enable systemd-resolved.service


And things work as expected:



~ # cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53


Config



  • Ubuntu 19.04

  • 5.0.0-23-generic

Related packages installed:



~ # cat /etc/resodpkg -l |grep systemd
ii libnss-resolve:amd64 240-6ubuntu5.2 amd64 nss module to resolve names via systemd-resolved
ii libnss-systemd:amd64 240-6ubuntu5.2 amd64 nss module providing dynamic user and group name resolution
ii libpam-systemd:amd64 240-6ubuntu5.2 amd64 system and service manager - PAM module
ii libsystemd0:amd64 240-6ubuntu5.2 amd64 systemd utility library
ii networkd-dispatcher 2.0-2 all Dispatcher service for systemd-networkd connection status changes
ii python3-systemd 234-2build2 amd64 Python 3 bindings for systemd
ii systemd 240-6ubuntu5.2 amd64 system and service manager
ii systemd-sysv 240-6ubuntu5.2 amd64 system and service manager - SysV links
~ # dpkg -l |grepdpkg -l |grep resolv
ii libc-ares2:amd64 1.14.0-1 amd64 asynchronous name resolver
ii libgeoip1:amd64 1.6.12-1 amd64 non-DNS IP-to-country resolver library
ii libnss-resolve:amd64 240-6ubuntu5.2 amd64 nss module to resolve names via systemd-resolved
ii resolvconf 1.79ubuntu13 all name server information handler


Name resolution worked on boot prior to updating to 19.04.



No apparent errors in syslog. Related excerpt:



Aug 3 11:41:16 green systemd[1]: Starting Network Name Resolution...
Aug 3 11:41:16 green systemd-resolved[807]: Positive Trust Anchors:
Aug 3 11:41:16 green systemd-resolved[807]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 3 11:41:16 green systemd-resolved[807]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 3 11:41:16 green systemd-resolved[807]: 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.arp
Aug 3 11:41:16 green systemd[1]: Started Network Name Resolution.


Status before reboot (with nameserver listed in /etc/resolv.conf):



~ # systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
 Active: active (running) since Sat 2019-08-03 11:39:32 EDT; 2 days 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: 807 (systemd-resolve)
 Status: "Processing requests..."
 Tasks: 1 (limit: 4915)
 Memory: 7.9M
 CGroup: /system.slice/systemd-resolved.service
 └─807 /lib/systemd/systemd-resolved

Aug 06 10:00:38 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:04:06 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:15:53 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:17:05 green systemd-resolved[807]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature


Status before reboot (with nothing listed in /etc/resolv.conf):



~ # systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
 Active: active (running) since Tue 2019-08-06 10:23:53 EDT; 1min 9s 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: 798 (systemd-resolve)
 Status: "Processing requests..."
 Tasks: 1 (limit: 4915)
 Memory: 7.8M
 CGroup: /system.slice/systemd-resolved.service
 └─798 /lib/systemd/systemd-resolved

Aug 06 10:23:51 green systemd[1]: Starting Network Name Resolution...
Aug 06 10:23:52 green systemd-resolved[798]: Positive Trust Anchors:
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 06 10:23:52 green systemd-resolved[798]: 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.
Aug 06 10:23:52 green systemd-resolved[798]: Using system hostname 'green'.
Aug 06 10:23:53 green systemd[1]: Started Network Name Resolution.

~ # systemd-resolve --status
Global
 LLMNR setting: no
MulticastDNS setting: no
 DNSOverTLS setting: no
 DNSSEC setting: no
 DNSSEC supported: no
 Current DNS Server: 8.8.8.8
 DNS Servers: 8.8.8.8
 8.8.4.4
 DNSSEC NTA: 10.in-addr.arpa
 16.172.in-addr.arpa
 168.192.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
 corp
 d.f.ip6.arpa
 home
 internal
 intranet
 lan
 local
 private
 test

Link 3 (eno2)
 Current Scopes: none
DefaultRoute setting: no
 LLMNR setting: yes
MulticastDNS setting: no
 DNSOverTLS setting: no
 DNSSEC setting: no
 DNSSEC supported: no

Link 2 (eno1)
 Current Scopes: none
DefaultRoute setting: no
 LLMNR setting: yes
MulticastDNS setting: no
 DNSOverTLS setting: no
 DNSSEC setting: no
 DNSSEC supported: no


After systemctl enable systemd-resolved.service(with nameserver listed in /etc/resolv.conf):



~ # systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
 Active: active (running) since Tue 2019-08-06 10:23:53 EDT; 3min 47s 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: 798 (systemd-resolve)
 Status: "Processing requests..."
 Tasks: 1 (limit: 4915)
 Memory: 7.9M
 CGroup: /system.slice/systemd-resolved.service
 └─798 /lib/systemd/systemd-resolved

Aug 06 10:23:52 green systemd-resolved[798]: Positive Trust Anchors:
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 06 10:23:52 green systemd-resolved[798]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 06 10:23:52 green systemd-resolved[798]: 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.
Aug 06 10:23:52 green systemd-resolved[798]: Using system hostname 'green'.
Aug 06 10:23:53 green systemd[1]: Started Network Name Resolution.
Aug 06 10:27:32 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:27:35 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:27:35 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature
Aug 06 10:27:35 green systemd-resolved[798]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature


systemd-resolve --status shows the same as before.






networking dns 19.04




networking dns 19.04






share|improve this question
















share|improve this question













share|improve this question




share|improve this question








edited Aug 6 at 14:30







Paul Schreiber

















asked Aug 3 at 15:48









Paul SchreiberPaul Schreiber

1001 silver badge9 bronze badges




1001 silver badge9 bronze badges















  • Try systemctl enable and an implicit systemctl start.

    – heynnema
    Aug 3 at 16:17











  • you have to run systemctl enable... every time you reboot?

    – Joshua Besneatte
    Aug 3 at 16:23











  • @heynnema As you can see, I've tried systemctl enable. Unfortunately, it only starts the resolver, but doesn't keep it running after a reboot.

    – Paul Schreiber
    Aug 3 at 20:18






  • 1





    Are you using sudo?

    – heynnema
    Aug 3 at 20:19






  • 1





    I've seen some commands... like fsck not work from a # prompt without the use of sudo. Try sudo systemctl enable... and sudo systemctl start... and see if it makes any difference.

    – heynnema
    Aug 3 at 23:54

















  • Try systemctl enable and an implicit systemctl start.

    – heynnema
    Aug 3 at 16:17











  • you have to run systemctl enable... every time you reboot?

    – Joshua Besneatte
    Aug 3 at 16:23











  • @heynnema As you can see, I've tried systemctl enable. Unfortunately, it only starts the resolver, but doesn't keep it running after a reboot.

    – Paul Schreiber
    Aug 3 at 20:18






  • 1





    Are you using sudo?

    – heynnema
    Aug 3 at 20:19






  • 1





    I've seen some commands... like fsck not work from a # prompt without the use of sudo. Try sudo systemctl enable... and sudo systemctl start... and see if it makes any difference.

    – heynnema
    Aug 3 at 23:54
















Try systemctl enable and an implicit systemctl start.

– heynnema
Aug 3 at 16:17





Try systemctl enable and an implicit systemctl start.

– heynnema
Aug 3 at 16:17













you have to run systemctl enable... every time you reboot?

– Joshua Besneatte
Aug 3 at 16:23





you have to run systemctl enable... every time you reboot?

– Joshua Besneatte
Aug 3 at 16:23













@heynnema As you can see, I've tried systemctl enable. Unfortunately, it only starts the resolver, but doesn't keep it running after a reboot.

– Paul Schreiber
Aug 3 at 20:18





@heynnema As you can see, I've tried systemctl enable. Unfortunately, it only starts the resolver, but doesn't keep it running after a reboot.

– Paul Schreiber
Aug 3 at 20:18




1




1





Are you using sudo?

– heynnema
Aug 3 at 20:19





Are you using sudo?

– heynnema
Aug 3 at 20:19




1




1





I've seen some commands... like fsck not work from a # prompt without the use of sudo. Try sudo systemctl enable... and sudo systemctl start... and see if it makes any difference.

– heynnema
Aug 3 at 23:54





I've seen some commands... like fsck not work from a # prompt without the use of sudo. Try sudo systemctl enable... and sudo systemctl start... and see if it makes any difference.

– heynnema
Aug 3 at 23:54










1 Answer
1






active

oldest

votes


















2


















You installed something like resolvconf which cuts sytemd-resolved off entirely by commenting out the 53 listening address in stub-resolv.conf which the /etc/resolv.conf should link to.For a fresh Ubuntu 18.04 install, the only additional name resolution package I needed was libnss-resolve. I never use resolvconf, so don't know why you need it.






share|improve this answer



























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "89"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );














    draft saved

    draft discarded
















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1163183%2fsystemd-resolved-not-starting-on-boot%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown


























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2


















    You installed something like resolvconf which cuts sytemd-resolved off entirely by commenting out the 53 listening address in stub-resolv.conf which the /etc/resolv.conf should link to.For a fresh Ubuntu 18.04 install, the only additional name resolution package I needed was libnss-resolve. I never use resolvconf, so don't know why you need it.






    share|improve this answer






























      2


















      You installed something like resolvconf which cuts sytemd-resolved off entirely by commenting out the 53 listening address in stub-resolv.conf which the /etc/resolv.conf should link to.For a fresh Ubuntu 18.04 install, the only additional name resolution package I needed was libnss-resolve. I never use resolvconf, so don't know why you need it.






      share|improve this answer




























        2














        2










        2









        You installed something like resolvconf which cuts sytemd-resolved off entirely by commenting out the 53 listening address in stub-resolv.conf which the /etc/resolv.conf should link to.For a fresh Ubuntu 18.04 install, the only additional name resolution package I needed was libnss-resolve. I never use resolvconf, so don't know why you need it.






        share|improve this answer














        You installed something like resolvconf which cuts sytemd-resolved off entirely by commenting out the 53 listening address in stub-resolv.conf which the /etc/resolv.conf should link to.For a fresh Ubuntu 18.04 install, the only additional name resolution package I needed was libnss-resolve. I never use resolvconf, so don't know why you need it.







        share|improve this answer













        share|improve this answer




        share|improve this answer










        answered Aug 9 at 14:43









        ubfan1ubfan1

        11k4 gold badges20 silver badges31 bronze badges




        11k4 gold badges20 silver badges31 bronze badges































            draft saved

            draft discarded















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid …


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1163183%2fsystemd-resolved-not-starting-on-boot%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown









            -

            Popular posts from this blog

            Distance measures on a map of a game The 2019 Stack Overflow Developer Survey Results Are Inmin distance in a graphShortest distance path on contour plotHow to plot a tilted map?Finding points outside of a diskDelaunay link distanceAnnulus from GeoDisks: drawing a ring on a mapNegative Correlation DistanceFind distance along a path (GPS coordinates)Finding position at given distance in a GeoPathMathematics behind distance estimation using camera

            Image
            Delete all lines which don't have n characters before delimiter How to manage monthly salary Deal with toxic manager when you can't quit Button changing it's text & action. Good or terrible? For what reasons would an animal species NOT cross a *horizontal* land bridge? Why do some words that are not inflected have an umlaut? Are there any other methods to apply to solving simultaneous equations? Does a dangling wire really electrocute me if I'm standing in water? Right tool to dig six foot holes? Is there a symbol for a right arrow with a square in the middle? Can a rogue use sneak attack with weapons that have the thrown property even if they are not thrown? What is the motivation for a law requiring 2 parties to consent for recording a conversation What is the accessibility of a package's `Private` context variables? Is "plugging out" electronic devices an American expression? Is there any way to tell whether the shot is g...
            Read more

            How to get a smooth, uniform ParametricPlot of a 2D Region?How to plot a complicated Region?How to exclude a region from ParametricPlotHow discretize a region placing vertices on a specific non-uniform gridHow to transform a Plot or a ParametricPlot into a RegionHow can I get a smooth plot of a bounded region?Smooth ParametricPlot3D with RegionFunction?Smooth border of a region ParametricPlotSmooth region boundarySmooth region plot from list of pointsGet minimum y of a certain x in a region

            Image
            Did "2001: A Space Odyssey" make any reference to the names of companies, or show any evidence of the existence of advertisements? Pros and cons of playing correspondence chess How do professors and lecturers learn to teach? Is it OK for a Buddhist teacher to charge their students an hourly rate for their time? Do insurance rates depend on credit scores? Why does California seem to have much more aggressive Consumer Protection and Safety Legislation? Query more than 50000 records Is this medieval picture of hanging 5 royals showing an historical event? Film about the USA being run by fake videos of the president after his kidnapping Is American Express widely accepted in Hong Kong? How many atoms in the hydrocarbon? How do you give spell casters xp? If a picture of a screen is a screenshot, what is a video of a screen? Is there any plausible in-between of Endotherms and Ectotherms? How can we save ourselves from large drops in stock price? How wo...
            Read more

            Training a classifier when some of the features are unknownWhy does Gradient Boosting regression predict negative values when there are no negative y-values in my training set?How to improve an existing (trained) classifier?What is effect when I set up some self defined predisctor variables?Why Matlab neural network classification returns decimal values on prediction dataset?Fitting and transforming text data in training, testing, and validation setsHow to quantify the performance of the classifier (multi-class SVM) using the test data?How do I control for some patients providing multiple samples in my training data?Training and Test setTraining a convolutional neural network for image denoising in MatlabShouldn't an autoencoder with #(neurons in hidden layer) = #(neurons in input layer) be “perfect”?

            Image
            Extremely casual way to make requests to very close friends Why are Gatwick's runways too close together? AsyncDictionary - Can you break thread safety? Different inverter (logic gate) symbols Y2K... in 2019? Withdrew when Jimmy met up with Heath Christian apologetics regarding the killing of innocent children during the Genesis flood How does 'AND' distribute over 'OR' (Set Theory)? Ex-contractor published company source code and secrets online how to differentiate when a child lwc component is called twice in parent component? Infeasibility in mathematical optimization models How is this kind of structure made? Plausibility of Ice Eaters in the Arctic Tikzpicture - finish drawing a curved line for a cake slice Why is transplanting a specific intact brain impossible if it is generally possible? How to create all combinations from a nested list while preserving the structure using R? What should I call bands of armed men in Medieval T...
            Read more