TheQuantumPhysicist
@TheQuantumPhysicist@lemmy.world
- Comment on Tick tock 🕚 1 year ago:
This is nothing… imagine that to this day we have people who believe the Russia-gate nonsense, despite the FBI having poured 25 million USD into it and found nothing, and people in CNN admitting it was a hoax. But mission accomplished… people are duped.
I’m not American, but this whole “indictment” nonsense is just attempts to cheat in 2024 to prevent Trump from rallying. They’re terrified! They know if Trump wins he’ll empty the swamp and remove 90% of the bureaucrats. He swore he’ll do it.
And people still doubt this is a civil war… and dumber people to this day think this is done in good faith. The stupidity of humans never stops to impress me. Go ahead, Americans, start killing each other already… maybe then you’ll learn how to respect each other’s boundaries, like Trump never locked Hillary up because he knows what message it sends.
- Comment on How can I restrict visiting a service through a domain to VPN-connected devices? 1 year ago:
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.
- Comment on How can I restrict visiting a service through a domain to VPN-connected devices? 1 year ago:
Thank you for the clarification. I’ll give that a shot. Cheers!
- Comment on How can I restrict visiting a service through a domain to VPN-connected devices? 1 year ago:
Please see this comment to understand my frustrations with the answers in this thread: lemmy.world/comment/2363248
- Comment on How can I restrict visiting a service through a domain to VPN-connected devices? 1 year ago:
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 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.
- Comment on How can I restrict visiting a service through a domain to VPN-connected devices? 1 year ago:
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, how will the service only work through that VPN?
- Comment on How can I restrict visiting a service through a domain to VPN-connected devices? 1 year ago:
But what about the domain name association? How is that done?
- Submitted 1 year ago to selfhosted@lemmy.world | 20 comments