Home/Notes/Managing DNS TTL at a photo studio
Managing DNS TTL at a photo studio
18 Oct 2024
How a photo studio deals with DNS TTL — and what usually goes wrong.
The problem: TTL of 300 seconds. This is where DNS TTL breaks for a photo studio.
HTTPS is table stakes, but DNS TTL is where trust actually lives for a photo studio. A padlock with a misconfigured record behind it is decoration, not security.
a photo studio did not want to hear about DNS TTL. They wanted to know: will the site work tomorrow morning. The answer was yes, but only if we fix TTL of 300 seconds today.
A form that collects data for a photo studio should say where the message goes. Nine fields and a captcha on a quiet Tuesday will cost you the person who actually wanted to pay.
Automate DNS TTL if you can. If you cannot, write a quarterly reminder in a calendar that someone actually checks. TTL of 300 seconds is what happens when nobody does either.
a photo studio asked us to look at DNS TTL after a customer screenshot showed a browser warning. The fix took eleven minutes; finding the cause took two hours.
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