Home/Notes/Managing CAA records at a language school
Managing CAA records at a language school
3 Sep 2026
How a language school deals with CAA records — and what usually goes wrong.
The problem: a robots.txt that disallows the blog. This is where CAA records breaks for a language school.
DNS propagation is not instant, but it is not magic either. We explained to a language school that the TTL on the old CAA records record was 86 400 seconds — twenty-four hours.
We rotate API keys for CAA records annually. a language school 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.
Launch day for a language school is usually light. Week three is when leftover tags, fonts, and staging URLs show up. a robots.txt that disallows the blog is the usual passenger.
The hosting bill for a language school is twelve dollars a month. Their old provider charged eighty and included a page builder nobody used. CAA records was broken on both plans.
Instead of migrating CAA records all at once, we ran both configurations in parallel for a week. The switch happened on a Wednesday morning — the quietest traffic window.
The real issue was not CAA records itself — it was a robots.txt that disallows the blog. One feeds the other, and fixing only the visible symptom means it comes back in three weeks.
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