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
How exactly are you testing this from your client, with ping? What are you using to query the DNS?
If you run nslookup from the client
I’m assuming you’ve run ifconfig to verify your client’s NIC has been assigned the correct DNS via DHCP?
Thanks for replying, I appreciate the response.
I’m running
dig @192.168.0.249 study.lan
from my client (a MacBook).If I run ‘dig @192.168.0.249 study.lan TXT’ I get a correct response (I have added a txt record)
If I run ‘dig @192.168.0.249 lan SOA’ or ‘NS’ I correctly get the records for the zone.
I think this eliminates the possibility of it being a routing error?