Home/Notes/A practical look at A records for a restaurant
A practical look at A records for a restaurant
21 Oct 2024
How a restaurant deals with A records — and what usually goes wrong.
The problem: a www record that disagrees with the apex. This is where A records breaks for a restaurant.
When we onboard a restaurant, the first thing we check is A records. It tells us more about the previous provider than any sales call.
The most expensive outage for a restaurant was not a hack — it was a www record that disagrees with the apex. Nobody attacked anything. The config just drifted.
The vendor promised a restaurant that A records was handled. We verified: it was not. Trust but verify has saved more uptime than any product we have used.
The fix was to delete the old entry, wait for TTL to expire, and re-add A records with the correct value. We scheduled it for 3 AM so nobody lost traffic.
When a restaurant moved hosts, the outage was not the new box — it was a www record that disagrees with the apex. We keep TTL short the week of a move, then raise it once everything is stable.
Big agencies solve A records with a team. We solve it with a checklist and a dig command. The result is the same; the invoice is shorter.
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