@geerlingguy we don't yet know that the CS goof wasn't caused by a DNS problem internally!