Date: Fri, 26 Jul 1996 16:25:34 +0000 From: "Ian Kallen" <ian@gamespot.com> To: rich@oester.com Cc: questions@freebsd.org Subject: Re: named and arpresolve problems Message-ID: <199607261620.QAA00318@gamespot.com>
next in thread | raw e-mail | index | archive | help
Hi, thanks! Well, I went back to the kernel config I was using before the migration and it still won't work -- I can query the nameserver from other hosts, but I nor processes on the machine can "look itself up" -- it's like something changed in the way loopbacks work or something since 2.1. ifconfig -a reports for the loopback: lo0: flags=8008<LOOPBACK,MULTICAST> mtu 16384 hmm, does'nt say that it UP in <brackets> like I believe it should. Any more ideas?! TIA! > Date: Fri, 26 Jul 1996 15:19:26 -0700 > From: "G.R.Gircys" <rich@oester.com> > Reply-to: rich@oester.com > Organization: Oesterreich & Assc. Inc. > To: ian@gamespot.com > Subject: Re: named and arpresolve problems > Ian Kallen wrote: > > > > Hi there, > > Since installing 2.1.5 and compiling a streamlined kernel, I'm > > Try running with the generic kernel and I bet things will work. > > > repeatedly plagued with the message: > > /kernel: arpresolve: can't allocate llinfo for 127.0.0.1 > > Now named is running but I can't query it with nslookup -- I don't > > There is nothing wrong with named - you are getting a kernel error; > try the generic kernel and then check your streamlined rebuild. Sounds > to me you over streamlined - something is really broken in the network layer > if you can't use nslookup. > > rich > > > really know how to interpret the results of a netstat -nr but > > ifconfig -a reports that there is a loopback interface. I'm pretty > > confused by all this! There should'nt be any other machines sending > > arp requests (there's no other machines on this ethernet segment -- > > it just goes to the router) -- this problem only started with my > > system rebuilt. Is there something weird in the new (2.1.5 stable) named > > binary? > > > > It was suggested to me that I: > > >... find the broken machine that's broadcasting ARP requests for the > > >loopback address, and turn it off. > > > > I'm not clear on how to track that down -- again, this is the only > > machine on this ehternet segment. Thanks for any help you can offer! > > > > Ian Kallen ian@gamespot.com > > Director of Technology & Web Administration > > http://www.gamespot.com > > Ian Kallen ian@gamespot.com Director of Technology & Web Administration http://www.gamespot.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607261620.QAA00318>