this post was submitted on 11 Jun 2026
42 points (95.7% liked)
Selfhosted
59973 readers
418 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.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Do you have a static IP? Just point your domain to that. I only have A- MX- and CNAME-record. A is for the numerical IP. MX is for mail, I don't use it. CNAME is for subdomains afaics (currently only contains www).
All fields are comma-separated lists.
NS stuff is for if you're running a nameserver and I never even looked into it.
A records return the numerical address of a name.
CNAME returns a different name for a name. Basically 'synonym' so the maintainer only has to change the one master, A record when the IP address changes. Convenient to use CNAME to point www.example.com to example.com, but you can use it just as well to point example.com at my.private.host.xyz You can even chain multiple CNAMEs to make it easier to manage a complex backend structure while presenting a simple address to users.