Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Free DDNS with Cloudflare and a cronjob

github.com

Post reply on HN
Print view View original

191–200 of 202 posts

Re: Free DDNS with Cloudflare and a cronjob

#191

Post by tracker1 »

KennyBlanken wrote: post #72
kazinator wrote: post #60

Earlier quoted context omitted.

How can you claim it's simpler in the light of the revelations in noname120's comment? Dynamic DNS is literally one little service you run to "phone home" to the dynamic DNS provider. This service is bundled in consumer routers; just find it in the WebUI, put in the credentials and turn it on. You know what could be simple: a periodic job that figures out your public IP address, and if it has changed, generates a hos…

Consumer firewalls, the largest names in open source firewalls, and at least one webserver/reverse proxy that I know of. There also dozens of existing DDNS daemons out there already with far more developer, testing, and user eyeballs on them. The firewall solution is preferred because the firewall knows when the external interface changes IP addresses, so there's no system or network overhead from having an agent rep…

Assuming you can add a custom URL, you can still do this through the firewall instead of an event to check the public IP. I like using my own, custom domain for this use case. I've also used and put a couple of domains up on freedns.afriad.org for others to be able to use.

That said, the only hole in my firewall/router is a port for Wireguard.

Re: Free DDNS with Cloudflare and a cronjob

#192

Post by tracker1 »

sagz wrote: post #182
tssva wrote: post #19

I used ddclient with Cloudflare for years with no issues. Recently upgraded my home router and the manufacturer operates a free dynamic dns service enabled with a toggle button. I have a cname record in my domain’s dns records pointing to the dynamic dns entry. I actually don’t even need that anymore. All the services I run at home are only for immediate family so only available remotely via a Wireguard vpn connectio…

Wow! May I know the router model that does 900+mbps of Wireguard? The dedicated GLinet box I got for tailscale does only about 60-90mbps. Apple TV 4K does a paltry 20-40...

Is that being limited from your connection's uplink speed? My uplink is only 100mbit (I can sometimes get as much as 120mbps though). When I connect remotely through wireguard, I have to issue reaching that. I can set to my home connection at whatever the location I'm at has allowed.

I've got my additional services on a Ryzen R9 5900HX mini pc. My router is an N300 mini-pc with 4 network ports. I had trouble configuring wireguard on the router, so it's in a VM on the mini-pc and runs as well as can be expected.

Re: Free DDNS with Cloudflare and a cronjob

#194

Post by eddd-ddde »

rogerpeters wrote: post #32

I'm calling out the elephant in the room - you’re putting way too much faith in these IP lookup services without questioning their obvious ability to screw you over with giving the wrong IP. Is no-one in here able to see this is terrible security??

If you can't trust cloudflare to give you a correct IP how could you trust it as a name server?

Re: Free DDNS with Cloudflare and a cronjob

#195

Post by wibblewobble125 »

janwillemb wrote: post #74
KennyBlanken wrote: post #68

Earlier quoted context omitted.

If someone finds LetsEncrypt challenging, they don't have sufficient network andsystem administrator skills to be running a private, public-facing web server. They should be running tailscale.

Parent did not say it was challenging. I find fiddling with LE tedious because it has to be repeated too often.

I’ve been using caddy for a year which does everything for you. Basically nginx/haproxy but with https built-in via LE, no fiddling about with cert files and brittle LE scripts, also supports subdomains equally easily.

Re: Free DDNS with Cloudflare and a cronjob

#197

Post by max-ibel »

djbusby wrote: post #129
max-ibel wrote: post #117

Did anyone here here set up a good rsyslogd configuration where the receiving syslog collector limits incoming logs to only known ddns machines ? I think I may be able to stitch something together with periodically reconfigured packet filters, but I'd appreciate an existing solution. Bonus points if running on freebsd.

Put a filter on syslog-ng, IIRC that runs on the BSDs

That looks good.

I'd probably prefer doing this at lower layers like pf, since I know how to reload those configs via cron, and since I want to avoid unwanted or malicious packets to even make it to the syslog code.

I was just surprised to find no recipe online, it's apparently more of a niche case than I thought. Worth documenting, probably.

Re: Free DDNS with Cloudflare and a cronjob

#198

Post by graton »

tcfhgj wrote: post #196
graton wrote: post #193

Earlier quoted context omitted.

I'll agree to disagree :)

I.e. you agree to deny reality https://superuser.com/questions/468727/how-to-get-the-ipv6-i...

As I've said before. The server behind the router does not have a public IPv6 address. It is NATed to the Internet. Getting the internal IPv6 address is useless for this case.

I do not like to have the servers/computers that are on the internal home network directly connected to the Internet.

Re: Free DDNS with Cloudflare and a cronjob

#199

Post by tcfhgj »

graton wrote: post #198
tcfhgj wrote: post #196

Earlier quoted context omitted.

I.e. you agree to deny reality https://superuser.com/questions/468727/how-to-get-the-ipv6-i...

As I've said before. The server behind the router does not have a public IPv6 address. It is NATed to the Internet. Getting the internal IPv6 address is useless for this case. I do not like to have the servers/computers that are on the internal home network directly connected to the Internet.

Nating in the context of ipv6 is not a common thing. It is the exception, while it's the rule for ipv4

Re: Free DDNS with Cloudflare and a cronjob

#200

Post by rogerpeters »

eddd-ddde wrote: post #194
rogerpeters wrote: post #32

I'm calling out the elephant in the room - you’re putting way too much faith in these IP lookup services without questioning their obvious ability to screw you over with giving the wrong IP. Is no-one in here able to see this is terrible security??

If you can't trust cloudflare to give you a correct IP how could you trust it as a name server?

The script was not using Cloudlfare to grab the IP, it was using iptools website. Plus, it doesn’t even need to be malicious - it can simply hive you the wrong IP. I know this because I ran a script querying 40 different sites which provided the IP address, and I found at least 4 of them giving incorrect IP addresses over the course of 24 hours. This is why you shouldn’t trust any single source, but compare multiple different sources and THEN update cloudflare with the IP. You see?
Post reply on HN