Selfhosted

Surprised nobody has mentioned cloudflare ddns. If you registered your domain with cloudflare, you can use the api or qdm12’s (author of gluetun) ddns-updater to keep your A/AAAA records up to date.

You can use a ddns such as duckdns or host on github pages with jekyll or something

You only need a static address for hosting email or VoIP.

You can do just about everything else with DDNS (dynamic DNS). However with DDNS, you will have downtime until the DDNS update takes effect and propagates to clients. This can be seconds... or hours. Depends on the DDNS service and TTLs that they set and how quickly your script/DDNS client works to push the update out.

You should check how often your address changes and check how quickly your DDNS solution pushed the update out. If it's 10 seconds every 10 months, you will likely find that perfectly acceptable. If it's an hour every other sunday... maybe not. But only you will know how much downtime you can tolerate.

I always will take static IP personally. But it's not technically required and you can work around it if you want to save the 10-15$/month.

Edit: You could also argo tunnel if you're okay using cloudflare. But I don't think that answer is particularly in scope of the question. But just in case it's useful to someone out there I'm adding this edit. Doesn't fix the PTR requirement for Email and VoIP stuff though.

As others have said, you can use dynamic DNS, but you also might have an IPv6 address that doesn’t change. Or maybe it does, you’ll have to check with your ISP. But that one can be set up as an AAAA record in your DNS.

Most ISPs support IPv6, but some don’t, so you might not be accessible to everyone without also having an A record.

Whether your ip changes frequently depends on your ISP, but it's not necessary to have a static ip. My public IP changes about once a year, but I use my router to update my dns and make ally external services rely on DNS and not IP to connect.

You can also do this, look up "dynamic DNS". You just need to register a DNS name (can be free) and set up the updates to make it accurate.

I selfhost my blog without a static IP. You just need Dynamic DNS.

Keep in mind that your outbound bandwidth might be different from your inbound. I get 300mbps in, but only 5mbps out. It's not noticeable during normal Internet use, but as you start sharing content publicly, limited bandwidth becomes really noticeable.

You can rent a virtual private server (VPS). I used to have a number of these for under $10 / month. I imagine they might cost more now., but chances are you can still find something super affordable.

Wordpress.org will let you have a free site but you don't get a custom domain. Wordpress.com has a personal plan for $4 / month. Matt Mullenweg (CEO) has revealed himself to be a crazy piece of shit, so maybe look elsewhere. I'm just trying to give you a sense of how accessible this stuff can be.

Running a VPS will require more learning, but it can be super gratifying if you enjoy nerdy computer stuff and solving puzzles just for self-satisfaction. I used to use Rackspace, Linode, and something else that I can't recall at the moment. All were pretty reasonable. Rackspace had a ton of good setup guides for newbies that were well written. I'd occasionally land on those doing a web search for other hosting stuff and found them reliable.

Edit: DigitalOcean was the one I couldn't remember.

As others have already commented, what you need is a Dynamic DNS service, where you register a subdomain, and setup a small program or script on your computer that pings the DDNS server every few minutes, that way you leave that running on the background, and if the program detects that the IP with the request changes, it will update the subdomain to point to it automatically.

You could access the blog from the subdomain of the DDNS directly or if you get your own domain, you can point it to the DDNS.

If you want a recommendation, I have been using DuckDNS for years, and it has been pretty reliable.

It makes things easier, but you have options, such as:

1. dynamic dns.
2. Public reverse proxy or tunnel.
3. Onion routing.

You don't need one, but it does make things easier.

What you can use is something like Dynamic DNS to update your DNS record if your IP ever changes.

I could make this quick: Is your internet access behind a CG-NAT? If yes: you're gonna need a static IP.

Thank you for your replies everyone!

I'm looking into DDNS. Before I go with a provider, I notice that my router has this functionality built in. Should I use that?

(It's an Asus RT-AX86U Pro - so fairly chunky in terms of spec)

For reference, the set up is:

Docker containers for

1. Ghost
2. Nginx Proxy Manager

I would stand up a VPS in a cloud provider

Personally I would look at using a tunnel, something like Cloudflare tunnels (easy to setup, sorts dns out) but many here dislike Cloudflare for a lot of reasons. However the free plan allows you to get started, easily, and then once you are started and serving your blog you can look into other solutions, or failing that stay on Cloudflare. Other tunnels exist but if you have a domain, using cloudflare is the easiest imho to get started

@Paddy66 it depends.

I host everything, including website and email server behind a regular dynamic ip for years.

And no I don't get block by any gafam.

But I am lucky because my ISP doesn't change that often (maybe twice a year). And my domain provider provides an API that my ISP router can use to update my IP automatically.

It may work, it may not :)

Some of the other options are cloud flare tunnel or ddns that would give you static ip effect without static ip

YunoHost has automatic DNS updates

https://doc.yunohost.org/admin/tutorials/domains/dns_dynamicip/

No, you don't. Use Tailscale to expose your blog.

I just use github pages tbh. Free