From owner-freebsd-net@FreeBSD.ORG Thu Jan 26 15:01:54 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 721F716A420 for ; Thu, 26 Jan 2006 15:01:54 +0000 (GMT) (envelope-from subscriber@osk.com.ua) Received: from gandalf.osk.com.ua (osk.com.ua [195.5.17.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9489043D49 for ; Thu, 26 Jan 2006 15:01:53 +0000 (GMT) (envelope-from subscriber@osk.com.ua) Received: from localhost (localhost [127.0.0.1]) by gandalf.osk.com.ua (Postfix) with ESMTP id EF6C878C2A for ; Thu, 26 Jan 2006 17:03:27 +0200 (EET) Received: from gandalf.osk.com.ua ([127.0.0.1]) by localhost (gandalf.osk.com.ua [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52979-07 for ; Thu, 26 Jan 2006 17:03:27 +0200 (EET) Received: from OLEG (unknown [192.168.82.111]) by gandalf.osk.com.ua (Postfix) with ESMTP id 5A24D78C1D for ; Thu, 26 Jan 2006 17:03:27 +0200 (EET) Date: Thu, 26 Jan 2006 17:01:50 +0200 From: Oleg Tarasov X-Mailer: The Bat! (v3.64.01 Christmas Edition) Professional X-Priority: 3 (Normal) Message-ID: <1623226562.20060126170150@osk.com.ua> To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at osk.com.ua Subject: Named could not listen on UDP socket: permission denied X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD MailList List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2006 15:01:54 -0000 Hello, I run FreeBSD 6.0 and I have begun to recieve quite periodic error messages like these: Jan 25 19:45:50 central named[728]: could not listen on UDP socket: permission denied Jan 25 19:45:50 central named[728]: creating IPv4 interface ng0 failed; interface ignored ng0 is my main internet interface and is created on early boot (rcordered like ppp-user) by mpd. Certainly, I need DNS listening on this interface. The reason is that if mpd is restarted for some reason, interface ng0 is destroyed and created again while listener on this interface is destroyed too. Named is chrooted at this time and cannot re-bind listener on this interface. Only manual restart of named helps it bind to this interface. This is not deadly situation as if I manually restart mpd I will be able to restart named too... Running named under root user or out of chroot environment is not quite acceptable way... Please tell me if this problem has a solution other then above -- Best regards, Oleg Tarasov mailto:subscriber@osk.com.ua