this post was submitted on 11 Mar 2025
45 points (86.9% liked)
Selfhosted
60281 readers
617 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Have you tried deleting
/etc/systemd/resolved.confand restarting the service withsystemctl restart systemd-resolved?Ok wtf. I retried this solution and it worked for some reason. I have no idea what happened differently. I didn't delete the file because it was already gone.
However if I restart it breaks again.
I found an informative post about a related issue that might be of some use to you. Sounds like DHCP or Network Manager may be rewriting your systems-resolved.conf.
https://joshrnoll.com/my-tailscale-dns-woes/
That did not work, I deleted the file and then I restarted the service. I then restarted the pc just to make sure. Still no internet access and still same limited connectivity error.
What's the config file look like?
https://wiki.archlinux.org/title/Systemd-resolved
None of those config files exist in that folder location.