I want to get out of the way the fact that I do not know networking. I work Desktop Support at my job so I have a pretty okay understanding of hardware. I use Fedora Linux at home and I am not scared of a terminal. When it comes to networking though it is a big shoulder shrug for anything outside my LAN. I would like to know more but it will take some time.

I have a project that is coming together to make a little NAS with a Pi4 that I have collecting dust. I have the hardware figured out, I will probably use OpenMediaVault, may just set up the SMB share myself, and if all I wanted is a NAS at home I would be golden. But I want to set up a Wireguard VPN because my ultimate goal is to replace my pCloud subscription. I have watched some tutorials on YouTube from larger channels like Networkchuck and Wolfgang, but I am confused specifically around the whole DNS thing.

I get that my public IP changes from time to time. I understand the need for a dynamic DNS to counter that. I purchased a domain from a registrar service up here in Canada and after the purchase the immediate next step was web hosting. Do I need to host the domain in order to use it for the Wireguard setup?

  • InfamousAgency6784@alien.topBEnglish
    1·
    10 months ago

    When you buy a domain name, DNS is just a way to link that name to your IP.

    When your IP changes, you need to notify the DNS servers that it has changed.

    In the real world, DNS would be a book where people’s names are written alongside their house address. If you change house, you need to tell the editors of those books your new address.

    Dynamic DNS providers are like normal providers except that they continuously edit new versions of their book and make it easy for just anyone to update their address automatically.

    Given what you say though, I would not proceed like that. Either just get a cheap VPS as a fixed-IP bridge or use something like Tailscale to manage the dynamic side for you.

    I say this because dynamic DNS services can be a bit problematic at times. If you change IPs like once a week/month, it’s absolutely fine though long-term SMB/NFS shares will fail very badly when that happens. If you change IP for every GB downloaded, that will be a real pain real quick (IP update is far from instant when going through DNS).

    You’ll learn more about routing with the bride setup but you’ll get a much nicer ‘turn key’ experience with Tailscale, wherever you are. With both solutions, long-term connections won’t be a problem: the only downtime you’ll get is where either one of your box actually restarts.