search

wyne / blog-comments

1 stars 0 forks source link

posts/remote-containers #4

Open utterances-bot opened 1 month ago

utterances-bot commented 1 month ago

Remote Synology Containers | Justin Wyne

Personal blog about software, travel, photography, and rock climbing.

https://www.justinwyne.com/posts/remote-containers

wyne commented 1 month ago

Migrated comment from SquareSpace:

SciaticNerd

Thanks so much for this article. I'm not so familiar with configuring things like this, but I've set up the DNS server on the Synology, but am not sure how to configure the additional subdomains? So right now I use custom ports to be able to hit self-hosted services on the NAS. How are the subdomains ... is managed the right word? I'm thinking I am only intending the DNS server to really support the Synology, even though it could do more. I only mean for it to be used for the subdomains I'm self-hosting. Is that right? If that's true, do I need to configure the zone(?) for each subdomain? Are they aliased to the IPs? I realize I've got some learning to do, but am unfamiliar with this part. Any help or direction is appreciated.

wyne commented 1 month ago

Migrated comment from SquareSpace:

Michael

I am trying to figure out how to get Tailscale to go out via a Gluetun container. Any suggestions?

wyne commented 1 month ago

Migrated comment from SquareSpace:

D

Thanks for this article. How do you generate certificates for the nas.home domain and wildcard?

Justin Wyne

Something along these lines: https://xirkus.github.io/posts/synology-self-signed-cert-howto

wyne commented 1 month ago

Migrated comment from SquareSpace:

Elliot

Hi Justin. Great article - and after reading loads, I think this is the closest I've got to finding one that works and is simple (i.e. robust)... But your setup hinges on using the Firewalla as a DNS server for your local network, right? So you're duplicating entries across Firewalla and the NAS DNS? Any thoughts on how you might do this without a Firewalla - I was thinking of using the NAS DNS either way (i.e. Tailscale IP's internally and externally).

Justin Wyne

Thanks for the comment.

But your setup hinges on using the Firewalla as a DNS server for your local network, right?

That's right. Though you could just run another DNS server for inside the network? Which is basically what the router is doing. Not super clean though. I'll have a think about that...

So you're duplicating entries across Firewalla and the NAS DNS?

Yes, but the only one I really duplicated was my NAS, since that's all I really care about access while remote. This includes all the NAS subdomains as mentioned in the article. The only downside I can think of for using tailscale IPs internally and externally is that you always have to be running tailscale, and devices that don't use tailscale will have to use local IP address instead, which is more cognitive load.

rwaeselynck commented 1 week ago

Hi, I followed your tutorial cause I'm in the same configuration. Still, my subdomains keep reaching my router interface. vlookup send the public IP I guess.

rwaeselynck commented 1 week ago

how did you configure your domain dns ? I mean, you certainly have a public dns declaring your home domain somewhere with your public Ip, don't you?