is it better to use subdomains or paths?
https://lemmy.blahaj.zone/post/122352
is it better to use subdomains or paths? - Blåhaj Lemmy
I have a few selfhosted services, but I’m slowly adding more. Currently, they’re
all in subdomains like linkding.sekoia.example etc. However, that adds DNS
records to fetch and means more setup. Is there some reason I shouldn’t put all
my services under a single subdomain with paths (using a reverse proxy), like
selfhosted.sekoia.example/linkding?
Everyone is saying subdomains so I'll try to give a reason for paths. Using subdomains makes local access a bit harder. With paths you can use httpS://192etc/example, but if you use subdomains, how do you connect internally with https? Https://example.192etc won't work as you can't mix an ip address with domain resolution. You'll have to use http://192etc:port. So no httpS for internal access. I got around this by hosting adguard as a local DNS and added an override so that my domain resolved to the local IP. But this won't work if you're connected to a VPN as it'll capture your DNS requests, if you use paths you could exclude the IP from the VPN.
If your router has NAT reflection, then the problem you describe is non existent. I use the same domain/protocol both inside and outside my network.
Does NAT reflection still work if your PC is connected to a VPN?
Sekoia
tkohhh