5·
5 months agoI switched from duckdns about a year ago as it failed to resolve the addresses for my jellyfin server. I ended up buying a domain from cloudflare for 3 years for about $4, and I self-hosted ddns updater to automatically grab the dynamic ip, and set it to a subdomain.
As for your nginx config, I’d imagine you could make 2 separate config files in sites-enabled that are nearly identical, but listen for different domains.
Something like this:
#config file 1
server {
listen 80;
server_name example_a.com;
location / {
return 301 http://example_c.com$request_uri;
#or use an ip instead of example_c.com
}
}
#config file 2
server {
listen 80;
server_name example_b.com;
location / {
return 301 http://example_c.com$request_uri;
#or use an ip instead of example_c.com
}
}
#Or use "proxy_pass http://example_c.com;" in the location tag instead of "return 301..." if you want to reverse proxy the traffic
I wouldn’t say my hostnames are very creative, but they all have some kind of backstory.
Main desktop: POwOful
It’s a pretty powerful desktop, so why not call it that :)
Laptop: LenOwO
Can you guess the laptop brand?
Server 1: Shitbox
It’s my first server box I ever built, so it’s underpowered and pretty shitty.
Server 2: Stowage
My proper server with actual data parity, and it’s pretty powerful
Server 3: Jank
This one is another shitmix of hardware with random harddrives in raid 0. I am aware that they’ll die at some point, and all of that data stored on it will be lost, so i use it as temporary storage whenever I need to copy something from one machine to another.
Robot vacuum: suckywucky
Yea…