X-Original-To: pgsql-www-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id A5E8B9FA666 for ; Mon, 11 Sep 2006 04:25:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 40045-01 for ; Mon, 11 Sep 2006 04:25:57 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by postgresql.org (Postfix) with ESMTP id 095BD9FA617 for ; Mon, 11 Sep 2006 04:25:57 -0300 (ADT) Received: from mailgate.vale-housing.co.uk ([194.217.48.34] helo=vale-housing.co.uk) by anchor-post-33.mail.demon.net with esmtp (Exim 4.42) id 1GMgB2-00029J-Bc for pgsql-www@postgresql.org; Mon, 11 Sep 2006 07:25:56 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: Who admins DNS? Date: Mon, 11 Sep 2006 08:25:55 +0100 Message-ID: In-Reply-To: <45046FF1.5020806@commandprompt.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [pgsql-www] Who admins DNS? thread-index: AcbVFHKOnTlntADJR5qDw/m8XPDduAAXqZyw From: "Dave Page" To: "Joshua D. Drake" , "Magnus Hagander" Cc: "Robert Treat" , , X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/59 X-Sequence-Number: 10637 =20 > -----Original Message----- > From: Joshua D. Drake [mailto:jd@commandprompt.com]=20 > Sent: 10 September 2006 21:05 > To: Magnus Hagander > Cc: Dave Page; Robert Treat; pgsql-www@postgresql.org;=20 > josh@agliodbs.com > Subject: Re: [pgsql-www] Who admins DNS? >=20 > >=20 > > I'm *sure* they provide delegation of subdomain, given the customers > > that they have. AFAIK, UltraDNS is a professional *enterprise* DNS > > hoster. But I can be wrong on that ;) > >=20 > > The more interesting question to ask is do they have an API for > > dynamically updating the DNS records. (Maybe just dynamic-dns? If > > security is configure dproperly, that should work, no?) If=20 > it's an API > > we can use, then it can definitly still be a win. Even if they do, it doesn't eliminate the point of failure that went last time - the zone file generation script. > If we are seriously interested in this, CMD is a long term=20 > customer of=20 > theirs. I would be happy to call and see what type of=20 > accomodations they=20 > would be willing to make for us. I don't believe there's any real need thanks. This is the first DNS screw up in over 10 years, and was one I don't expect will be made again. Moving to a whole new provider will undoubtedly cause more pain for little, if any gain. Regards, Dave.