Hello everyone.
I bought domain name (example.com) from https://njal.la/ and I want to direct it to my server but I need help with it.
Let’s say that I have public and static home IPv4 address 10.172.172.172 (example) and on that address is a computer running on 192.168.200.101 (example) and there is jellyfin server (port 1020/tcp), immich server(port 1021/tcp) and bitwarden server (port 1022/tcp).
My question is can I create a subdomain and point it to these servers?
Like; jellyfin.example.com -> 192.168.200.101:1020
immich.example.com -> 192.168.200.101:1021
bitwarden.example.com -> 192.168.200.101:1022
Or do I have to buy two more separate domains for these servers? Like example2.com and example3.com?
Sorry for english and also if this is a stupid question but I need to know. I have never so far used domains and never dabbled in dns setting and I don’t know where to search for info.
DNS and domains are just human-friendly IP addresses.
You only have 1 public IP address.
So, to access different services you need to use different ports.
Or run a service on a single port in front of the other services that can understand the connections and forward the connections to the actual services - known as a reverse proxy. In the case of http/https, there are plenty of reverse proxies that can direct requests based on all sorts of parameters, subdomains being one of them.
If you are just starting out, I’d recommend a docker compose stack and Nginx Proxy Manager.
Learning containers & docker makes everything easier.
NPM is a very easy to use reverse proxy with a nice GUI, so you don’t have to configure CertBot/ACME or learn the specific config language of Nginx.
If you are unsure of domains and all that, you can try it out for free.
Your computer has a hosts file (/etc/hosts on Linux, I think it’s in system32 on windows). This allows you to tell the computer “for the domain example.com use the IP 10.0.0.200” or whatever you want. You need a hosts file entry for each subdomain.
What this means is that you can run up a docker compose stack on your computer and point a bunch of sub domains to 127.0.0.1, use self-signed certs, and play around with nginx proxy manager and docker.
No money spent, no records published, no traffic leaving your computer.
Zero risk.
There are loads of tutorials out there on NPM and docker compose stacks. Probably some close to your specific requirements.