From owner-freebsd-hackers Wed Dec 13 21:11:26 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA03939 for hackers-outgoing; Wed, 13 Dec 1995 21:11:26 -0800 (PST) Received: from suphys.physics.usyd.edu.au (dawes@suphys.physics.usyd.edu.au [129.78.129.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA03904 Wed, 13 Dec 1995 21:11:13 -0800 (PST) Received: (from dawes@localhost) by suphys.physics.usyd.edu.au (8.6.12/8.6.12) id QAA27518; Thu, 14 Dec 1995 16:05:20 +1100 From: David Dawes Message-Id: <199512140505.QAA27518@suphys.physics.usyd.edu.au> Subject: Re: loopback and multicast messed up on /etc/sysconfig ? To: chuckr@glue.umd.edu (Chuck Robey) Date: Thu, 14 Dec 1995 16:05:19 +1100 (EST) Cc: joerg_wunsch@uriah.heep.sax.de, mango@communique.net, hackers@freefall.freebsd.org, questions@freefall.freebsd.org In-Reply-To: from "Chuck Robey" at Dec 13, 95 10:23:05 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG Precedence: bulk >On Wed, 13 Dec 1995, J Wunsch wrote: > >> As Raul Zighelboim wrote: >> > >> > # route_multicast="224.0.0.0 -netmask 0xf0000000 -interface ${hostname}" >> > # route_loopback="${hostname} localhost" >> > >> > If I uncomment this line in sysconfig, the system will not boot. >> > (attaching a monitor/keyboard to the pc will allowed me to continue the >> > boot process by typing -C, but no multicast nor loopback oute will >> > exist. >> >> Are you using /etc/resolv.conf? Does your nameserver respond to the >> reverse query for 224.0.0.0? Did you wait 45 seconds for the DNS >> request timing out? >> > >I've been silently a victim of this for a long time. I have a private, 2 >machine network, with one machine doing a nameserver, the other >resolver. Could you suggest a line for the nameserver that would >eliminate this? I'd really appreciate it. > >I _never_ realized it might be a multicast thing .... I've seen this too. I added something equivalent to localhost.rev for multicast. In named.boot I have: primary 0.0.224.IN-ADDR.ARPA multicast.rev and multicast.rev has the following in addition to the SOA, and NS records: 0 IN PTR multicast.. I haven't had any problems since doing this. David