Someone

  • 55 Posts
  • 950 Comments
Joined 2 years ago
cake
Cake day: March 12th, 2024

help-circle




    1. You need port forwarding and hosting a reverse proxy into your infrastructure
    2. You shouldn’t really worry about DNS in that case, only make sure you’re domain resolve to the right IP
    3. As I said in 1. you will have to port forward to get access from outside (maybe you want to setup fail2ban on the reverse proxy to limit a bit spam)
    4. Reverse-proxy. No, you own a part of the domain so all the subdomain are belonging to you as well. Ex. When you buy test.com you don’t buy the com domain but you buy media.test.com for example


















  • I want to protect my home services, so when accessing my domain it goes trough the vps and you only knows its IP (a datacenter IP) but for my friends and family I don’t need this protection so they are accessing my home with a VPN connection and btw they are using the vps to make requests and so protect their privacy.

    The simple solution (since my services are publicly available), would be to route all traffic coming from my friends trough my home and then through the vps. But I don’t like this idea since it would add a lot of latency and useless traffic since the client is already going trough my home…

    So my question is how could I route directly to the client the local services and let go through the vps the rest of the traffic?