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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
As a temporary fix, instead of service systemd-resolved restart as per the article, you can try this, service systemd-resolved stop
Once the service is stopped the port should be free. You'll have to do this on every reboot (though maybe you can try adding the command to /etc/rc.local to stop it on every reboot)
The service is using the default config, which you can override by creating this file.
View the package contents to find out where the default config is located.
Yep, it might be enough to just add that file with the setting set to no and restart.
Here is a good primer on the configuration files and their possible locations: https://www.freedesktop.org/software/systemd/man/latest/resolved.conf.html
Edit: be careful because this is your domain name lookup you’re messing with. 😊
The domain name shouldn't matter
FWIW, I’m referring to the local DNS (domain name system) resolver; the mechanism that resolves local domain names into IP addresses so that computers can talk to each other over the LAN.
I know
It still won't really matter. The domain name is arbitrary in this case
Disable systemd-resolved.service? Uninstall systemd-resolved?
Um, dnf doesn't do anything with configuration files. It is used for packages.
I would start by trying to create that file. If that doesn't fix it after restarting the service look into the docs. You may need to configure network manager.
It tries to install the associated package when given a path to a configuration file.
They probably moved it to somewhere under /usr or /var/lib.
When I installed it it suggested turning that service off onvthe host. If you search online there are many suggestions on shutting off that stuff so 53 is left for pihole