To resolve whatever hostname you’ve setup for ddns

As long as whatever firewall rules you’re using is capable of resolving FQDNs then I don’t see an advantage of doing this. Maybe in the off chance that your IP changes, someone else gets the old IP and exploits it before the DDNS setup has a chance to update. I think that’s really unlikely.

Edit: just to add to this, I do think static IPs are preferable to DDNS, just because it’s easier, but they also typically cost money.

They’re generally highly regarded.

Way easier than having them wear an armband.

Sure and I know that you meant. But I also think that with a little creativity and compromise it’s also not difficult at all to get something that’s not that long and also easily said.

Even if they are finite, the number would be so impossibly large that for all practical purposes this would not be the case.

I use Portainer for this, though it doesn’t aggregate logs or anything. It just makes them easy to get to and read.

Airplane mode is one button. Cellular is another button.

Just pull up your control center and you should see.

There’s a separate cellular toggle yes.

You don’t need a protectli, even an old optiplex should be able to handle opnsense and/or a pi hole. You would just want to have 2+ NICS.

Or if it needs to be low powered there are definitely other options.

Look, I never said you were wrong man. Clearly you probably have a lot more experience than i do. Which is why I said what I said. Because I personally believe Proxmox is way easier for someone who is a casual like me. That’s all.

Edit: Also, though it doesn’t really matter, I don’t use LXC.

I’m going to disagree with this. I’ve setup everything in one Debian server before and it became unwieldy to keep in check when you’re trying new things, because you can end up with all kinds of dependencies and leftover files from shit that you didn’t like.

I’m sure this can be avoided with forethought and more so if you’re experienced with Debian, but I’m going to assume that OP is not some guru and is also interested in trying new things, and that’s why he’s asked this question.

Proxmox is perfectly fine. For many years I had an OMV VM for my file server and another server for my containers. If you don’t like what you’ve done it is much easier to just remove one VM doing one thing and switch to some other solution.

It seems cool but it’s just going to be a big headache man. I would just spin up a domain controller and maybe some workstations to play around with.

I would check out serverpartdeals as they’re pretty reputable. But for any used drive, I would make sure that you have a limited warranty or at least some sort of return policy. Once you get the drive, run badblocks on it, which will check for… bad blocks.

There’s been plenty of malicious apps found in the past. Though, I’m sure the play store isn’t much better. Disappointing that Apple will bend devs over a Barrel sometimes but they don’t find shit like this.

Looks like jellyfin has an api. I’m sure that could be leveraged. Just would need to have a way to send over api requests. You mentioned JavaScript, but I could see this being done in maybe DJango instead if you’re familiar with python. Though the learning curve for Django is a beast in itself imo

Seems like you could just make a simple web page for this.

.local is definitely local but it’s common for it to be used with mDNS primarily. To the second part of your question, yes that’s correct, since it will be reserved it will not be any public DNS server, even if it did look outside it wouldn’t find anything.

Sure. Though I’m not an expert on mDNS or anything. It stands for multi cast DNS. In a normal scenario, when your PC tries to connect to a local resource at its hostname it will use a local DNS server (or its own cache). It’s like a phone book. I know who I’m looking for, I just need to look in the phone book and see what their IP is. With mDNS there is no server. You’ll have a service that will plan to respond at a particular .local hostname, so like jellyfin.local (this is just an example, I don’t know if it has mDNS) but that isn’t registered on a server. Instead when your PC wants to reach jellyfin it will send a multi-cast to the other local devices and say “ok, I’m looking for some guy named jellyfin.local, which one of y’all is that?” And the jellyfin server will respond and say “yo what up, this is my ip address”

So anyway, that only works with .local addresses. You could use .local with a regular dns server, but then you may run into a conflict. So that would be the benefit of reserving .internal

If you want more confidence, run badblocks on the drives right after you get them. It will test the drive for any… bad blocks. Will take a while depending on your drive size.