On 2020-04-07 03:51, Andy Burns wrote:
T wrote:

Follow up.Â* The customer uses drop box,
so I am writing a raku program on his RDP server
to upload his WAN IP to Dropbox once an hour
and another program on his RDP client to read
the drop box file and wrap mstsc and WFree RDP
with his server's WAN address.

if only RFC2136 was more widely supported, instead of all the
mickey-mouse dyndns providers.

https://en.wikipedia.org/wiki/Dynamic_DNS:

Dynamic DNS (DDNS) is a method of automatically
updating a name server in the Domain Name Server
(DNS), often in real time, with the active DDNS
configuration of its configured hostnames, addresses
or other information.

The term is used to describe two different concepts.
The first is "dynamic DNS updating" which refers to
systems that are used to update traditional DNS
records without manual editing. These mechanisms
are explained in RFC 2136, and use the TSIG mechanism
to provide security. The second kind of dynamic DNS
permits lightweight and immediate updates often using
an update client, which do not use the RFC2136 standard
for updating DNS records. These clients provide a
persistent addressing method for devices that change
their location, configuration or IP address frequently.

I actually do this on my Linux servers that I have a caching
name server running. I link bind (dns) with DHCP and
update the local DHCP with anyone who gets a new IP
address, but obviously only on the local network.

I once mistakenly allow my caching name server out on
the Internet. Some poor guy with a host name the
same as on my local area network got grabbed and was
given a local IP. But only for about an hour.
How he managed to see my DNS is a mystery to me.
Poor guy must have thought he was losing his mind.

Chuckle.