Home/Notes/How a florist should handle DNS TTL
How a florist should handle DNS TTL
25 Feb 2026
How a florist deals with DNS TTL — and what usually goes wrong.
The problem: a staging URL left in the sitemap. This is where DNS TTL breaks for a florist.
We moved DNS TTL for a florist to a provider that supports DNSSEC. It added five minutes to the migration and closed a class of attacks they did not even know about.
We underestimated how long DNS TTL migration would take for a florist. The estimate was two hours; the reality was a full day because a staging URL left in the sitemap had never been documented.
A free certificate and a correct DNS TTL record will do more for a florist than a redesign that ships with a staging URL left in the sitemap still in place.
We solved DNS TTL for a florist by moving it behind a reverse proxy. The old configuration stayed live as a fallback for forty-eight hours, then we pulled it.
We keep a playbook for DNS TTL. Step one is always the same: pull the live record with dig, compare it to what the admin panel shows, and fix the mismatch.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com