News for hackers. Stuff that matters.
Re:Upgrading my home server by kissgyorgy on Sunday July 21, 2019 @06:53AM (#20490771)
You register a domain name, set it up on CloudFlare and use a script which checks if your IP changed and submits it to the CloudFlare REST API setting an A record: https://github.com/kissgyorgy/cloudflare-dyndns
Re:Upgrading my home server by ThatPlayer on Sunday July 21, 2019 @07:12AM (#20490818)
I've used ddclient which has support for a lot more DNS services, including Cloudflare: https://github.com/ddclient/ddclient
Re:Upgrading my home server by kissgyorgy on Sunday July 21, 2019 @08:50AM (#20491114)
I wrote the script because I did not wanted to use ddclient :D and it's terrible config syntax. Also, it corrupted the cache regularly for some reason.
Re:Upgrading my home server by lunchables on Sunday July 21, 2019 @09:06AM (#20491160)
I wanted to add my "anecdata": I've run ddclient with namecheap for years and never had a single issue.
Re:Upgrading my home server by rograndom on Sunday July 21, 2019 @01:16PM (#20492379)
I ran into an issue doing this a few years ago where my ISP was blocking ports 80 and 443. I could port forward from my router on non-standard ports like host1.domain.tld:10080 (wan) -> 80 (lan), but LetsEncrypt didn't really like this and it was a pain to manually enter port numbers.

My solution was to use a VPS that was doing other stuff to also act as a nginx proxy to the internal machine on a non-blocked port. So it's now host2.domain.tld:443/80 (vps/nginx) -> host1.domain.tld:10080 (wan/host1.domain.tld) -> 80 (lan).