Fedora 43 webpages randomly do not open

Ask Fedora
1

It is already few months that I fresh-installed Fedora 43 on my Desktop.
I have another laptop on which ubuntu is installed. Both computers are connected to the same internet box via cable. I use Chrome and Firefox as internet browser on both machines.

I recently noticed that some random websites (stackexchange, imdb etc.) which I had opened earlier on my fedora, do not show up anymore, saying : " This site can’t be reached"
When I check it on ubuntu, I can open both pages. What could be the issue?

I also tried switching the box off and on. Problem remains.

2

When this issue occurs, can you resolve the FQDN in DNS on the machine in question.

I would suspect it’s a DNS issue - you probably want to double-check that both machines are configured to both resolve DNS via the same upstream DNS.

3

What is the output of resolvectl?
As @anothermindbomb suggested do a look of the failing dns name using resolvectl query NAME to check how the NAME is resolved.

4 
systemctl status systemd-resolved
resolvectl status
5 
sina@sinooshka:/etc/NetworkManager$ systemctl status systemd-resolved
● 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 Tue 2026-06-02 16:36:52 CEST; 3h 55min ago
 Invocation: c91fce5fe15c4f01896d48c1bdba4f48
TriggeredBy: ● systemd-resolved-varlink.socket
             ● systemd-resolved-monitor.socket
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS
             https://systemd.io/WRITING_RESOLVER_CLIENTS
   Main PID: 7087 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 18930)
     Memory: 4.9M (peak: 5.9M)
        CPU: 2.710s
     CGroup: /system.slice/systemd-resolved.service
             └─7087 /usr/lib/systemd/systemd-resolved

Jun 02 17:21:00 sinooshka systemd-resolved[7087]: enp3s0: Bus client reset DNS server list.
Jun 02 17:21:06 sinooshka systemd-resolved[7087]: enp3s0: Bus client set default route setting: yes
Jun 02 17:21:06 sinooshka systemd-resolved[7087]: enp3s0: Bus client set DNS server list to: fd0f:ee:b0::1
Jun 02 19:04:56 sinooshka systemd-resolved[7087]: enp3s0: Bus client set default route setting: no
Jun 02 19:04:56 sinooshka systemd-resolved[7087]: enp3s0: Bus client reset DNS server list.
Jun 02 20:29:23 sinooshka systemd-resolved[7087]: Clock change detected. Flushing caches.
Jun 02 20:29:23 sinooshka systemd-resolved[7087]: Closing all remaining TCP connections.
Jun 02 20:29:23 sinooshka systemd-resolved[7087]: Resetting learnt feature levels on all servers.
Jun 02 20:29:28 sinooshka systemd-resolved[7087]: enp3s0: Bus client set default route setting: yes
Jun 02 20:29:28 sinooshka systemd-resolved[7087]: enp3s0: Bus client set DNS server list to: fd0f:ee:b0::1
6 
sina@sinooshka:/etc/NetworkManager$ resolvectl status
Global
         Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
  resolv.conf mode: stub

Link 2 (enp3s0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: fd0f:ee:b0::1
       DNS Servers: fd0f:ee:b0::1
     Default Route: yes
7

how do they compare with the Ubuntu machine which apparently always works? Are they configured the same way?

By the way, posting in

preformatted text

makes things a LOT easier to read by the way. At least you didn’t post screenshots of plain text.

9

Sorry for my forgetfulness! I edited the output of the commands with preformatted text :slight_smile:

Please find bellow the result of the same two commands on my “ubuntu” machine (there are a number of differences between the configurations in two machines):

● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
     Active: active (running) since Mon 2026-05-25 15:50:01 CEST; 1 week 1 day 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: 1552 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 18949)
     Memory: 8.9M (peak: 9.9M)
        CPU: 12.383s
     CGroup: /system.slice/systemd-resolved.service
             └─1552 /usr/lib/systemd/systemd-resolved

juin 02 19:01:45 Rostam systemd-resolved[1552]: enp4s0: Bus client set default route setting: no
juin 02 19:01:45 Rostam systemd-resolved[1552]: enp4s0: Bus client reset DNS server list.
juin 02 19:01:45 Rostam systemd-resolved[1552]: wlp3s0: Bus client set default route setting: no
juin 02 19:01:45 Rostam systemd-resolved[1552]: wlp3s0: Bus client reset DNS server list.
juin 02 21:06:48 Rostam systemd-resolved[1552]: Clock change detected. Flushing caches.
juin 02 21:06:52 Rostam systemd-resolved[1552]: enp4s0: Bus client set default route setting: yes
juin 02 21:06:52 Rostam systemd-resolved[1552]: enp4s0: Bus client set DNS server list to: fd0f:ee:b0::1
juin 02 21:06:54 Rostam systemd-resolved[1552]: wlp3s0: Bus client set default route setting: yes
juin 02 21:06:54 Rostam systemd-resolved[1552]: wlp3s0: Bus client set DNS server list to: 192.168.1.254
juin 02 21:06:56 Rostam systemd-resolved[1552]: wlp3s0: Bus client set DNS server list to: 192.168.1.254, fd0f:ee:b0::1

And

(base) sina@Rostam:~$ resolvectl status
Global
         Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
  resolv.conf mode: stub

Link 2 (enp4s0)
    Current Scopes: DNS
         Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: fd0f:ee:b0::1
       DNS Servers: fd0f:ee:b0::1

Link 3 (wlp3s0)
    Current Scopes: DNS
         Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.254
       DNS Servers: 192.168.1.254 fd0f:ee:b0::1
10

Your Fedora machine only uses IPv6 for it’s upstream DNS resolver.

Your Ubuntu machine uses both IPv6 and IPv4 for it’s upstream DNS resolver.

Other than that they both look perfectly OK to me.

11

Thanks a lot for your comment. I need to go through the points you mentioned and become familiar with the whole DNS and network configuration topic :slight_smile:

12

Next time this happens on the Fedora machine, pop open a terminal and run a quick resolvectl query google.com && ping fd0f:ee:b0::1

If it fails, then your DNS server is dropping out… or at least the IPv6 aspect of it is.

It shouldn’t hurt to add the IPv4 address to the Fedora box anyway; gives a little fallback which might be all you need.

13

Thanks a lot. Lots of useful hints and info. I need to go through them one by one :slight_smile:

14

Are you using NetworkManager on both systems?
If so compare how your network connects are configured.