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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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
Kinda overlapping other replies, but to answer your question: A = your external IPv4 address
The rest could be empty AAAA = an external IPv6 address NS = a DNS server MX = Mail Server
TXT is just text, but it can be used by, ie Lets Encrypt to prove you own that domain for your SSL certificate
If you open TCP 80 / 443 on the open internet EVERYONE will probe you, but you want to run a Friendica server, so you kinda need that (disclaimer: I do not know how Friendica is setup)
So, you'll need something (firewall, Fail2Ban, etc) to protect your server whilst also allowing it to federate to other servers.
I'd strongely suggest you put your server on a VPS with a provider that has some level of defense already setup for you.
I wouldn't run this in your home network with putting it into a DMZ of some kind.
If you're not using a domain for email, the MX record should not be left empty, as it can still be used maliciously.
Following a guide like this (it's one of many) will ensure it's not used at all:
https://www.mailhardener.com/kb/hardening-unused-domains
Should probably note that "DMZ" in this context means a separate VLAN. Because the term is also commonly used to mean "DMZ host" where a router exposes a machine directly to the Internet. You want the former, not the latter.
But, more to the point, a beginner really shouldn't be exposing anything to the Internet. 🙂 Running a public service as a person who doesn't know how domains work will not end well.