TODO

finish writing FAQ in README
error if you change state from in_use to available for an IP that exists in record.content
set defaults in config file for several settings (like defaults for soa record)
headers to disable automatically creating/modifying domains, soa, ptr records
don't allow deleting of domain until all records are deleted first
validate that content is unique for all PTR records
validate there is only one SOA per domain
don't allow changes to the record if the domain is type SLAVE
write audit job that validates records match domain, valid soa, orphan records, ptr errors, etc
soa serial number should increment date format on change
only update soa once per transaction (or every N minutes?)
only allow delete subnet if all IPs are available
auto create PTR records for AAAA records
auto create SOA record for in-addr-arpa when we add a subnet?
automatically set network, gateway and broadcast as in use
write lots more tests (especially around error handling)
write tests for client library and CLI
document web services API
complete/make usable web UI
update README to explain how there can be multiple A records with same content, but only one ptr per ip
update README to explain relationship between A records content and IP resources
respond with deleted object on delete
command line confirmation for write operations (with --quiet or something to disable)
splitting up base and mask_bits in subnets was a mistake (complete transition to "name")
cli should warn you if you try to create an A record with a name that already exists