4 ms·
I fix this by running a script on a cron job that updates dns records based on my current ip, using cloudfront to only allow known ips through my ufw rules. It
by hellojesus 5y ago
I fix this by running a script on a cron job that updates dns records based on my current ip, using cloudfront to only allow known ips through my ufw rules. It doesn't work for 100% uptime, but I've never had an instance where visiting my domain failed.
It may not work if you're running a tor node, depending on how cloudfront deals with them, but it does work for mostly-reliable dns resolution on a non-static, residential isp connection.
Not negating the project, just offering an alternative for people that want a static ip without renting vps/metal and without the isp static upcharge.
- mike_d 5y ago> alternative for people that want a static ip without renting vps/metal How do you think Cloudfront works? Amazon is just selling you a bunch of VMs pre-configured as load balancers. Not trying to be a jerk here, but the cloud has really caused otherwise smart people to lose a grasp on reality.
- hellojesus 5y agoI wrote Cloudfront but meant Cloudflare. My bad. I have a script that updates the dns record on a free tier plan with Cloudflare, and since traffic passes through them I can open my residential network to only ports 80 and 443 from their ip4/6 addresses.