Currently Being ModeratedNov 15, 2013 7:10 PM (in response to StephenM)
look in /var/named and remove any of your zones
edit /etc/named.conf and remove entries for the zones you've removed.
Currently Being ModeratedNov 15, 2013 7:45 PM (in response to UptimeJeff)
Aren't those bind related? Bind doesn't even ship with 10.9. It has been replaced with scutil, if I remember correctly.
Currently Being ModeratedNov 15, 2013 8:03 PM (in response to StephenM)
Looks like the same old files.. just a new location
both the conf and the zone files are there.
Currently Being ModeratedNov 15, 2013 8:16 PM (in response to UptimeJeff)
Thanks. I'll take a look at that tomorrow.
Currently Being ModeratedNov 16, 2013 7:11 AM (in response to StephenM)
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