From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <46F2160A.8050501@diyaorg.dp.ua> Date: Thu, 20 Sep 2007 09:41:14 +0300 From: Roman Savochenko User-Agent: Thunderbird 2.0.0.6 (X11/20070804) MIME-Version: 1.0 To: sysadmins Content-Type: multipart/mixed; boundary="------------000509050501010509080108" X-Virus-Scanned: amavisd-new at localhost Subject: [Sysadmins] =?koi8-u?b?QmluZDog8NLFy9LB3cXOycUg0NLP08zV28nXwc7J?= =?koi8-u?b?0SDXzsXbzsXHzyDJztTF0sbFytPBINDP08zFINfSxc3Fzs7Px88gxcfPIMnT?= =?koi8-u?b?3sXazs/Xxc7J0S4=?= X-BeenThere: sysadmins@lists.altlinux.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: ALT Linux sysadmin discuss List-Id: ALT Linux sysadmin discuss List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Sep 2007 06:41:25 -0000 Archived-At: List-Archive: This is a multi-part message in MIME format. --------------000509050501010509080108 Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 8bit Приветствую Всех Имеется 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 прикладываю. С уважением, Роман --------------000509050501010509080108 Content-Type: text/plain; name="named.conf" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="named.conf" acl lan { 192.168.200/2; 192.168.2/24; 127.0.0.1 ; 82.207.88.73; }; options { directory "/zone"; query-source address * port 53; version "no version info"; listen-on { any; }; // listen-on { lan; }; allow-transfer { none; }; allow-recursion { lan; }; forward first; forwarders { 82.207.79.5; 193.110.20.1; 195.24.128.65; }; }; zone "diya.org" { type master; file "diya.org.zone"; }; zone "2.168.192.in-addr.arpa" { type master; file "diya.backname"; }; zone "1.168.192.in-addr.arpa" { type master; file "diya_o.backname"; }; zone "200.168.192.in-addr.arpa" { type master; file "diya_n.backname"; }; zone "diyaorg.dp.ua" { type master; file "diyaorg.dp.ua"; }; --------------000509050501010509080108--