Thats a error from a kernel security extension and not from bind itself. Do you have apparmor or selinux activated?
Actually those errors showed up at the same time Bind decided not to start anymore, just after adding the other name servers. Nope. Just plain Ubuntu with ISPConfig.
Just tried to start Bind (at 16:33, 2 minutes ago) and guess what we've got in the /var/log/messages Code: Jan 23 14:55:32 minimalist -- MARK -- Jan 23 15:15:32 minimalist -- MARK -- Jan 23 15:35:33 minimalist -- MARK -- Jan 23 15:55:33 minimalist -- MARK -- Jan 23 16:15:33 minimalist -- MARK -- Jan 23 16:33:40 minimalist kernel: [1485758.735570] Failure registering capabilities with primary security module.
OK, we got Bind working again by an old fashioned reboot. We also managed to get all four name servers listed.