Не стартует BIND, никак не аргументируя это

Всем привет! После недавнего апдейта перестал стартовать BIND. Делает он это молча, ничего не говоря.
Выглядит это так:

/etc/init.d/named start

 * Starting named ...                          [ !! ]

при этом в /var/log/message пишется вот это:

Aug 22 15:50:12 bagrincev syslog-ng[32109]: syslog-ng starting up; version='3.1.1'
Aug 22 15:50:19 bagrincev named[32182]: starting BIND 9.4.3-P5 -u named -n 1
Aug 22 15:50:19 bagrincev named[32182]: found 1 CPU, using 1 worker thread
Aug 22 15:50:19 bagrincev named[32182]: using up to 4096 sockets
Aug 22 15:50:19 bagrincev named[32182]: loading configuration from '/etc/bind/named.conf'

Интересно, что, если запустить бинд вот так: named -g -p 53

Сервис стартует, в консоль валится следующее:

22-Aug-2010 15:57:47.594 starting BIND 9.4.3-P5 -g -p 53
22-Aug-2010 15:57:47.594 found 1 CPU, using 1 worker thread
22-Aug-2010 15:57:47.594 using up to 4096 sockets
22-Aug-2010 15:57:47.602 loading configuration from '/etc/bind/named.conf'
22-Aug-2010 15:57:47.603 using default UDP/IPv4 port range: [1024, 65535]
22-Aug-2010 15:57:47.603 using default UDP/IPv6 port range: [1024, 65535]
22-Aug-2010 15:57:47.607 listening on IPv4 interface lo, 127.0.0.1#53
22-Aug-2010 15:57:47.608 listening on IPv4 interface eth1, 192.168.0.1#53
22-Aug-2010 15:57:47.610 listening on IPv4 interface ppp0, 79.120.84.217#53
22-Aug-2010 15:57:47.615 automatic empty zone: 0.IN-ADDR.ARPA
22-Aug-2010 15:57:47.615 automatic empty zone: 254.169.IN-ADDR.ARPA
22-Aug-2010 15:57:47.615 automatic empty zone: 2.0.192.IN-ADDR.ARPA
22-Aug-2010 15:57:47.615 automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
22-Aug-2010 15:57:47.615 automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
22-Aug-2010 15:57:47.615 automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
22-Aug-2010 15:57:47.615 automatic empty zone: D.F.IP6.ARPA
22-Aug-2010 15:57:47.615 automatic empty zone: 8.E.F.IP6.ARPA
22-Aug-2010 15:57:47.616 automatic empty zone: 9.E.F.IP6.ARPA
22-Aug-2010 15:57:47.616 automatic empty zone: A.E.F.IP6.ARPA
22-Aug-2010 15:57:47.616 automatic empty zone: B.E.F.IP6.ARPA
22-Aug-2010 15:57:47.620 command channel listening on 127.0.0.1#953
22-Aug-2010 15:57:47.620 ignoring config file logging statement due to -g option
22-Aug-2010 15:57:47.622 zone 127.in-addr.arpa/IN: loaded serial 2008122601
22-Aug-2010 15:57:47.624 zone zotikov.com/IN: loaded serial 2010013000
22-Aug-2010 15:57:47.625 zone localhost/IN: loaded serial 2008122601
22-Aug-2010 15:57:47.625 zone bagrincev.ru/IN: loaded serial 2010012900
22-Aug-2010 15:57:47.626 zone dasmoke.ru/IN: loaded serial 2009030401
22-Aug-2010 15:57:47.627 zone equieblog.ru/IN: loaded serial 2009072500
22-Aug-2010 15:57:47.628 zone mba-groups.ru/IN: loaded serial 2009072400
22-Aug-2010 15:57:47.631 zone artweb.pp.ru/IN: loaded serial 2010013000
22-Aug-2010 15:57:47.632 zone utrovtebe.ru/IN: loaded serial 2009023101
22-Aug-2010 15:57:47.632 zone woodstore.su/IN: loaded serial 2009012201
22-Aug-2010 15:57:47.633 running
22-Aug-2010 15:57:47.634 zone zotikov.com/IN: sending notifies (serial 2010013000)
22-Aug-2010 15:57:47.638 zone equieblog.ru/IN: sending notifies (serial 2009072500)
22-Aug-2010 15:57:47.638 zone woodstore.su/IN: sending notifies (serial 2009012201)
22-Aug-2010 15:57:47.638 zone dasmoke.ru/IN: sending notifies (serial 2009030401)
22-Aug-2010 15:57:47.638 zone mba-groups.ru/IN: sending notifies (serial 2009072400)
22-Aug-2010 15:57:47.638 zone artweb.pp.ru/IN: sending notifies (serial 2010013000)
22-Aug-2010 15:57:47.639 zone bagrincev.ru/IN: sending notifies (serial 2010012900)
22-Aug-2010 15:57:47.641 zone utrovtebe.ru/IN: sending notifies (serial 2009023101)

Вот /etc/bind/named.conf

options {
	directory "/var/bind";

	// uncomment the following lines to turn on DNS forwarding,
	// and change the forwarding ip address(es) :
	//forward first;
	forwarders {
		212.1.224.34;
		212.1.230.111;
	};

	//listen-on-v6 { none; };
        listen-on { 192.168.0.1; 127.0.0.1; 79.120.84.217; };

	// to allow only specific hosts to use the DNS server:
	//allow-query {
	//	127.0.0.1;
	//};

	// if you have problems and are behind a firewall:
	//query-source address * port 53;
	pid-file "/var/run/named/named.pid";
};

// Briefly, a zone which has been declared delegation-only will be effectively
// limited to containing NS RRs for subdomains, but no actual data beyond its
// own apex (for example, its SOA RR and apex NS RRset). This can be used to
// filter out "wildcard" or "synthesized" data from NAT boxes or from
// authoritative name servers whose undelegated (in-zone) data is of no
// interest.
// See http://www.isc.org/products/BIND/delegation-only.html for more info

//zone "COM" { type delegation-only; };
//zone "NET" { type delegation-only; };

//zone "." IN {
//	type hint;
//	file "named.ca";
//};

zone "localhost" IN {
	type master;
	file "pri/localhost.zone";
	allow-update { none; };
	notify no;
};

zone "127.in-addr.arpa" IN {
	type master;
	file "pri/127.zone";
	allow-update { none; };
	notify no;
};

zone "bagrincev.ru" IN {
	type master;
	file "pri/bagrincev.ru";
};

zone "woodstore.su" IN {
	type master;
	file "pri/woodstore.su";
};

zone "artweb.pp.ru" IN {
	type master;
	file "pri/artweb.pp.ru";
};

zone "mba-groups.ru" IN {
	type master;
	file "pri/mba-groups.ru";
};

zone "utrovtebe.ru" IN {
        type master;
        file "pri/utrovtebe.ru";
};

zone "dasmoke.ru" IN {
        type master;
        file "pri/dasmoke.ru";
};

zone "zotikov.com" IN {
        type master;
        file "pri/zotikov.com";
};

zone "equieblog.ru" IN {
        type master;
        file "pri/equieblog.ru";
};

named-checkzone и named-checkconf - не выдают ошибок.