From owner-freebsd-stable Sun Jan 16 12:22:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 7E9B315035 for ; Sun, 16 Jan 2000 12:22:33 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id MAA11546; Sun, 16 Jan 2000 12:45:21 -0800 (PST) Date: Sun, 16 Jan 2000 12:45:21 -0800 From: Alfred Perlstein To: matt Cc: freebsd-stable@FreeBSD.ORG Subject: Re: bind related freebsd-stable question. Message-ID: <20000116124521.D508@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from matt@ARPA.MAIL.NET on Sun, Jan 16, 2000 at 01:54:17PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * matt [000116 11:18] wrote: > > Hi, > > I'm running bind 8.2.2-p5 on a machine that has a large amount of IPs > bound to it. Instead of having bind listen on all interfaces, I set it > to listen to one ip via listen-to option. > > When I did this, certain braindead things like IRCd stopped working, even > though I had /etc/resolv.conf set to the IP I was making bind listen on, > it seems that trying to do something like, dig @0.0.0.0 does not work > unless bind is listening on all interfaces. This is a problem I need to > get worked out. The machine is 3.4-STABLE, with about 200 IPs bound to it. > > Any ideas? Also, I realize this post is somewhat off-topic, but I couldn't > think of anyone else to ask, allow me to apologize ahead of time for the > somewhat off-topic post. Thank you. Try adding 127.0.0.1 as one of bind's listen-to options? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message