Home/Notes/A practical look at DNS TTL for an accountant
A practical look at DNS TTL for an accountant
13 Jul 2025
How an accountant 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 an accountant.
We document DNS TTL in a shared spreadsheet. It is not glamorous, but an accountant can open it on their phone at midnight if something breaks.
When an accountant asked for a quote on DNS TTL, we sent a one-paragraph email instead of a slide deck. They signed the same day.
We do not start with a platform when handling DNS TTL. We write down who types what, who gets the mail, and what must not get lost. That list is always shorter than a vendor pitch deck.
We billed an accountant two hours for DNS TTL. The previous agency billed forty hours and left a staging URL left in the sitemap behind. Complexity is not expertise.
DNS propagation is not instant, but it is not magic either. We explained to an accountant that the TTL on the old DNS TTL record was 86 400 seconds — twenty-four hours.
A form that collects data for an accountant 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.
The worst DNS TTL failure we have seen at an accountant was invisible for eight months. The backup existed but had never been tested, and the data inside was three migrations old.
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