Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Please elaborate a little more. So assuming the server where the service lies has IP address 1.2.3.4, and some VPN that I can connect to with 1.2.3.4:1194. If my DNS server points to 1.2.3.4, and say there's an http server there that's normally accessible with 1.2.3.4:80, how will we enforce that working only through VPN?
There's an internal ip address for the VPN server, say 4.3.2.1, you point the http dns record to that address.
The VPN server has 2 addresses by definition, an internal address and an external, public one that you connect the VPN to. Make sure the webserver only exposes itself on the private address, either by configuration (nginx/apache listen address) or by firewall (iptables -A input -j DROP)
About the DNS, you can use an internal DNS and find some way for your VPN to configure it in all the machines connected to it.
DNS usually has a fall back if the name is not found, so you can always have your custom DNS on and it'll first check its own records then check for some level up (I'm basing this off of my experience with with pihole https://docs.pi-hole.net/ftldns/ )
About your ports question: you just need to change the ip to the VPN one.
For example, I have a VPS which has a public IP and I have tailscale installed.
If I were to make my service listen to all interfaces I could use
1.2.3.4:1194or100.100.100.100:1194(this being the tailscale ip)But I usually only configure them to listen to
tailscale0, so I can no longer reach them with1.2.3.4:1194, only with the tailscale ip.In your DNS you need to configure this new IP to be served.
I'm guessing you can also do some configuration with a firewall.
Probably
ufw add allow from 10.0.0.0/8could work if this was the IP range of your VPN, then any one can still use your public IP and only your VPN will be able to connect (But don't quote me on this, I haven't done it).(Just be sure to check the configuration of your service, docker can bypass ufw :/ )
Thank you, but my question was specifically about DNS. Another person pointed out that setting the DNS record to the VPN destination is the right answer. I appreciate the details you wrote and I'll look into them.
Whatever you do with IPs, you can do with ports too.
"Allow this port, but not that one".
Please see this comment to understand my frustrations with the answers in this thread (copy/pasted from another comment):
I’ve been managing servers for over 10 years, and I never have felt stupider, and I still don’t understand how to do this. Everyone is making a comment that I don’t understand.
Let’s talk internet 101, and please tell me where I’m wrong.
You make a request to https://myservice.example.com. The DNS responds to a query giving you an IP address, say 1.2.3.4. Now the client software makes another request to 1.2.3.4:433 (say if we’re attempting to access an https server, binding the SNI address to the SSL/TLS header). The request will be sent to that server, and the server will respond. In what part of all this process can the VPN can do anything?
Normally if you want to access a device through VPN, you make a request to a WHOLE other ip address in another subnet on another (virtual) device locally. It has absolutely nothing to do with 1.2.3.4. It’s something like 10.10.100.X… or similar. How will my domain, myservice.example.com, route to that address, 10.10.100.X? Is it as dumb and simple as routing there? Or is there more to it? It doesn’t sound right to make the DNS server record point to 10.10.100.X.
I'm sorry. I don't know enough about the subject. I'm sure there are firewall daemons, or IPTABLES configuration that can do what you want, but that's beyond my area of expertise. Good luck.