Received: (at submit) by bugs.debian.org; 3 Mar 2001 09:45:17 +0000 From dilinger@mp3revolution.net Sat Mar 03 03:45:16 2001 Return-path: Received: from saloma.stu.rpi.edu (incandescent.mp3revolution.net) [::ffff:128.113.199.230] by master.debian.org with smtp (Exim 3.12 1 (Debian)) id 14Z8bE-0001SE-00; Sat, 03 Mar 2001 03:45:16 -0600 Received: (qmail 24254 invoked by uid 1000); 3 Mar 2001 09:45:13 -0000 Date: Sat, 3 Mar 2001 04:45:13 -0500 From: Andres Salomon To: submit@bugs.debian.org Subject: restarting networking does not restart bind Message-ID: <20010303044512.A23798@incandescent.mp3revolution.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i X-Operating-System: Linux incandescent 2.4.2 Delivered-To: submit@bugs.debian.org Package: bind Version: 8.2.3-3 Distribution: testing Bind currently listens on all interfaces that are up when the daemon is brought up; ie: [dilinger@incandescent etc]$ sudo lsof -n|grep LISTEN named 158 root 21u IPv4 178 TCP 127.0.0.1:domain (LISTEN) named 158 root 23u IPv4 180 TCP 128.113.199.230:domain (LISTEN) This would be fine, if bind itself would restart when networking was restarted (/etc/init.d/networking restart); but currently, it does not. If I change eth0's ips in /etc/network/interfaces, and restart networking, bind will continue listening on the old ip (and not the new one), until I manually restart bind. Correct behavior (imo) would be to have the bind package stick a script in netbase's /etc/networking/if-up.d/ directory, which checks if bind is running, and if it is, restart the (name) daemon. -- "... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed." - Unix for Dummies, 2nd Edition -- found in the .sig of Rob Riggs, rriggs@tesser.com