DNS needs restart twice

Question

I needed to delete a domain from my primary DNS.
In order to do so, I removed the matching entry from named.conf and also the zone file. Then stopped DNS service and restarted it using the serveradmin command.
Upon the first restart, the DNS service still showed "stopped". When I then restart the DNS another time, it seems to work.
On SA it is the same: Pushing the button to stop the service disables DNS, but to enable DNS again, it is necessary to press the "Start service" button twice.
The log file shows these two lines that may be affiliated with the problem:
Jan 11 00:00:11.650 dnsrdatafromtext: db.194.77.100.zone:2: near eol: unexpected end of input
Jan 11 00:00:11.650 zone 100.77.194.in-addr.arpa/IN: loading master file db.194.77.100.zone: unexpected end of input
Beside of removing the domain entry from named.conf I don't changed anything on other entries or the above mentioned db.194.77.100.zone file overall.
Is this something I have to live with, is it anything bad or all okay ?
By the way, all I did yesterday was to repair permissions on the boot volume. But beside this, nothing else was done.

Answer 1

Before and after the "100.77.194..."-zone are other domain zones. Not sure what kind of information you requested, but here is all content of named.conf, except domain zones:
From beginning of the named.conf file till the first zone, it shows:
// Include keys file
include "/etc/rndc.key";
// Declares control channels to be used by the rndc utility.
// It is recommended that 127.0.0.1 be the only address used.
// This also allows non-privileged users on the local host to manage
// your name server.
// Default controls
controls {
inet 127.0.0.1 port 54 allow {any;} keys {
"rndc-key";
options {
directory "/var/named";
recursion false;
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
// query-source address * port 53;
// a caching only nameserver config
zone "." IN {
type hint;
file "named.ca";
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
Then the first domain zone starts.
After my custom zones, this appears:
logging {
category default {
defaultlog;
channel defaultlog {
file "/Library/Logs/named.log";
severity info;
print-time yes;
Not sure if this is the information you need. Just let me know.