20
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Oct 2024
20 points (88.5% liked)
Selfhosted
40347 readers
286 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: 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!
founded 1 year ago
MODERATORS
Do you have any idea on how to do it ? Knowing that I am on opensuse
Well, on linux I'd use systemd's resolved which would listen on localhost:53 (it would also point resolv.conf there) and then set resolved's uplink server to your custom port. I don't have the exact config in mind but it seems to support custom uplink ports("expects IPv4 or IPv6 address specifications of DNS servers [...] optionally take a port number separated with ":"[...]")
Edit: found this: https://en.opensuse.org/Network_Management_With_Systemd