operator

joined 1 year ago
[–] operator@kbin.social 1 points 1 year ago

That’s becoming interesting once I’m setting up a slaves for failover & local proximity ^^ looking forward to deep diving into it

[–] operator@kbin.social 2 points 1 year ago (2 children)

Appreciate it!

[–] operator@kbin.social 2 points 1 year ago (5 children)

That be amazing! I am currently not using anything (took down my homelab a while back) and planning on completely starting over fresh now.

I am most likely going with unbound! So if you could, that be great!

[–] operator@kbin.social 2 points 1 year ago (1 children)

Thanks! That was really insightful. I guess I'll give it a try some day, for now everything runs in ipv4 and that runs well haha!

[–] operator@kbin.social 1 points 1 year ago

How does the usenet work exactly?

[–] operator@kbin.social 1 points 1 year ago (3 children)

What were the biggest pains? What was surprisingly easier than expected?

[–] operator@kbin.social 1 points 1 year ago* (last edited 1 year ago) (2 children)

What I'm doing is using a dedicated VPN Gateway container. The instances running delicate services have a static default route to the GW-container.

This is an extra step, but allows me add easily route other services or clients or even whole networks through my VPN without additional setup or specialized containers bundling both.

Wanna use it on the phone? Change the gateway address. Wanna use it from my Linux machine? Add a static default route. Etc...

Works flawlessly!

[–] operator@kbin.social 1 points 1 year ago (8 children)

Of course! So in order to get maximum speed on your services, you wanna use a direct internal route when you're inside your net. My understanding is, that when using an external cloud VPS with a proxy, local clients go through unnecessary routing..

Local request --out--> external VPS (proxy) --request data from internal--> receive data on external proxy --send back--> local client

So what I am saying, all requests are unnecessarily routed through the external VPS. So one would have to create an exact duplicate reverse proxy internally to avoid leaving the net. When accessing domain.com, the internal DNS returns the local proxy IP, when outside you receive the cloud VPS IP.

Or am I missing something?

Thank you for taking the time!

[–] operator@kbin.social 2 points 1 year ago

One of my considerations is the privacy side… VPN or self hosted solution seems to be the waay better choice in that case.

[–] operator@kbin.social 1 points 1 year ago

Haha! Explaining for dummies, I like it.

[–] operator@kbin.social 1 points 1 year ago (10 children)

Thanks! How do you handle that with internal DNS? I suppose you’d need to setup the exact same proxies on the internal and external server, and local DNS handles which one my domain it’s being resolved to?

[–] operator@kbin.social 1 points 1 year ago (1 children)

Thank you for the detailed explanation. I am running Tailscale as a temporary solution to access some services, but I dislike that you have to set firewall rules basically twice (once in your local network and once in Tailscale). I suppose it would be similar for CF?

view more: ‹ prev next ›