From owner-freebsd-questions@FreeBSD.ORG  Wed Feb 17 21:39:35 2010
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 34B2A1065724
	for <freebsd-questions@freebsd.org>;
	Wed, 17 Feb 2010 21:39:35 +0000 (UTC)
	(envelope-from john@dexter.starfire.mn.org)
Received: from dexter.starfire.mn.org (starfire.skypoint.net [173.8.102.29])
	by mx1.freebsd.org (Postfix) with ESMTP id CDA7B8FC16
	for <freebsd-questions@freebsd.org>;
	Wed, 17 Feb 2010 21:39:34 +0000 (UTC)
Received: (from john@localhost)
	by dexter.starfire.mn.org (8.11.3/8.11.3) id o1HLdXp14455
	for freebsd-questions@freebsd.org; Wed, 17 Feb 2010 15:39:33 -0600 (CST)
	(envelope-from john)
Date: Wed, 17 Feb 2010 15:39:33 -0600
From: John <john@starfire.mn.org>
To: freebsd-questions@freebsd.org
Message-ID: <20100217153933.A14400@starfire.mn.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
Subject: Named errors after adding IPv4 alias - solved by restarting named
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Feb 2010 21:39:35 -0000

It seems that if you add an alias to an interface once named is up
and running, it will cause named, on an hourly basis from the time
named was first started (that is, if it was started at 07:32 after
the hour, then every hour after the alias is added at about 07:32
after each hour), named will say:

Feb 16 22:07:32 elwood named[626]: could not listen on UDP socket: permission denied
Feb 16 22:07:32 elwood named[626]: creating IPv4 interface fxp0 failed; interface ignored

A "kill -1" does not help.  If you do a full "stop" and "start" on named,
that will take care of the problem.

Is this something that should be addressed within named, or is this
such a rare event (adding an IP alias on an interface that named is
using) that it should just be let go?
-- 

John Lind
john@starfire.MN.ORG