Home/Notes/Managing A records at a plant nursery
Managing A records at a plant nursery
25 Mar 2026
How a plant nursery deals with A records — and what usually goes wrong.
The problem: query-string copies of the same page. This is where A records breaks for a plant nursery.
Early on we tried to automate A records for a plant nursery with a cron job. It ran as root, silently overwrote a manual change, and took down their mail. Lesson learned.
After fixing A records, we added a monitoring alert. If the record changes or the certificate approaches expiry, both we and a plant nursery get an email. No surprises.
Nobody at a plant nursery could remember who had configured A records. The credentials were in a text file inside a folder called OLD STUFF on a shared drive.
We hand over a one-page document after every A records job. It says what was changed, what the login is, and what to check if something feels wrong. a plant nursery keeps it in a drawer they actually open.
We run a monthly diff on DNS for a plant nursery. If a record changes and nobody in the team made the change, we get an alert. query-string copies of the same page was caught this way last quarter.
We keep a playbook for A records. Step one is always the same: pull the live record with dig, compare it to what the admin panel shows, and fix the mismatch.
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