From owner-freebsd-net@FreeBSD.ORG Wed Apr 27 13:28:49 2005 Return-Path: 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 62BDF16A4CE for ; Wed, 27 Apr 2005 13:28:49 +0000 (GMT) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90E3643D45 for ; Wed, 27 Apr 2005 13:28:47 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])j3RDRVSu002276; Wed, 27 Apr 2005 16:27:31 +0300 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) j3RDSjij098818; Wed, 27 Apr 2005 16:28:45 +0300 (EEST) (envelope-from keramida@linux.gr) Received: (from keramida@localhost)j3RDSj3t098813; Wed, 27 Apr 2005 16:28:45 +0300 (EEST) (envelope-from keramida@linux.gr) Date: Wed, 27 Apr 2005 16:28:44 +0300 From: Giorgos Keramidas To: Shyam Shantikumar Message-ID: <20050427132844.GA86820@orion.daedalusnetworks.priv> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: freebsd-net@freebsd.org Subject: Re: errors while starting named X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2005 13:28:49 -0000 On 2005-04-27 14:29, Shyam Shantikumar wrote: > Dear All, > I am getting the following errors when I run /usr/sbin/named > > Named[1398]: could not listen on UDP socket: address in use > Named[1398]: creating IPv4 interface lo0 failed; interface ignored > Named[1398] dns_rdata_fromtext: db.10.1.3.197:4 near '3h': not a valid number > Named[1398]: zone 3.1.10.in-addr.arpa/IN: loading master file db.10.1.3.197: not a valid number > Named[1398]: zone 0.0.127.in-addr.arpa/IN: loading master file db.127.0.0: not a valid number > > Could anyone please tell me how to solve these issues If you are already running named, the correct way to reload the configuration, after making changes to it, is *NOT* to manually run /usr/sbin/named. Try using the rc.d script: # /etc/rc.d/named restart Then, you need to fix the db.10.* zone files, because they have some obvious errors, reported above in your log files.