How does DNS work with a setup like this? I assume that ISPs generally don't want people hosting servers on residential connections.

NAT is the hard problem. I'm tracking this one: https://github.com/tailscale/tailscale/issues/11563

You can also talk to your ISP (or their competition). My friend negotiated something like +5€/mo for a static IP. We can play Factorio together, yay!

Plenty of dynamic DNS solutions. TP-link even has one you can set up from their app (not a endorsement, don't know if it is good or bad)

I have a fiber 2.5 gbit connection without static IP. But I run a script on the router that updates the DNS settings when the IP changes, you just have to have a DNS provider that allows you to do that and change ttl.

Don't most ISPs hand out IPs that are only nominally dynamic?

My IP is dynamic, but in practice only changes ~once/year. Even if I go to my router and release the WAN IP and reboot, when it comes back up, it'll have the same WAN IP. But then that once/year, my Internet randomly goes down and I have to reboot my router and I end up with a new WAN IP.

When that happens, I just go and manually update the IP for a hostname I use. If I wanted to get fancy, I could automate all this, but meh. CBF to spend the time automating something that only takes me 30 seconds to do once/year.

> I assume that ISPs generally don't want people hosting servers on residential connections.

They likely don't care unless you're saturating your upload consistently. Also, some ISPs like Comcast/XFinity are known for having extremely asymmetrical connections. At least, they used to. I'm fairly certain I've heard of some people having 1 gbps down, but only like 16 mbps up.