News for hackers. Stuff that matters.
Re:WireGuard is now in Linus' tree by RL_Quine on Tuesday January 28, 2020 @10:41PM (#22177128)
For most people it's dynamic. Mine is dynamic with the PPPoE fibre session.
Re:WireGuard is now in Linus' tree by Polylactic_acid on Tuesday January 28, 2020 @11:36PM (#22177483)
I have a rpi set up with a minutely cron job to update my domain name to point to home. Works pretty well. At the worst you lose connection for a minute but usually the IP address only changes when the home connection fails which can take more than a minute to reset anyway.
Re:WireGuard is now in Linus' tree by core-questions on Wednesday January 29, 2020 @01:29AM (#22178000)
Isn't this what the DynDNS protocol and various daemons are for? Why write your own? :P
Re:WireGuard is now in Linus' tree by input_sh on Wednesday January 29, 2020 @01:42AM (#22178070)
That's precisely how they work. You install a client that pings their server. They see if there's an IP address change and switch the A DNS record.

If your DNS provider has an API, this is probably the very first example in the docs.

Re:WireGuard is now in Linus' tree by gjhr on Wednesday January 29, 2020 @04:08AM (#22178719)
Why not? It is pretty simple and very fun! My first project in golang was a program that polled for the machine's IP address and updated a AWS Route53 record.
Re:WireGuard is now in Linus' tree by canofbars on Wednesday January 29, 2020 @05:04AM (#22179004)
Its not exactly "write your own" I have a single line in my crontab that just uses curl to post to a url and the remote server takes the IP address it got the request from and sets the dns to that.
Re:WireGuard is now in Linus' tree by cbzbc on Wednesday January 29, 2020 @06:33AM (#22179447)
Though usually on firmware like openwrt the request going out is tied to a particular interface going up (and down) as it should be, so its somewhat more robust and 'correct' than crontab would be.
Re:WireGuard is now in Linus' tree by CrazyStat on Tuesday January 28, 2020 @11:14PM (#22177369)
Dynamic in theory, but for many people the IP is unchanged for a long time. I remember reading an article that said the average length of time between dynamic IP changes tracked by some company was something like seven months, though I can't find it now.

I have cable with a theoretically dynamic DNS but it's changed once in >4 years.

Re:WireGuard is now in Linus' tree by 3xblah on Tuesday January 28, 2020 @11:38PM (#22177498)
Can you be sure that during 4yrs it never changed >1 even for a short time, maybe hours or days, then reverted back
Re:WireGuard is now in Linus' tree by marcan_42 on Wednesday January 29, 2020 @12:02AM (#22177612)
That's not really a thing. The pools are large-ish; the chances of winding back on the same IP after a change are tiny.
Re:WireGuard is now in Linus' tree by 3xblah on Wednesday January 29, 2020 @04:37AM (#22178871)
Not speaking for all ISPs worldwide.
Re:WireGuard is now in Linus' tree by 3xblah on Wednesday January 29, 2020 @05:39AM (#22179157)
Maybe running dynamic DNS client that keeps logs of IP address changes. Do DDNS clients keep logs. Maybe passive DNS would detect changes.

The point of the comment was that cannot just assume it never changed unless monitoring it contiuously.

Re:WireGuard is now in Linus' tree by makapuf on Wednesday January 29, 2020 @02:18AM (#22178244)
Well if you don't notice it, for a home vpn, well... you wont notice it.