From owner-freebsd-questions@FreeBSD.ORG Tue Jun 27 12:06:13 2006 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00AC916A412 for ; Tue, 27 Jun 2006 12:06:13 +0000 (UTC) (envelope-from kyrreny@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9116A43D49 for ; Tue, 27 Jun 2006 12:06:12 +0000 (GMT) (envelope-from kyrreny@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0J1I005FEPMB7R00@osl1smout1.broadpark.no> for questions@freebsd.org; Tue, 27 Jun 2006 14:06:11 +0200 (CEST) Received: from urban.broadpark.no ([80.203.212.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0J1I000GAPMBS0W4@osl1sminn1.broadpark.no> for questions@freebsd.org; Tue, 27 Jun 2006 14:06:11 +0200 (CEST) Date: Tue, 27 Jun 2006 14:06:22 +0200 From: Kyrre Nygard To: questions@freebsd.org Message-id: <7.0.1.0.2.20060627135153.021cece8@broadpark.no> Message-id: <7.0.1.0.2.20060626152226.022d4b38@broadpark.no> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT Cc: Subject: named: invalid rndc key X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2006 12:06:13 -0000 Hello! I just tried reloading my nameserver after adding a new domain (zonefile). But then this happened: $ rndc reload rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. I've tried using rndc-confgen to create a new rndc.key, as well as rndc.conf and references in named.conf, but the problem is still there. I've been using my nameserver setup for months and it's all been working smooth. I've made no incremental changes that would result in this thing either. Thanks, Kyrre