Cloudflare-sync – Tool for using Cloudflare as a dynamic DNS provider
1–10 of 44 posts
Re: Cloudflare-sync – Tool for using Cloudflare as a dynamic DNS provider
#2That's cool.
No discredit to the author, they posted about this a few days ago with a couple other tools https://support.cloudflare.com/hc/en-us/articles/36002052451...
See also https://dnsomatic.com/ if you'd prefer to share your info with a third party and not deal with running your own tool.
Re: Cloudflare-sync – Tool for using Cloudflare as a dynamic DNS provider
#3having cloudflare in front is even better than just DDNS: you can hide your origin ip and avoid being DOSed.
I then use chrome's ssh extension with nassh-relay[1] to ssh, allowing me to not ever need to know the ip of my machine.
I have a modified version of docker-cloudflare[2] that also emails me when re-iping occurs (~once a year), just in case.
Re: Cloudflare-sync – Tool for using Cloudflare as a dynamic DNS provider
#4This is very handy! Bonus points for having it all dockerized too!
Re: Cloudflare-sync – Tool for using Cloudflare as a dynamic DNS provider
#5Here's another tool, this one written in Rust that does this: https://github.com/nickbabcock/dness
Re: Cloudflare-sync – Tool for using Cloudflare as a dynamic DNS provider
#6Another little-known Cloudflare tip is to use their Argo product's TryCloudflare feature when you want to open a localhost port to the world for experiments, demos.
It enables painless NAT traversal like ngrok, with the added benefit of Cloudflare's network acceleration and security.
https://developers.cloudflare.com/argo-tunnel/trycloudflare/
Re: Cloudflare-sync – Tool for using Cloudflare as a dynamic DNS provider
#7I wrote a little Go tool a few years back that can use your Digital Ocean account as a Dynamic DNS provider. It has been running on my EdgeRouter ever since with a cron job.
Re: Cloudflare-sync – Tool for using Cloudflare as a dynamic DNS provider
#8This is not very efficient:
- It updates the records every 30 seconds even if it doesn't have to.
- It has to be run as a daemon, eating memory and CPU time constantly.
- only checks one IP service (ipify)
I have a more advanced version, which:
- you can run as a cron job
- only updates the records if the IP address actually changed.
- checks multiple IP services (so in case multiple of them going down, it will still work)
- have a better command line interface
Re: Cloudflare-sync – Tool for using Cloudflare as a dynamic DNS provider
#9This is not very efficient: - It updates the records every 30 seconds even if it doesn't have to. - It has to be run as a daemon, eating memory and CPU time constantly. - only checks one IP service (ipify) I have a more advanced version, which: - you can run as a cron job - only updates the records if the IP address actually changed. - checks multiple IP services (so in case multiple of them going down, it will still…
It would also probably be good to use Cloudflare's own ip lookup service, available on every CF website's "/cdn-cgi/trace" page. The only thing is that you need to find a ipv4-only CF website to get the v4 instead of v6.
Re: Cloudflare-sync – Tool for using Cloudflare as a dynamic DNS provider
#10Another little-known Cloudflare tip is to use their Argo product's TryCloudflare feature when you want to open a localhost port to the world for experiments, demos. It enables painless NAT traversal like ngrok, with the added benefit of Cloudflare's network acceleration and security. https://developers.cloudflare.com/argo-tunnel/trycloudflare/
I definitely recommend anyone check out Argo. I use it in production and it's great.