Selfhosted
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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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!
view the rest of the comments
The issue fixes after the restart command but when I reboot it cimes back.
'ls -lh /etc/resolv*' spits out:
lrwxrwxrwx 1 root root 37 Mar 11 16:48 /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf
I really think you have conflicting resolvers running on startup, which would explain this. Double check your systemd units that are enabled on boot. If you don't see anything like networkmanager, reboot the machine, get the status of systemd-resolv to make sure it's actually running after a fresh boot, check the logs and see if you see anything interesting there, then restart it and check the logs again once DNS works. Something is different between those two actions.