production DNS cutover checklist for small teams

DNS cutovers always sound simpler in the planning meeting than they feel during the actual window. Change the record, wait for propagation, watch traffic move. In practice, one cached resolver, one forgotten subdomain, or one health check pointed at the old host can make the night longer than it needs to be. The checklist I trust now starts days before the cutover, not during it. Lower TTL early…