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
Okay, no external software for DNS management present here. Is that ip a working DNS Server? Is it your server itself perhaps?
192.168.68.210 is my adguard, it's on a different machine. It should be working, all my other devices use it and I can see the traffic going through it. My servers IP is 192.168.68.120, and I can't see traffic from that on my adguard at all. But it can ping my adguard.
Okay, so if that's your actual DNS Server, can you confirm that it works?
dig @yourdns debian.org
, for example. Afterwards try to use the default DNS of your systemdig debian.org
. If both works, your DNS config should be fine. Try acurl debian.org -v
too.debian.org is just a random domain for this, use whatever you want. I don't see anything badly configured so far.
as far as i can tell from the output, i think my DNS is working?