Home/Notes/How a small hotel should handle DNS TTL
How a small hotel should handle DNS TTL
5 Apr 2026
How a small hotel deals with DNS TTL — and what usually goes wrong.
The problem: a backup that was never restored as a drill. This is where DNS TTL breaks for a small hotel.
A free certificate and a correct DNS TTL record will do more for a small hotel than a redesign that ships with a backup that was never restored as a drill still in place.
Fixing DNS TTL cost less than the lunch meeting where a small hotel decided to wait another quarter. Waiting is never free.
When a small hotel asked for a quote on DNS TTL, we sent a one-paragraph email instead of a slide deck. They signed the same day.
Early on we tried to automate DNS TTL for a small hotel with a cron job. It ran as root, silently overwrote a manual change, and took down their mail. Lesson learned.
The vendor promised a small hotel that DNS TTL was handled. We verified: it was not. Trust but verify has saved more uptime than any product we have used.
We rotate API keys for DNS TTL annually. a small hotel did not see the point until we showed them the access log: the old key had been used from an IP in a country nobody on their team has visited.
A form that collects data for a small hotel 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.
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