KISS
Delete all the registrar's crap
Add A record for the subdomains you want, like www or root (@) or socialwhatever to point to your reverse proxy's public IP
Done, reverse proxy proxies the request based on the requested URL
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.
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 30 days old, your post is exempt from this rule as long as you continue to engage in comments.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
KISS
Delete all the registrar's crap
Add A record for the subdomains you want, like www or root (@) or socialwhatever to point to your reverse proxy's public IP
Done, reverse proxy proxies the request based on the requested URL
An A record maps to an IP address. A CNAME record maps to another URL. Since you are trying to map to an IP address rather than a URL, you will want an A record.
If all of your sites will be served from the same proxy server at 204.230.30.104, you can create a single, wildcard A record for *.newexample.com. This will point every subdomain to your proxy's IP address. You don't need to create an A record for each subdomain.
If you are planning on serving some subdomains from 204.230.30.104 and other subdomains from another proxy at 69.4.20.187, you would need multiple A records for pointing the subdomains toward their respective proxies.
If you wanted to serve from proxy running on a dynamic IP address, and you're using a DDNS provider to point newexample.ddns.net back to your current IP address, you could use a CNAME record to point newexample.com to newexample.ddns.net.
If you have a static IP address, you can just use A records for each subdomain you want to use and not really worry about it.
If you do not have a static IP address, you may want to use one single A record, usually your base domain (example.com), then CNAME records for each of your subdomains.
A CNAME record is used to point one name at another name, in this case your base domain. This way, when your IP address changes, you only have to change the one A record and all the CNAME records will point at that new IP as well.
Example:
A example.com 1.2.3.4
CNAME sub1.example.com example.com
CNAME sub2.example.com example.com
You'd then use a tool like ACME.sh to automatically update that single A record when your IP changes.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| HTTP | Hypertext Transfer Protocol, the Web |
| IP | Internet Protocol |
| LXC | Linux Containers |
| NAS | Network-Attached Storage |
| VPS | Virtual Private Server (opposed to shared hosting) |
| nginx | Popular HTTP server |
[Thread #80 for this comm, first seen 10th Feb 2026, 06:50] [FAQ] [Full list] [Contact] [Source code]