Hi - yes, this did unfortunately happen for some servers during this update. It was actually related to a bug in the previously installed djbdns RPM - this update removed the bug, but despite our best efforts, some folks were still hit by it. It definitely won’t be a problem that repeats itself.