42
What to do after getting a domain name?
(programming.dev)
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 11 Jun 2026
42 points (95.7% liked)
Selfhosted
61021 readers
195 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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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 3 years ago
MODERATORS
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.
No, I was referring to a separate DMZ host...
Physically separate firewall connection, with different firewall policies between internet<--> DMZ than DMZ <--> internal network.
Not a VLAN. VLAN Hopping makes it possible to jump between VLANs, so they should only be consided as an administration tool, not a security mechanism.
But, I agree with you, putting a device on the internet isn't something that anyone should do without understanding the technical issues.