Matt The Horwood

I moved to Google workspace for email, yes I know it Google.

I have my home IP and dedi IP in the routing settings, then just use SMTP to Google and let them forward to me.

All servers have null mail installed and setup for Google, I also have docker containers with config if needed

You need a way to hand it a file for editing, nextcloud can do that

I use nginx as the internet facing proxy, write my own config and manage it with source control. Also use traefik in docker land with service labels to configure it

Im not sure I understand your issue, DNS is the magic that allows you to goto home.somedomain.com and get a webpage. But you still need to give DNS the location of the server, much like the contacts in your phone.

DDNS is how you have your home connection attached to a DNS record that is updated when the IP changes, see other comments.

Also once you understand how it all hangs together, you can do some really cool magic to make getting to your services easier

First off, backups of the configs any user data that you can’t torrent should the inevitable happen.

Then set time aside to do updates, I spend Wednesday evenings updating and improving my setup.

Then find a way to track update announcements, I use both an RSS reader and newrealeases.io to know when something I run gets an update

What I can tell you, working for a company hosting data for the UK NHS.

Is that hosting is easy, I have a very reliable homelab. I keep things up to date and make sure to secure things the best I can.

But security is hard, there are many things to secure. Blind spots you didn’t even know you had.

The bast way to look at security, it to start with secure and dial things back so that it works.