2 Sep
2018
2 Sep
'18
4:20 a.m.
On 2018-Aug-31 11:33:19 -0600, Grant Taylor via COFF <coff(a)minnie.tuhs.org> wrote:
On 08/31/2018 10:24 AM, Cornelius Keck wrote:
My approach is a script on the client system (that has dynamic address) that
compares its external address with its address in DNS. If they differ, it
sends an update to the DNS server. The script is hooked into dhclient so
it's invoked when the address is updated or renewed.
The "DNS server" is a hack I've added to Iodine[1] - for an "A"
lookup, it
does a readlink(2) of the FQDN in a config directory and treats the target
as an IPv4 address[2]. This FQDN is within a subdomain I've delegated to
Iodine - I have a CNAME pointing into the subdomain. The client updates the
symlink by SSHing to the DNS server host and running a command that takes
the domain name and address and updates the symlink.
Whilst I've managed to get a static address at home, I still find it useful
for VPSs where the address is static whilst the instance is running but not
preserved across rebuilds.
As an example, lookup gce1.rulingia.com.
[1] http://code.kryo.se/iodine/
[2] This is good enough because Australian ISPs don't believe in IPv6
--
Peter Jeremy
But, I liked the way to have physical control
over my setup, still do,
so there was, is no reason to switch at this time. Given different
circumstances, I might.
I've actually seen / discussed some options to combine the static IP
that you get with inexpensive VPSs with the only dynamic nature of some
residential connections.