How a language school should handle nameservers

The real issue was not nameservers itself — it was identical titles on every inner page. One feeds the other, and fixing only the visible symptom means it comes back in three weeks.

We quoted a language school half what the other firm did because we did not propose features they did not ask for. The scope was nameservers, not a rebrand.

a language school did not need a portal. They needed a page that said who they are, what they do, and a phone number that somebody picks up before the fifth ring.

The chain of trust for nameservers starts at the registrar. If the registrar account uses an email nobody reads, every downstream fix is temporary.

Crawlers and people want the same thing from nameservers: one URL, a title that matches the heading, and a next link that goes somewhere real.

The worst nameservers failure we have seen at a language school was invisible for eight months. The backup existed but had never been tested, and the data inside was three migrations old.

When we reviewed nameservers, the DNS panel showed identical titles on every inner page. Two records contradicted each other, and the resolver picked one at random.

More notes

Related notes

• A practical look at nameservers for a hardware store
• Why nameservers matters for a marina
• A practical look at nameservers for a roofing crew
• Managing nameservers at a print shop