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
I don't know what your previous setup was, but given that running resolved fixes your DNS issues, run:
ln -sf ../run/systemd/resolve/stub-resolv.conf /etc/resolv.confThis will point programs that use /etc/resolved.conf during DNS resolution to the local DNS server provided by systemd-resolved.
Then, enable resolved so that it is started when you reboot:
systemctl enable systemd-resolved.serviceFinally, start the service so that it is available immediately:
systemctl start systemd-resolved.serviceYou will want it run those with the required permissions, e. g. via sudo.
"It's always DNS"
This seems to have fixed it!! Thank you so much!