Dyn Update API Certificate Replacement: Update Client Impact (April 9, 2026)

Update timeline

1. monitoring Apr 08, 2026, 05:48 PM UTC

   [[update_1775758197 class="lifecycle_message_update"]] [[update_status]]Extended[[/update_status]] [[update_text]]The update is completed. This post will remain active as a notice of options for customers.[[/update_text]] [[update_ts class="timestamp" data-ts=1775759669601 ]]April 09, 18:34 UTC (14:34 EDT)[[/update_ts]] [[/update_1775758197]] [[update_1775669821 class="lifecycle_message_update"]] [[update_status]]Scheduled[[/update_status]] [[update_text]]On April 9, 2026 , we will replace the certificate used by the Dyn Update API endpoint at https://members.dyndns.org/ ahead of its expiration, as part of preparation for an upcoming root certificate update. This change is necessary because DigiCert G1 SHA-1 rooted certificates will no longer be trusted by major browsers and related trust stores beginning April 15, 2026 . The current certificate could not be renewed past that date without causing compatibility issues. Who may be affected Customers using Dyn Updater Client v5 may need to take action. Available options Choose one of the following update methods: Use the NEW web-based Dyn Updater v6 (Simplest solution) https://updater.dyn.com Manually update the v5 certificate store and continue using v5 temporarily https://help.dyn.com/update-client-certificate-workaround.html Use a script and scheduler alternative Windows: https://help.dyn.com/windows-task-scheduler-ddns-cli-guide.html macOS / Linux: https://help.dyn.com/macos-ubuntu-cron-ddns-cli-guide.html Additional background and troubleshooting https://help.dyn.com/update-client-faqs.html Important Use only one update method per hostname at a time to avoid unnecessary updates or possible hostname blocks. Customers with questions are encouraged to reach out to Dyn Customer Support. [[/update_text]] [[update_ts class="timestamp" data-ts=1775670504160 ]]April 08, 17:48 UTC (13:48 EDT)[[/update_ts]] [[/update_1775669821]]