Comment on Self hosting and HSTS preload domains
wraith@lemmy.ca 4 weeks agoI will need it to be available via a VPN or other means, but it’s not going to be any more public-facing than it has to be.
Comment on Self hosting and HSTS preload domains
wraith@lemmy.ca 4 weeks agoI will need it to be available via a VPN or other means, but it’s not going to be any more public-facing than it has to be.
just_another_person@lemmy.world 4 weeks ago
Right, so if it’s going to JUST be available over VPN, you don’t need to use a public TLD, DNS, or HSTS at all. Why use the public TLD with these requirements and expose private IP address space over public DNS if it’s solely purpose isn’t going to be consuming publicly?
wraith@lemmy.ca 4 weeks ago
So I should just host it with an IP address instead of using the domain?
I hadn’t thought to do that, at least not for anything other than short lived internal-network-only projects and tests. An IT guy in the company I work for advised me to just get a domain and host with it/subdomains to make it easier to manage if I wanted to host multiple services.
just_another_person@lemmy.world 4 weeks ago
Well, that’s the simplest way in practice, but not usability. Let me explain:
You control the IP address space once you’re connected to your VPN, and you control the various settings that connection makes, including DNS.
You have a network already, and a VPN of some sort, so that means you have a network device that is terminating that VPN. Is that a router you’re familiar with, or a box on your network?
wraith@lemmy.ca 4 weeks ago
I haven’t set up the VPN yet. I am getting as much info as I can before I start any work. For the sake of this discussion, it would be a box on my network.