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
this post was submitted on 10 Feb 2026
24 points (100.0% liked)
Selfhosted
56568 readers
635 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 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!
founded 2 years ago
MODERATORS
And to which IP do I open ports 80 and 443 in my router, then?
(You are really underestimating the second S of KISS in my case, sorry!)
When port forwarding, you want that internal IP to be the internal address of the server on your LAN. That way, all port 443 traffic sent to your external ipv4 (as received by your router) is sent to whatever machine is hosting the web server or reverse proxy.
Regarding the www sub domain cname, idk what your registrar is doing but it's common practice to redirected www to your base domain, or vise versa; so web visitors get a consistent experience whether they type www or not. It would probably be best to start fresh though
(You are really underestimating the second S of KISS in my case, sorry!)
LOL That got a physical chuckle as I can most definitely relate.
I'll need to know a little more about your setup. Sending DM...
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.
Thanks for the reply. That makes sense. I now understand how to point the domains / subdomains using "A" record.
Could you please also clarify which IP I need to open ports 80 and 443 to, in the router? Or does the IP in the router actually refer to the internal IP device addresses? (Like 142.168.0.6, etc)?
Your 142.x.x.x will be your public IP address. All devices on your network share that public IP. They all have a unique private IP address too, accessible only on your network. It probably starts with 192.168.x.x, but it could be 10.x.x.x or even less likely 172.16–31.x.x.
If you want to operate a web server that users can go to by typing https://youdomain.com/, you'll need to forward from ports 80 and 443 through to the internal IP address of your server, using the "port forwarding" settings on your router. What port on the internal IP you route to depends on how your server is configured. But a basic default configuration is fairly likely to be 80 and 443, too.
Since you have a reverse proxy, all traffic from your router should go to that. Then you use that to send the appropriate traffic to the appropriate server based on whatever rules you want to apply. (e.g. siteone.mydomain.com goes to server 1, sitetwo.mydomain.com goes to server 2, or mydomain.com/siteone goes to server 1, etc.).
It depends on how you want to do it; how your reverse proxy server is setup. I use Pangolin running on a VPS as my proxy server. It uses a tunnel ("Newt") between web servers running on my home network and the VPS, so I don't need any open/forwarded ports on my home router.
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]