PC can't resolve internet addresses after boot. Need to restart NetworkManager

[mojth (Thomas Moj)]

Hi everyone,

I’m having an issue with my network connection. Every time I reboot, I can’t resolve internet addresses. I can access other computers in the local network via hostname and IP address. I can access the internet via IP address, but not using domain names. Restarting the NetworkManager service resolves the issue, but only until I reboot the PC.

I’ve already tried the following steps:

• Checked /etc/resolv.conf. There is no DNS configured. But since restarting the NetworkManager solves the issue temporarily I don’t think the config is worng.

• Checked the systemd journal for any errors related to NetworkManager. There were no error messages. I attached it anyway, maybe I missed something.

• Restarted the NetworkManager service and even reinstalled the package

I’ve found some related post, but they didn’t help:

Dns problem in fedora server due to resolvectl

Hi, At Each reboot from my fedora server 34 the same story occurs since a recent update I m getting this : Global Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (enp5s0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 3 (bridge0) Current Scopes: none Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported DNS Servers: 192.168.5.10 192.168.5.2 Failed to get l…

The solution was a kernel update, but this was to years ago.

No DNS after updating network manager

Hi everyone, Today I got an update via dnfdragora of network manager and since a reboot I have no name resolution anymore. I checked another user’s issue here: Connected with wifi but no Internet after F37 upgrade but could not figure out, if this is another issue or a similar one. I have an ip address and can connect to other computers in the same network and the router by entering the target ip address, but not with a hostname. This behavior prevents me from connecting to the internet. I t…

The user has had a wrong DNS config. But since restarting NetworkManager solves the issue without changing any configs, I’m pretty sure, my configs are fine.

I’m not sure what else to try. Do you have any suggestions?

Thanks in advance for your help.

journalctl -u NetworkManager

-- Boot eddc129ba9374f3abda75e2231f23b68 --
Feb 20 09:55:28 pc systemd[1]: Starting NetworkManager.service - Network Manager...
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5521] NetworkManager (version 1.40.10-1.fc37) is starting... (boot:eddc129b-a937-4f3a-bda7-5e2231f23b68)
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5523] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf) (run: 15-carrier-timeout.conf)
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5530] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Feb 20 09:55:28 pc systemd[1]: Started NetworkManager.service - Network Manager.
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5542] manager[0x56288c601030]: monitoring kernel firmware directory '/lib/firmware'.
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5796] hostname: hostname: using hostnamed
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5796] hostname: static hostname changed from (none) to "pc"
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5798] dns-mgr: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5826] manager[0x56288c601030]: rfkill: Wi-Fi hardware radio set enabled
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5826] manager[0x56288c601030]: rfkill: WWAN hardware radio set enabled
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5861] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.40.10-1.fc37/libnm-device-plugin-bluetooth.so)
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5866] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.40.10-1.fc37/libnm-device-plugin-adsl.so)
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5877] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.40.10-1.fc37/libnm-device-plugin-team.so)
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5885] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.40.10-1.fc37/libnm-device-plugin-wifi.so)
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5888] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.40.10-1.fc37/libnm-device-plugin-wwan.so)
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5889] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5889] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5890] manager: Networking is enabled by state file
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5892] settings: Loaded settings plugin: keyfile (internal)
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5899] dhcp: init: Using DHCP client 'internal'
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5899] device (lo): carrier: link connected
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5901] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5905] manager: (enp4s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.5907] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Feb 20 09:55:28 pc NetworkManager[1083]: <info>  [1676883328.7738] modem-manager: ModemManager available
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.3707] device (enp4s0): carrier: link connected
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.3710] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.3715] policy: auto-activating connection 'Profil 1' (16c79651-3a1b-429e-aacf-822277a616b3)
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.3719] device (enp4s0): Activation: starting connection 'Profil 1' (16c79651-3a1b-429e-aacf-822277a616b3)
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.3720] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.3721] manager: NetworkManager state is now CONNECTING
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.3722] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.3973] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.3977] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.4422] dhcp4 (enp4s0): state changed new lease, address=192.168.0.6
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.4424] policy: set 'Profil 1' (enp4s0) as default for IPv4 routing and DNS
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.4606] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.4612] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.4613] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.4614] manager: NetworkManager state is now CONNECTED_SITE
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.4615] device (enp4s0): Activation: successful, device activated.
Feb 20 09:55:32 pc NetworkManager[1083]: <info>  [1676883332.4617] manager: startup complete
Feb 20 09:55:33 pc NetworkManager[1083]: <info>  [1676883333.8935] agent-manager: agent[f7888fa8b584d4f5,:1.33/org.gnome.Shell.NetworkAgent/42]: agent registered
Feb 20 09:55:33 pc NetworkManager[1083]: <info>  [1676883333.9703] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Feb 20 09:55:33 pc NetworkManager[1083]: <info>  [1676883333.9707] policy: set 'Profil 1' (enp4s0) as default for IPv6 routing and DNS
Feb 20 09:55:33 pc NetworkManager[1083]: <info>  [1676883333.9933] dhcp6 (enp4s0): state changed new lease
Feb 20 09:56:33 pc NetworkManager[1083]: <info>  [1676883393.0755] agent-manager: agent[09e05382aa2704ff,:1.81/org.gnome.Shell.NetworkAgent/1000]: agent registered
Feb 20 10:14:55 pc systemd[1]: Stopping NetworkManager.service - Network Manager...
Feb 20 10:14:55 pc NetworkManager[1083]: <info>  [1676884495.2605] caught SIGTERM, shutting down normally.
Feb 20 10:14:55 pc NetworkManager[1083]: <info>  [1676884495.2693] dhcp4 (enp4s0): canceled DHCP transaction
Feb 20 10:14:55 pc NetworkManager[1083]: <info>  [1676884495.2693] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Feb 20 10:14:55 pc NetworkManager[1083]: <info>  [1676884495.2693] dhcp4 (enp4s0): state changed no lease
Feb 20 10:14:55 pc NetworkManager[1083]: <info>  [1676884495.2694] dhcp6 (enp4s0): canceled DHCP transaction
Feb 20 10:14:55 pc NetworkManager[1083]: <info>  [1676884495.2694] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Feb 20 10:14:55 pc NetworkManager[1083]: <info>  [1676884495.2694] dhcp6 (enp4s0): state changed no lease
Feb 20 10:14:55 pc NetworkManager[1083]: <info>  [1676884495.2726] exiting (success)
Feb 20 10:14:55 pc systemd[1]: NetworkManager.service: Deactivated successfully.
Feb 20 10:14:55 pc systemd[1]: Stopped NetworkManager.service - Network Manager.
Feb 20 10:14:55 pc systemd[1]: Starting NetworkManager.service - Network Manager...
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3156] NetworkManager (version 1.40.10-1.fc37) is starting... (after a restart, boot:eddc129b-a937-4f3a-bda7-5e2231f23b68)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3156] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf) (run: 15-carrier-timeout.conf)
Feb 20 10:14:55 pc systemd[1]: Started NetworkManager.service - Network Manager.
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3162] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3175] manager[0x556430af6050]: monitoring kernel firmware directory '/lib/firmware'.
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3428] hostname: hostname: using hostnamed
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3428] hostname: static hostname changed from (none) to "pc"
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3430] dns-mgr: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3432] manager[0x556430af6050]: rfkill: Wi-Fi hardware radio set enabled
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3432] manager[0x556430af6050]: rfkill: WWAN hardware radio set enabled
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3446] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.40.10-1.fc37/libnm-device-plugin-bluetooth.so)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3447] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.40.10-1.fc37/libnm-device-plugin-adsl.so)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3451] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.40.10-1.fc37/libnm-device-plugin-team.so)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3453] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.40.10-1.fc37/libnm-device-plugin-wifi.so)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3454] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.40.10-1.fc37/libnm-device-plugin-wwan.so)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3455] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3455] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3456] manager: Networking is enabled by state file
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3457] settings: Loaded settings plugin: keyfile (internal)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3466] dhcp: init: Using DHCP client 'internal'
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3466] device (lo): carrier: link connected
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3467] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3471] device (enp4s0): carrier: link connected
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3473] manager: (enp4s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3476] manager: (enp4s0): assume: will attempt to assume matching connection 'Profil 1' (16c79651-3a1b-429e-aacf-822277a616b3) (indicated)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3476] device (enp4s0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'assume')
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3480] device (enp4s0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'assume')
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3485] device (enp4s0): Activation: starting connection 'Profil 1' (16c79651-3a1b-429e-aacf-822277a616b3)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3513] modem-manager: ModemManager available
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3514] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'assume')
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3515] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'assume')
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.3665] agent-manager: agent[ee04a1f8eeddf5c6,:1.81/org.gnome.Shell.NetworkAgent/1000]: agent registered
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.4790] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'assume')
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.4793] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.5202] dhcp4 (enp4s0): state changed new lease, address=192.168.0.6
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.5204] policy: set 'Profil 1' (enp4s0) as default for IPv4 routing and DNS
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.5667] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'assume')
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.5674] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'assume')
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.5674] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'assume')
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.5676] manager: NetworkManager state is now CONNECTED_SITE
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.5677] device (enp4s0): Activation: successful, device activated.
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.5679] manager: startup complete
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.6415] dhcp6 (enp4s0): activation: beginning transaction (timeout in 45 seconds)
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.6418] policy: set 'Profil 1' (enp4s0) as default for IPv6 routing and DNS
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.8092] dhcp6 (enp4s0): state changed new lease
Feb 20 10:14:55 pc NetworkManager[4105]: <info>  [1676884495.8374] manager: NetworkManager state is now CONNECTED_GLOBAL

nmcli

enp4s0: verbunden to Profil 1
	"Realtek RTL8111/8168/8411"
	ethernet (r8169), D8:5E:D3:A4:4A:E8, hw, mtu 1500
	ip4-Vorgabe, ip6-Vorgabe
	inet4 192.168.0.6/24
	route4 192.168.0.0/24 metric 100
	route4 default via 192.168.0.1 metric 20100
	inet6 2001:4dd2:5581:0:60a:a970:ea42:a89f/64
	inet6 fe80::683b:475c:ea8f:ee96/64
	route6 fe80::/64 metric 1024
	route6 2001:4dd2:5581::/64 metric 100
	route6 default via fe80::2e99:24ff:fe85:2840 metric 20100

lo: nicht verwaltet
	"lo"
	loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
	servers: 81.173.194.68 213.168.112.60
	interface: enp4s0

	servers: 2001:4dd0:100:1020:53:2:0:1 2001:4dd0:100:4220:53:2:0:4
	interface: enp4s0

/etc/resolv.conf

nameserver 127.0.0.53
options edns0 trust-ad
search .

uname -r

6.1.11-200.fc37.x86_64

[vgaetera (Vladislav Grigoryev)]

Looks like a similar issue, solved here:
https://discussion.fedoraproject.org/t/fedora-37-workstation-cant-connect-internet-after-first-boot-login/64299/3

[mojth (Thomas Moj)]

Thanks for helping me.
I’ve looked at the post and the marked solution
I’ve set up a public DNS provider and enabled DNSOverTLS as you suggested here:
https://discussion.fedoraproject.org/t/dns-resolution-broken/67067/2
Sadly it didn’t work.
I still need to restart NetworkManager after every reboot to resolve domains.

[vgaetera (Vladislav Grigoryev)]

When the issue happens, collect the output:

resolvectl status --no-pager
resolvectl query discussion.fedoraproject.org
nslookup discussion.fedoraproject.org 8.8.8.8
nslookup discussion.fedoraproject.org 1.1.1.1

[mojth (Thomas Moj)]

Thanks again for helping me.

here is the output:
resolvectl status --no-pager

Global
       Protocols: LLMNR=resolve -mDNS +DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (enp4s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
     Protocols: +DefaultRoute +LLMNR -mDNS +DNSOverTLS DNSSEC=no/unsupported
   DNS Servers: 8.8.8.8 8.8.4.4

resolvectl query discussion.fedoraproject.org

discussion.fedoraproject.org: 64.71.144.209           -- link: enp4s0
                       2602:fd3f:3:ff01::d1    -- link: enp4s0
                       (askfedora.hosted-by-discourse.com)

-- Information acquired via protocol DNS in 119.6ms.
-- Data is authenticated: no; Data was acquired via local or encrypted transport: yes
-- Data from: network

nslookup discussion.fedoraproject.org 8.8.8.8

Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
discussion.fedoraproject.org	canonical name = askfedora.hosted-by-discourse.com.
Name:	askfedora.hosted-by-discourse.com
Address: 64.71.144.209
Name:	askfedora.hosted-by-discourse.com
Address: 2602:fd3f:3:ff01::d1

nslookup discussion.fedoraproject.org 1.1.1.1

Server:		1.1.1.1
Address:	1.1.1.1#53

Non-authoritative answer:
discussion.fedoraproject.org	canonical name = askfedora.hosted-by-discourse.com.
Name:	askfedora.hosted-by-discourse.com
Address: 64.71.144.209
Name:	askfedora.hosted-by-discourse.com
Address: 2602:fd3f:3:ff01::d1

After restarting the NetworManager the output of resolvectl status --no-pager changes to:

Global
       Protocols: LLMNR=resolve -mDNS +DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (enp4s0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS +DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 8.8.8.8
       DNS Servers: 8.8.8.8 8.8.4.4

Sorry I don’t know how to highlight the Change in a code Block, the line “Current DNS Server: 8.8.8.8” is new after restarting the NetworkManager.

— Edit —

I just noticed running “resolvectl query discussion.fedoraproject.org” seems to also solve the issue until the next reboot… strange

[vgaetera (Vladislav Grigoryev)]

Since your connection is running in dual-stack mode, I recommend setting up IPv6 DNS as well:

sudo nmcli connection modify id CON_NAME \
    ipv6.dns 2001:4860:4860::8888,2001:4860:4860::8844

If the issue persists, collect the diagnostics:

# Check the repos
sudo dnf repolist

# Confirm the system is fully upgraded
sudo dnf upgrade --refresh

# Fix SELinux labels
sudo restorecon -F -R -T 0 /

# Check service statuses
systemctl status NetworkManager.service systemd-resolved.service

# Check configs
ls -l /etc/resolv.conf
grep -r -v -e "^#" -e "^$" /etc/nsswitch.conf /etc/systemd/resolved.conf*
grep -r -v -e "^#" -e "^$" /etc/NetworkManager/{conf.d/,}*.conf

You can post the output to paste.centos.org if it’s too large.

[mojth (Thomas Moj)]

adding the ipv6 DNS didn’t help.

sudo dnf upgrade --refresh

There were 4 Updates:

  gjs-1.74.1-7.fc37.x86_64             mozjs102-102.8.0-1.fc37.x86_64          
  xen-libs-4.16.3-2.fc37.x86_64        xen-licenses-4.16.3-2.fc37.x86_64 

after I installed them I ran

sudo restorecon -F -R -T 0 /

which gave me two errors, but did something judging from the time it took

restorecon: Could not stat /run/user/1000/doc: Permission denied.
restorecon: Could not stat /run/user/1000/gvfs: Permission denied.

After that I rebooted to reproduce the issue, so that I could get service states, but the problem no longer occurred.
So I’m not sure what did it, the update or restorecon.
Anyway it works now. Thank you for all the help.