From: "Massimo S." Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTPS id 297148 for ecs-isp@2rosenthals.com; Fri, 24 Jan 2020 14:31:32 -0500 Received: from [192.168.200.201] (port=44910 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1iv4g2-0003Mz-0O for ecs-isp@2rosenthals.com; Fri, 24 Jan 2020 14:31:34 -0500 Received: from mail2.quasarbbs.net ([80.86.52.115]:10148) by mail2.2rosenthals.com with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1iv4b9-0006jA-1K for ecs-isp@2rosenthals.com; Fri, 24 Jan 2020 14:26:31 -0500 Received: from [192.168.10.199] (dtp [192.168.10.199]) by srv2 (Weasel v2.71) for ; 24 Jan 2020 20:26:27 X-CTCH-RefID: str=0001.0A02020B.5E2B44E7.0044,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 Reply-To: ml@ecomstation.it Subject: Re: [eCS-ISP] GoDaddy DDNS To: eCS ISP Mailing List References: Organization: eComStation dot it Message-ID: Date: Fri, 24 Jan 2020 20:26:26 +0100 User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; it-IT; rv:1.7.13) Gecko/20060424 Thunderbird/1.0.8 Mnenhy/0.7.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: it-IT Content-Transfer-Encoding: 8bit Il 24/01/2020 20:18, Al Savage ha scritto: > Perhaps I'm misunderstanding something in this DDNS discussion . . . it > all sounds so difficult.  Maybe I've got it easy?  Perhaps I am not > doing things professionally? > > I have a hobby server, which was OS/2-based from 1997 until last year. > My (several) domain names are defined by dyn.com (formerly dyndns, now > Oracle), for about twenty years.  I pay $15/year (I think).  That gets > me basic DNS<->IP lookup.  I have residential broadband service, whose > IP changes on a whim: it may remain the same for six months, or change > three times in a day. > > When I was an OS/2 shop, I ran a java client that monitored changes to > the WAN IP, and it used the dyndns API to update my IP in their DNS, > which propagated out to other DNSs.  This worked well for around fifteen > years. > > Then, I changed to a router that offered to do this service on its own, > so I disabled the OS/2 java client and used the router to update my IP > with dyndns' DNS.  Since a year or so ago, that got flaky (probably a > change in dyndns' API, and my old hardware router had no firmware update > available), so I now use a Linux client (supplied as a Debian package, I > believe) on a local Ubuntu server to manage the IP updates to dyndns. > > Is what you're discussing some variation of what I'm doing with $15/year > dyn.com and a free Debian IP updater client?  Or something else? > > -- > Regards, > Al Savage in Italy with about 15$ per year you get a static IP massimo