I changed LIS systems, saved money.
What was really going on: there were a whole bunch of config files, into several of which the installer embedded whatever was the machine IP at install time. Support didn't know exactly how many files there were. Engineering was asked to document them all but for whatever reason were dragging their feet on doing it. My attitude was – why can't we just do a search&replace? Response I got – we can't trust customers/Support to do that without making a mess of it.
Eventually, engineering wrote and shipped a "change machine IP tool" which knew about exactly which config files contained the machine IP. Finally, we had a supported procedure for changing the IP address of the server.
> If you’re a Dyn Managed DNS customer and minimal downtime is acceptable, follow the instructions above to migrate your services to OCI.
> If you’re a Dyn Managed DNS customer and downtime is not acceptable, please check back with us in August when we are planning on having a migration tool available to help avoid downtime.
We happen to be wrapping up a migration to a self-hosted solution, but we chose Dyn because we didn't find "minimal" downtime to be something generally acceptable. [edited this sentence for clarity]
For personal use, it's worth checking out free DNS service from Hurricane Electric, https://dns.he.net/ it includes Dynamic DNS, and Hurricane Electric is probably not going anywhere. I'm not affiliated, but I use their secondaries for my personal domains.
I hear gandi.net's DNS is good.
Dear Customer,
Since Oracle acquired Dyn in 2016 and subsequently acquired Zenedge. The engineering teams have been working diligently to integrate Dyn’s products and network into the Oracle Cloud Infrastructure platform. A majority of Dyn products have now been integrated and upgraded on the Oracle Cloud Infrastructure.
Accordingly, DynDNS Pro/Remote Access is decoupling from the Dyn brand and business unit this summer, and will remain a business unit within Oracle.
Your organization has the right to access and use DynDNS Pro/Remote Access. This product will continue to be available from Oracle without any disruption of service and no action is required on your part at this time.
I think I will install for my personal domains a good chrooted bind (or powerdns) on a couple of public facing linux servers. AT THIS TIME sounds too intimidating to me.
That's a lot better, right? grin ;)
If you are going to treat me the same as any new subscriber, where I have to re-signup, re-add my payment method, export my settings and then import them again, you're asking me to buy all over again.
If you ask me to buy, then I get will reevaluate the relationship, and if it's just as easy to migrate to another supplier I will move.
Migrating internally should have been "push this button to accept the new terms and pricing, you don't even need to talk with your registrar."
I've been a Dyn customer for over a decade, and now I'm moving because it's just as easy to move as it is to stay, and I do not want to have to type in "oracle.com" to manage my service.