Home/Notes/A practical look at www redirects for a roofing crew
A practical look at www redirects for a roofing crew
23 Feb 2024
How a roofing crew deals with www redirects — and what usually goes wrong.
The problem: nameservers that still list a freelancer. This is where www redirects breaks for a roofing crew.
We moved www redirects for a roofing crew to a provider that supports DNSSEC. It added five minutes to the migration and closed a class of attacks they did not even know about.
We run a monthly diff on DNS for a roofing crew. If a record changes and nobody in the team made the change, we get an alert. nameservers that still list a freelancer was caught this way last quarter.
Related work on this site follows the same principle: one job, a real inbox, no theatre. a roofing crew did not need four analytics dashboards to know that Tuesdays are slow.
When a roofing crew moved hosts, the outage was not the new box — it was nameservers that still list a freelancer. We keep TTL short the week of a move, then raise it once everything is stable.
Maintenance is not glamorous, but it is the reason a roofing crew has not had downtime since we took over www redirects. The invoice is small and the peace of mind is large.
We keep a playbook for www redirects. 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