Hello, when I power on my laptop, I got a dns problem, I can’t load any web page that use a domain name. sudo systemctl restart NetworkManager solve the problem untill the next startup.
Check when the issue happens:
grep -e ^hosts: /etc/nsswitch.conf
ls -l -Z /etc/resolv.conf
systemctl status systemd-resolved.service
resolvectl status --no-pager
resolvectl query example.org --no-pager
grep -e ^hosts: /etc/nsswitch.conf
hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns
ls -l -Z /etc/resolv.conf
lrwxrwxrwx. 1 root root system_u:object_r:net_conf_t:s0 39 13 avril 23:47 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Wed 2023-10-11 16:42:57 CEST; 3min 11s ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 5571 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 18375)
Memory: 5.3M
CPU: 142ms
CGroup: /system.slice/systemd-resolved.service
└─5571 /usr/lib/systemd/systemd-resolved
oct. 11 16:42:57 fedora systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
oct. 11 16:42:57 fedora systemd-resolved[5571]: Positive Trust Anchors:
oct. 11 16:42:57 fedora systemd-resolved[5571]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
oct. 11 16:42:57 fedora systemd-resolved[5571]: Negative trust anchors: home.arpa 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-add>
oct. 11 16:42:57 fedora systemd-resolved[5571]: Using system hostname 'fedora'.
oct. 11 16:42:57 fedora systemd[1]: Started systemd-resolved.service - Network Name Resolution.
oct. 11 16:42:57 fedora systemd-resolved[5571]: wlp3s0: Bus client set default route setting: yes
oct. 11 16:42:57 fedora systemd-resolved[5571]: wlp3s0: Bus client set DNS server list to: 192.168.0.254
oct. 11 16:42:58 fedora systemd-resolved[5571]: wlp3s0: Bus client set DNS server list to: 192.168.0.254, fd0f:ee:b0::1
resolvectl status --no-pager
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Current DNS Server: 1.1.1.1#cloudflare-dns.com
DNS Servers: 1.1.1.1#cloudflare-dns.com
Fallback DNS Servers: 9.9.9.9
Link 2 (enp2s0)
Current Scopes: none
Protocols: -DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 3 (wlp3s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.0.254
DNS Servers: 192.168.0.254 fd0f:ee:b0::1
I ran these command after the restart of Network manager
We need to check this while the issue is still happening, i.e. before restarting NetworkManager.
It seem that resolvectl status --no-pager and resolvectl query example.org --no-pager both solves temporarly the problem
grep -e ^hosts: /etc/nsswitch.conf
hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns
ls -l -Z /etc/resolv.conf
lrwxrwxrwx. 1 root root system_u:object_r:net_conf_t:s0 39 13 avril 23:47 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
systemctl status systemd-resolved.service
× systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Thu 2023-10-12 18:35:04 CEST; 1min 53s ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Process: 972 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, status=1/FAILURE)
Main PID: 972 (code=exited, status=1/FAILURE)
Error: 13 (Permission non accordée)
CPU: 61ms
oct. 12 18:35:04 fedora systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5.
oct. 12 18:35:04 fedora systemd[1]: Stopped systemd-resolved.service - Network Name Resolution.
oct. 12 18:35:04 fedora systemd[1]: systemd-resolved.service: Start request repeated too quickly.
oct. 12 18:35:04 fedora systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
oct. 12 18:35:04 fedora systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
oct. 12 18:35:13 fedora systemd[1]: systemd-resolved.service: Start request repeated too quickly.
oct. 12 18:35:13 fedora systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
oct. 12 18:35:13 fedora systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
resolvectl status --no-pager
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Current DNS Server: 1.1.1.1#cloudflare-dns.com
DNS Servers: 1.1.1.1#cloudflare-dns.com
Fallback DNS Servers: 9.9.9.9
Link 2 (enp2s0)
Current Scopes: none
Protocols: -DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 3 (wlp3s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.0.254
DNS Servers: 192.168.0.254 fd0f:ee:b0::1
1 Like
journalctl --no-pager -b -u systemd-resolved.service
journalctl --no-pager -b -u systemd-resolved.service
oct. 12 18:55:37 fedora systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
oct. 12 18:55:37 fedora systemd-resolved[924]: Positive Trust Anchors:
oct. 12 18:55:37 fedora systemd-resolved[924]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
oct. 12 18:55:37 fedora systemd-resolved[924]: Negative trust anchors: home.arpa 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
oct. 12 18:55:37 fedora systemd-resolved[924]: Using system hostname 'fedora'.
oct. 12 18:55:37 fedora systemd-resolved[924]: Failed to connect to system bus: Permission denied
oct. 12 18:55:37 fedora systemd-resolved[924]: Could not create manager: Permission denied
oct. 12 18:55:37 fedora systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
oct. 12 18:55:37 fedora systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
oct. 12 18:55:37 fedora systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
oct. 12 18:55:37 fedora systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 1.
oct. 12 18:55:37 fedora systemd[1]: Stopped systemd-resolved.service - Network Name Resolution.
oct. 12 18:55:37 fedora systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
oct. 12 18:55:37 fedora systemd-resolved[957]: Positive Trust Anchors:
oct. 12 18:55:37 fedora systemd-resolved[957]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
oct. 12 18:55:37 fedora systemd-resolved[957]: Negative trust anchors: home.arpa 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
oct. 12 18:55:37 fedora systemd-resolved[957]: Using system hostname 'fedora'.
oct. 12 18:55:37 fedora systemd-resolved[957]: Failed to connect to system bus: Permission denied
oct. 12 18:55:37 fedora systemd-resolved[957]: Could not create manager: Permission denied
oct. 12 18:55:37 fedora systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
oct. 12 18:55:37 fedora systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
oct. 12 18:55:37 fedora systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
oct. 12 18:55:38 fedora systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 2.
oct. 12 18:55:38 fedora systemd[1]: Stopped systemd-resolved.service - Network Name Resolution.
oct. 12 18:55:38 fedora systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
oct. 12 18:55:38 fedora systemd-resolved[961]: Positive Trust Anchors:
oct. 12 18:55:38 fedora systemd-resolved[961]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
oct. 12 18:55:38 fedora systemd-resolved[961]: Negative trust anchors: home.arpa 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
oct. 12 18:55:38 fedora systemd-resolved[961]: Using system hostname 'fedora'.
oct. 12 18:55:38 fedora systemd-resolved[961]: Failed to connect to system bus: Permission denied
oct. 12 18:55:38 fedora systemd-resolved[961]: Could not create manager: Permission denied
oct. 12 18:55:38 fedora systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
oct. 12 18:55:38 fedora systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
oct. 12 18:55:38 fedora systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
oct. 12 18:55:38 fedora systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 3.
oct. 12 18:55:38 fedora systemd[1]: Stopped systemd-resolved.service - Network Name Resolution.
oct. 12 18:55:38 fedora systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
oct. 12 18:55:38 fedora systemd-resolved[965]: Positive Trust Anchors:
oct. 12 18:55:38 fedora systemd-resolved[965]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
oct. 12 18:55:38 fedora systemd-resolved[965]: Negative trust anchors: home.arpa 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
oct. 12 18:55:38 fedora systemd-resolved[965]: Using system hostname 'fedora'.
oct. 12 18:55:38 fedora systemd-resolved[965]: Failed to connect to system bus: Permission denied
oct. 12 18:55:38 fedora systemd-resolved[965]: Could not create manager: Permission denied
oct. 12 18:55:38 fedora systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
oct. 12 18:55:38 fedora systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
oct. 12 18:55:38 fedora systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
oct. 12 18:55:38 fedora systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 4.
oct. 12 18:55:38 fedora systemd[1]: Stopped systemd-resolved.service - Network Name Resolution.
oct. 12 18:55:38 fedora systemd[1]: Starting systemd-resolved.service - Network Name Resolution...
oct. 12 18:55:38 fedora systemd-resolved[969]: Positive Trust Anchors:
oct. 12 18:55:38 fedora systemd-resolved[969]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
oct. 12 18:55:38 fedora systemd-resolved[969]: Negative trust anchors: home.arpa 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
oct. 12 18:55:38 fedora systemd-resolved[969]: Using system hostname 'fedora'.
oct. 12 18:55:38 fedora systemd-resolved[969]: Failed to connect to system bus: Permission denied
oct. 12 18:55:38 fedora systemd-resolved[969]: Could not create manager: Permission denied
oct. 12 18:55:38 fedora systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
oct. 12 18:55:38 fedora systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
oct. 12 18:55:38 fedora systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
oct. 12 18:55:38 fedora systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5.
oct. 12 18:55:38 fedora systemd[1]: Stopped systemd-resolved.service - Network Name Resolution.
oct. 12 18:55:38 fedora systemd[1]: systemd-resolved.service: Start request repeated too quickly.
oct. 12 18:55:38 fedora systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
oct. 12 18:55:38 fedora systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
oct. 12 18:55:42 fedora systemd[1]: systemd-resolved.service: Start request repeated too quickly.
oct. 12 18:55:42 fedora systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
oct. 12 18:55:42 fedora systemd[1]: Failed to start systemd-resolved.service - Network Name Resolution.
1 Like
I ran:
sudo fixfiles onboot
and it solved the problem, thanks you 
1 Like