Editorial Policy

What we publish and why

We publish practical engineering writing about DNS: resolution behaviour, DNSSEC, anycast, zone management, registrar and registry mechanics, and the operational failure modes we see in the field. It is written to be useful to an infrastructure engineer whether or not they ever hire us.

How we research

DNS is unusually well specified, so we base claims on primary sources: the relevant RFCs, registry and registrar documentation, resolver and authoritative-server implementation docs (BIND, Knot, PowerDNS, Unbound), and published operational guidance. Where behaviour differs between implementations or resolvers, we say so instead of generalising.

Honesty about limits

Caching, negative caching and resolver behaviour mean DNS changes are rarely as instant or as predictable as vendors imply. We are explicit about propagation realities, about the operational cost of DNSSEC, and about cases where the simplest architecture beats the clever one.

No invented numbers

We do not publish statistics, uptime figures, client counts or certifications we cannot substantiate. Where we cite third-party research or benchmarks, we say whose they are and what was measured.

Accuracy and corrections

If we publish something inaccurate, we fix it. Material corrections — anything that changes the meaning or the recommendation — are made promptly and noted on the article rather than quietly edited. Minor fixes are made without a note. Spotted an error? Email [email protected] with the URL and what you believe is wrong. Corrections from practitioners are genuinely welcome.

Use of AI

We may use AI tools to help draft, outline or edit. AI is never the final authority: a person is responsible for every published article, checks its technical claims, and stands behind it. We do not publish unreviewed machine-generated text.

Independence

We name specific software and providers throughout our writing. We do not take payment for a recommendation, and if a commercial relationship ever affected what we wrote about a vendor we would disclose it on that article.

Related: About · Blog · Accessibility