It initially was designed to replace perl/bash based sets of maintenance scripts that made deployment and upkeep of large DNS systems time-consuming and prone to human error.
[1] mysqlBind (now unxsBind) centralizes all data in a replicated SQL database and limits any DNS configuration errors to one software package failure point.
This non-reliance on a live SQL database has been a major point for reliable deployment of large scale DNS services.
[2] unxsBind is based on a "Company/Organization-Contact-Role" login and permissions model, such that end user organization contacts can manage their own DNS data from a shared infrastructure.
For example, a DNS service provider branded AJAX based interface with punycode hostname conversion for IDNA support.