© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
BazziteB
Bazzite•4w ago•
5 replies
Supernova

Internet/DNS issues with systemd-resolved.service

questionbug
At random times, my internet would stop working. This happened regardless of ethernet or wifi, and would happen on different bazzite versions i would rollback to. The duration could be a few seconds, or long enough for the system to show "no internet" in the system tray. The immediate solution I follow is to open the networks tab in the tray and click disconnect/reconnect while waiting a few seconds to see if the internet returned.

These are the logs that are emitted during the times of no internet:
19:15:48.790 UTC systemd-resolved.service Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.1.1.
19:39:08.562 UTC systemd-resolved.service Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.1.1.
19:39:13.812 UTC systemd-resolved.service Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1.
19:39:34.312 UTC systemd-resolved.service Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1.
19:39:39.562 UTC systemd-resolved.service Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1.
19:40:00.062 UTC systemd-resolved.service Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1.
19:40:05.312 UTC systemd-resolved.service Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1.
19:40:25.812 UTC systemd-resolved.service Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1.
19:40:31.777 UTC systemd-resolved.service Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.1.1.
19:15:48.790 UTC systemd-resolved.service Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.1.1.
19:39:08.562 UTC systemd-resolved.service Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.1.1.
19:39:13.812 UTC systemd-resolved.service Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1.
19:39:34.312 UTC systemd-resolved.service Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1.
19:39:39.562 UTC systemd-resolved.service Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1.
19:40:00.062 UTC systemd-resolved.service Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1.
19:40:05.312 UTC systemd-resolved.service Using degraded feature set TCP instead of UDP for DNS server 192.168.1.1.
19:40:25.812 UTC systemd-resolved.service Using degraded feature set UDP instead of TCP for DNS server 192.168.1.1.
19:40:31.777 UTC systemd-resolved.service Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.1.1.


It seems this has been recorded before on long thread at https://github.com/systemd/systemd/issues/13432, but it is "Closed as not planned".

I am curious if anyone has a solution to this? From the thread above, It seems tied to fedora, which is what Bazzite is tied to.

i am on:
bazzite:stable
Linux 6.17.7-ba22.fc43.x86_64
BazziteJoin
The operating system for the next generation of gamers.
29,482Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

systemd-resolved.service/start hangs
BazziteBBazzite / 🛟bazzite-help
6mo ago
Issue with systemd service not running at boot.
BazziteBBazzite / 🛟bazzite-help
9mo ago
systemd-boot with bazzite?
BazziteBBazzite / 🛟bazzite-help
16mo ago
internet issues rog ally
BazziteBBazzite / 🛟bazzite-help
4d ago