Comment on Self hosting and HSTS preload domains
wraith@lemmy.ca 4 days agoI 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.
Comment on Self hosting and HSTS preload domains
wraith@lemmy.ca 4 days agoI 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.
just_another_person@lemmy.world 4 days ago
Then you just need to run a DNS Forwarder, or something with a DNS forwarding capability. Your router most likely already has this.
DNS is essentially just a request and a response from a service. These can be public or private. A DNS Forwarder on your network will quickly respond if it knows that something is when asked, and return an IP address. If it doesn’t know what it is, it will ask the public services available.
So if you have an internal-only network, a VPN into that network, and a forwarder or other DNS service on that network, you just tell your VPN client of choice to switch to using that DNS instead of public once it connects. It’s a simple setting that every VPN solution supports, and actually makes you MORE secure by not using public DNS servers by default. You can add any record you want to said forwarder, and it will return whatever value you give it for a given domain name.
Here’s a simple workflow as an example:
All contained within your local network and VPN by extension.