Приветствую Всех

Имеется Bind (bind-9.2.4.rc5-alt1) на ALT 2.4, который обслуживает все 
интерфейсы на сервере.
Сервер имеет широкий канал через ADSL, который перманентно откидывается, 
но восстанавливается в течении 10 попыток, за счёт опций pppd: persist и 
maxfail 10.
Однако за время восстановления, bind прекращает слушать этот интерфейс и 
не может возобновить, хотя интерфейс уже успешно поднялся:
Sep 19 16:48:10 server named[17493]: no longer listening on 82.207.88.73#53
Sep 19 17:25:51 server pppd[14092]: pppd 2.4.2 started by root, uid 0
Sep 19 17:25:51 server pppd[14092]: Using interface ppp0
Sep 19 17:25:51 server pppd[14092]: Connect: ppp0 <--> /dev/pts/0
Sep 19 17:25:51 server pppoe[14093]: PPP session is 40528
Sep 19 17:26:01 server pam_tcb[14110]: crond: Session opened for root by 
(uid=0)
Sep 19 17:26:01 server crond[14112]: (root) CMD (/usr/bin/enable lp 
"hp2550(color)")
Sep 19 17:26:02 server pam_tcb[14110]: crond: Session closed for root
Sep 19 17:26:14 server pppd[14092]: PAP authentication succeeded
Sep 19 17:26:14 server pppd[14092]: local  IP address 82.207.88.73
Sep 19 17:26:14 server pppd[14092]: remote IP address 195.5.5.7
Sep 19 17:48:09 server named[17493]: listening on IPv4 interface ppp0, 
82.207.88.73#53
Sep 19 17:48:09 server named[17493]: could not listen on UDP socket: 
permission denied
Sep 19 17:48:09 server named[17493]: creating IPv4 interface ppp0 
failed; interface ignored
Sep 19 18:48:09 server named[17493]: listening on IPv4 interface ppp0, 
82.207.88.73#53
Sep 19 18:48:09 server named[17493]: could not listen on UDP socket: 
permission denied
Sep 19 18:48:09 server named[17493]: creating IPv4 interface ppp0 
failed; interface ignored

Лечит только перезапуск bind:
Sep 19 18:51:46 server named[17493]: shutting down
Sep 19 18:51:47 server named[17493]: no longer listening on 127.0.0.1#53
Sep 19 18:51:47 server named[17493]: no longer listening on 192.168.2.1#53
Sep 19 18:51:47 server named[17493]: no longer listening on 
193.110.21.150#53
Sep 19 18:51:47 server named[17493]: no longer listening on 192.168.200.1#53
Sep 19 18:51:47 server named[17493]: exiting
Sep 19 18:51:47 server bind: named shutdown succeeded
Sep 19 18:51:47 server named[30241]: starting BIND 9.2.4rc5
Sep 19 18:51:47 server named[30241]: using 1 CPU
Sep 19 18:51:47 server bind: named startup succeeded
Sep 19 18:51:47 server named[30241]: loading configuration from 
'/etc/named.conf'
Sep 19 18:51:47 server named[30241]: listening on IPv4 interface lo, 
127.0.0.1#53
Sep 19 18:51:47 server named[30241]: listening on IPv4 interface eth0, 
192.168.2.1#53
Sep 19 18:51:47 server named[30241]: listening on IPv4 interface eth1, 
193.110.21.150#53
Sep 19 18:51:47 server named[30241]: listening on IPv4 interface eth1:0, 
192.168.200.1#53
Sep 19 18:51:47 server named[30241]: listening on IPv4 interface ppp0, 
82.207.88.73#53
Sep 19 18:51:47 server named[30241]: none:0: open: /etc/rndc.key: file 
not found
Sep 19 18:51:47 server named[30241]: couldn't add command channel 
127.0.0.1#953: file not found
Sep 19 18:51:47 server named[30241]: zone 1.168.192.in-addr.arpa/IN: 
loaded serial 5
Sep 19 18:51:47 server named[30241]: zone 2.168.192.in-addr.arpa/IN: 
loaded serial 5
Sep 19 18:51:48 server named[30241]: zone 200.168.192.in-addr.arpa/IN: 
loaded serial 5
Sep 19 18:51:48 server named[30241]: zone diya.org/IN: loaded serial 5
Sep 19 18:51:48 server named[30241]: zone diyaorg.dp.ua/IN: loaded 
serial 2005012410
Sep 19 18:51:48 server named[30241]: running

Как же быть в этой ситуации? Перезапускать bind руками уже достало.
Конфиг bind прикладываю.

С уважением, Роман