I am looking to try out a basic #homelab #selfhosting server with the most basic and simple setup possible. The server is already fully setup, up, and running. Does anyone have a recommendation for dynamic DNS provider? (EU based only, preference AT)
@esparta the answer is POC simple: public/outside world access. The piece of the whole puzzle, that I am searching for, would ideally filter out all sorts of bot/scammers/insecure traffic.
@hacrods depends how basic you want because your basic might mean insecure, unreliable etc.
I now have a more sophisticated setup but started with using Mythic Beasts as my domain host because they they provide an API to set / update DNS records. I'd no sooner got that working with an OpenWRT router than I realised it wasn't secure enough, and now have a cheap VPS running Pangolin instead.
Both solutions handle all the obstacles that ISPs have put in the way that make this difficult.
@hacrods I had first tried some DynDNS services but they were tricky, unreliable and I didn't like reliance on a third party anyway.
@happyborg you did read my mind! I do mean basic and secure and that was in fact missing from my message. But my first step don’t need to be secure, as it will be just a POC. Thanks for the references, I will do some reading!
@hacrods if you're even less up on this than I was, using a reverse proxy is a good way of making things secure. There are various ways but I think they all end up creating a secure tunnel to the services/servers in your network, and require the public part to be outside your network in order to avoid making anything local public.
I chose Pangolin as least reliant on third party and most acceptable licensing (mostly copyleft).
@hacrods I think you need to answer one question: do you want to have access to your services in your homelab from the outside world? Or do you want the outside world to have acess to the services in your home lab?
In my case I decided I eventually want to access from the outside, because the latter option is always risky and pretty surely resource intensive when bots decided it's something worthy to have. That's how I went to use Tailscale first, and moving to headscale soon enough.