Home/Notes/Managing nameservers at a plant nursery
Managing nameservers at a plant nursery
18 Aug 2026
How a plant nursery deals with nameservers — and what usually goes wrong.
The problem: a form that emails a shared inbox. This is where nameservers breaks for a plant nursery.
Nobody at a plant nursery could remember who had configured nameservers. The credentials were in a text file inside a folder called OLD STUFF on a shared drive.
The vendor portal had silently rotated the key for nameservers, but a plant nursery was still using the old one. Every outbound message bounced quietly.
Fixing nameservers cost less than the lunch meeting where a plant nursery decided to wait another quarter. Waiting is never free.
When we reviewed nameservers, the DNS panel showed a form that emails a shared inbox. Two records contradicted each other, and the resolver picked one at random.
DNS propagation is not instant, but it is not magic either. We explained to a plant nursery that the TTL on the old nameservers record was 86 400 seconds — twenty-four hours.
We check nameservers for a plant nursery once a quarter. It takes five minutes and has caught two problems in the past year. Both would have caused downtime within a week.
Related work on this site follows the same principle: one job, a real inbox, no theatre. a plant nursery did not need four analytics dashboards to know that Tuesdays are slow.
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