Nice.
Consider adding fallback services to api.ipify.org, such as ifconfig.me or icanhazip.com
Free DDNS with Cloudflare and a cronjob
151–160 of 202 posts
Re: Free DDNS with Cloudflare and a cronjob
#152Earlier quoted context omitted.
Not sure, honestly.
Interesting! also asked Claude Opus: Using the same provider for both domain registration and DNS hosting can introduce several risks. Here are some of the main risks and ways to mitigate them: 1. Single point of failure: If the provider experiences an outage or security breach, both your domain registration and DNS hosting could be affected simultaneously. This can cause your website or services to become unavailabl…
Those are valid. I would personally be worried about getting kicked off Cloudflare and the procedure for transferring domains being messy and time consuming.
(Although CF seems perfectly happy hosting really shady sites that host primarily illegal content)
Re: Free DDNS with Cloudflare and a cronjob
#153Earlier quoted context omitted.
GP was saying the client would require a web browser. The server of course needs cloudflared. That said, personally I don't really have any devices that can use SSH but not a browser.
My past comment is wrong but you do need to install cloudflared on the client if you want to SSH without a browser. Read the docs, you can do it either way.
I found it easier to use ssh over websocat over cloudflared. Then you just need websocat again on clientside and can use regular ssh client with it
Re: Free DDNS with Cloudflare and a cronjob
#154Earlier quoted context omitted.
the same specific interface used to contact the external server
That requires running it on the router/device which gets the public IP address. By using the service you can update your DNS IP address on a system that is behind the router.
What do you mean?
Every device gets a public ipv6 (usually).
Re: Free DDNS with Cloudflare and a cronjob
#155If you’re behind a CGNAT then this won’t help you much. For many residential installs that is the case unfortunately
Re: Free DDNS with Cloudflare and a cronjob
#156Instead of using DDNS, I have been using Cloudflare tunnels to expose my home services to the internet. The setup is much simpler and it seems like it's more secure too You specify a port and point it to a subdomain and it just immediately works, no maintenance necessary. The daemon only needs to be installed once with a simple terminal command
"Instead of DDNS, I have been using Cloudflare tunnels to expose my home services to the internet."
Will this work if the "home services" include authoritative DNS.
Re: Free DDNS with Cloudflare and a cronjob
#157Earlier quoted context omitted.
> Well, one of the "challenges" is the one in a different comment: most registrars don't allow fine-grained control over who can update what DNS records. Afaik, every major registrar allows you to add an NS record for the _acme-challenge subdomain, allowing you to put the _acme-challenge subdomain on a custom, self-hosted DNS server. That in turn allows you to make the permissions as specific as you'd like. Personall…
Using CNAME delegation for the ACME challenge domain and directing that to a Route 53 zone is my preferred approach. Then (as long as you have CloudWatch configured) you get inherent auditing and very flexible privilege management.
That wouldn't work for this use case though would it? AWS doesn't allow downloading the certificate (I could be wrong)? Typically certificates can only be used with other AWS services. E.g. you can't download the certificate and serve it from a home server.
Re: Free DDNS with Cloudflare and a cronjob
#158Earlier quoted context omitted.
From the discussions I've read, it's not as clear cut, e.g.: https://old.reddit.com/r/PleX/comments/152wfdh/can_i_use_a_c...
It rarely is clear cut with Cloudflare, many of their policies are ambiguous so you never really know if you're stepping over the line until you get an email from sales asking you to either cut it out, start paying, or pay more. Others experience might give you a rough idea of what they'll tolerate, but since none of it is in writing they can change their minds on a whim.
As I've painfully learned, Cloudflare's "free bandwidth" is only free until a point.
Cloudflare threatened to terminate our $15k enterprise license last week for serving 76 TB of API JSON files last month (90% cache hits).
I moved half of the traffic to a new domain with a Business license to see what they say...
Re: Free DDNS with Cloudflare and a cronjob
#159Earlier quoted context omitted.
It rarely is clear cut with Cloudflare, many of their policies are ambiguous so you never really know if you're stepping over the line until you get an email from sales asking you to either cut it out, start paying, or pay more. Others experience might give you a rough idea of what they'll tolerate, but since none of it is in writing they can change their minds on a whim.
As I've painfully learned, Cloudflare's "free bandwidth" is only free until a point. Cloudflare threatened to terminate our $15k enterprise license last week for serving 76 TB of API JSON files last month (90% cache hits). I moved half of the traffic to a new domain with a Business license to see what they say...
My email is jgc@cloudflare.com. You can email me about this.
Re: Free DDNS with Cloudflare and a cronjob
#160Earlier quoted context omitted.
Using CNAME delegation for the ACME challenge domain and directing that to a Route 53 zone is my preferred approach. Then (as long as you have CloudWatch configured) you get inherent auditing and very flexible privilege management.
That wouldn't work for this use case though would it? AWS doesn't allow downloading the certificate (I could be wrong)? Typically certificates can only be used with other AWS services. E.g. you can't download the certificate and serve it from a home server.
You're not wrong, but the idea here is not to use AWS' certificate manager but their DNS service on which you would only handle the acme-challenge subdomain. This would allow you to limit who can update which subdomain. The LE cert is obtained normally.