Take a look at this article... it confirms that Mavericks is still using BIND and has tips on editing via command line.
Any BIND startup errors should be logged here
It should detaill the zone file and specific issue.
When the Server app can't parse the config and zone files - your only choice it to manually clean them up or copy named.conf and the zone files from a working machine.
You'll also find some utilities that check your bind config and zone files located at