From owner-freebsd-isp@FreeBSD.ORG Wed Apr 29 06:51:17 2009 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCCF51065670 for ; Wed, 29 Apr 2009 06:51:17 +0000 (UTC) (envelope-from ml@geoffroy.eu.org) Received: from mail-ew0-f171.google.com (mail-ew0-f171.google.com [209.85.219.171]) by mx1.freebsd.org (Postfix) with ESMTP id 5C2938FC15 for ; Wed, 29 Apr 2009 06:51:16 +0000 (UTC) (envelope-from ml@geoffroy.eu.org) Received: by ewy19 with SMTP id 19so998066ewy.43 for ; Tue, 28 Apr 2009 23:51:16 -0700 (PDT) Received: by 10.210.76.4 with SMTP id y4mr5094756eba.97.1240986509889; Tue, 28 Apr 2009 23:28:29 -0700 (PDT) Received: from tintin.sicfa.net (tintin.sicfa.net [88.191.17.5]) by mx.google.com with ESMTPS id 7sm1145170eyg.27.2009.04.28.23.28.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 28 Apr 2009 23:28:29 -0700 (PDT) Date: Wed, 29 Apr 2009 08:28:27 +0200 From: Geoffroy RIVAT To: freebsd-isp@freebsd.org Message-ID: <20090429062827.GB60404@tintin.sicfa.net> References: <49E3D793.2090008@staff.openaccess.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <49E3D793.2090008@staff.openaccess.org> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: providing web based DNS management to customers X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2009 06:51:18 -0000 Hi Michael, Michael DeMan (OA) wrote: > Hi All, > > What are folks doing for providing web based DNS management to customers? > > I've looked at a lot of open source products over time, but never found > one that was enough to say "Thats it, lets integrate it!". > > It always seems that the tricky part is reverse DNS. PowerDNS and other > tools (at least a few years ago) offered reasonable support for forward > DNS management on a per-user basis, but not reverse, or at least not > reverse in the sense that we only want customers to be able to modify > the reverse DNS of say a single IP, or a subnet, etc. for this I'm using powerdns + poweradmin (but you can use another system) for only 1 IP i do 1.0.168.192.in-addr.arpa IN CNAME reverse.custdomain.tld and reverse.custdomain.tld IN PTR coolreverse.domain.tld. for a subnet : 1.0.168.192.in-addr.arpa IN CNAME 1.reverse.custdomain.tld 2.0.168.192.in-addr.arpa IN CNAME 2.reverse.custdomain.tld 3.0.168.192.in-addr.arpa IN CNAME 3.reverse.custdomain.tld it's explained in an rfc but I can't remember the numbre. Regards, Geo