Re: rndc stalls on any command -- maybe because 127.0.0.1 is not in routing table?

27.255.255.255 IPADDR_2=127.0.0.2/8 STARTMODE=onboot USERCONTROL=no FIREWALL=no On Sun, Jan 24, 2010 at 11:19 AM, Rick Dicaire wrote: > Is lo up? > Is named actually listening on 127.0.0.1:953? > Is there a firewall? > > On Sun, Jan 24, 2010 at 1:29 PM, Nicholas Tung wrote: >> H

rndc stalls on any command -- maybe because 127.0.0.1 is not in routing table?

Hi all, The rndc tool, which is used for all BIND configuration (yast, /etc/init.d/named stop), appears to stall on any command. See [Listing 1] for output before it stalls ("freezes" not in the DNS zone sense) and [Listing 2] for afterwards. I used lsof to show the open files [Listing 3]