I frequently have issues connecting to various internet resources, but it’s extremely random and intermittent. One minute, I couldn’t even load the KDE forums homepage, the next I could. This isn’t limited to the browser either; sometimes even built-in apps like Discover can’t seem to connect. No other device on my network has this problem, and I’m hard-wired all the way, so it’s not a wifi signal issue. Even on this same device, when I dual boot into Windows, it works perfectly. But trying to connect to any internet resource from any app in Fedora 42 KDE Plasma is a total crapshoot.
When I first installed the OS, this happened rarely, but it seems to be becoming more and more common now. Rebooting (the PC, the network adapter, the router, the modem) doesn’t seem to help.
Using the System Monitor doesn’t reveal any kind of resource hog or anything else particularly suspicious.
What is my next troubleshooting step? Is there something else I can profile or monitor to identify the issue?
@LIngenthron:
First, welcome to the KDE Discuss forum.
First thing to check – ‘/etc/resolv.conf’ – it should be a symbolic link –
> file /etc/resolv.conf
/etc/resolv.conf: symbolic link to /run/netconfig/resolv.conf
>
> cat /run/netconfig/resolv.conf
### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
# NETCONFIG_DNS_STATIC_SEARCHLIST
# NETCONFIG_DNS_STATIC_SERVERS
# NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
# NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
search fritz.box
nameserver 192.168.178.1
nameserver fda5:b1e5:3a56:0:62b5:8dff:fefe:ca0e
nameserver 2001:9e8:ab66:fd00:62b5:8dff:fefe:ca0e
>
Does your Router supply your system’s LAN IP address and DNS routing information via DHCP?
If you login to your Router, is your Fedora system visible on the LAN?
Can you “ping” your Router?
Can you “ping” your ISP?
Can you “ping” this forum?
> LANG=C:UTF-8 ping fritz.box
PING fritz.box (fda5:b1e5:3a56:0:62b5:8dff:fefe:ca0e) 56 data bytes
64 bytes from fritz.box (fda5:b1e5:3a56:0:62b5:8dff:fefe:ca0e): icmp_seq=1 ttl=64 time=0.297 ms
64 bytes from fritz.box (fda5:b1e5:3a56:0:62b5:8dff:fefe:ca0e): icmp_seq=2 ttl=64 time=0.346 ms
64 bytes from fritz.box (fda5:b1e5:3a56:0:62b5:8dff:fefe:ca0e): icmp_seq=3 ttl=64 time=0.312 ms
64 bytes from fritz.box (fda5:b1e5:3a56:0:62b5:8dff:fefe:ca0e): icmp_seq=4 ttl=64 time=0.317 ms
64 bytes from fritz.box (fda5:b1e5:3a56:0:62b5:8dff:fefe:ca0e): icmp_seq=5 ttl=64 time=0.327 ms
^C
--- fritz.box ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4087ms
rtt min/avg/max/mdev = 0.297/0.319/0.346/0.016 ms
>
> LANG=C:UTF-8 ping 1und1.de
PING 1und1.de (2001:8d8:5ff:7::1:3) 56 data bytes
64 bytes from www.1und1.de (2001:8d8:5ff:7::1:3): icmp_seq=1 ttl=59 time=8.51 ms
64 bytes from www.1und1.de (2001:8d8:5ff:7::1:3): icmp_seq=2 ttl=59 time=9.01 ms
64 bytes from www.1und1.de (2001:8d8:5ff:7::1:3): icmp_seq=3 ttl=59 time=8.85 ms
64 bytes from www.1und1.de (2001:8d8:5ff:7::1:3): icmp_seq=4 ttl=59 time=8.71 ms
64 bytes from www.1und1.de (2001:8d8:5ff:7::1:3): icmp_seq=5 ttl=59 time=8.93 ms
^C
--- 1und1.de ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 8.505/8.800/9.013/0.178 ms
>
> LANG=C:UTF-8 ping discuss.kde.org
PING discuss.kde.org (2a03:b0c0:3:d0::22b:6001) 56 data bytes
64 bytes from cinclo.kde.org (2a03:b0c0:3:d0::22b:6001): icmp_seq=1 ttl=55 time=11.8 ms
64 bytes from cinclo.kde.org (2a03:b0c0:3:d0::22b:6001): icmp_seq=2 ttl=55 time=9.12 ms
64 bytes from cinclo.kde.org (2a03:b0c0:3:d0::22b:6001): icmp_seq=3 ttl=55 time=8.92 ms
64 bytes from cinclo.kde.org (2a03:b0c0:3:d0::22b:6001): icmp_seq=4 ttl=55 time=9.01 ms
64 bytes from cinclo.kde.org (2a03:b0c0:3:d0::22b:6001): icmp_seq=5 ttl=55 time=9.56 ms
64 bytes from cinclo.kde.org (2a03:b0c0:3:d0::22b:6001): icmp_seq=6 ttl=55 time=8.55 ms
^C
--- discuss.kde.org ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5008ms
rtt min/avg/max/mdev = 8.549/9.494/11.811/1.077 ms
>
Here’s mine on Fedora 42 KDE if it helps:
$ file /etc/resolv.conf
/etc/resolv.conf: symbolic link to ../run/systemd/resolve/stub-resolv.conf
$ cat /etc/resolv.conf
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0 trust-ad
search .
Other information that would be useful:
- kernel version
- what’s the networking hardware on your PC? If it’s the built-in port on the motherboard, what model of motherboard?
Thanks for the response.
My resolve file setup is exactly the same as what pg-tips posted in a subsequent reply.
My router does supply an IP address via DHCP, not sure about if it provides DNS as well. But every other device on this router has no problems.
My fedora system is visible on the router’s client list.
I am able to ping all three. Right now, the internet is working fine. This issue only happens intermittently, and I have yet to find a common cause. When it does happen, it also seems to happen for random sites/endpoints, but never all sites.
I do believe the problem is ultimately somewhere in the DNS process, but I haven’t been able to isolate exactly where that’s failing, and the random nature of the problem makes that twice as hard to track down.