Suresh Ramasubramanian writes on 10/12/2003 8:29 PM:
Hi there
We operate webmail services for the .name TLD (MX and DNS resolution are handled by the nic.name people).
An update - forwarding a post to bind-announce
From: Peter Losher <[EMAIL PROTECTED]>Organization: ISC To: [EMAIL PROTECTED] Subject: Update to root-delegation-only exclude statement example. Date: Fri, 10 Oct 2003 09:09:06 -0700 User-Agent: KMail/1.5.3 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Content-Description: clearsigned data Content-Disposition: inline Message-Id: <[EMAIL PROTECTED]> X-Approved-By: [EMAIL PROTECTED] X-ecartis-version: Ecartis v1.0.0 Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] X-original-sender: [EMAIL PROTECTED] Precedence: bulk List-unsubscribe:
<mailto:[EMAIL PROTECTED]>
List-Id: <bind-announce.isc.org> X-List-ID: <bind-announce.isc.org> X-RCPT-TO: <[EMAIL PROTECTED]> X-UIDL: 365476378 Status: U
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
It has come to ISC's attention that there are non-delegation records=20 present in the following zones:
ar id md no name pf tw
Accordingly, we have added them to the list of zones where non-delegation data may be expected. Many administrators will want to include these zones in the "exclude" portion if they use the "root-delegation-only" option. Details may be found at:
http://www.isc.org/products/BIND/delegation-only.html
If you know of any other zones with non-delegation records, please let
us=20
know. =2D --=20 [EMAIL PROTECTED] | ISC | OpenPGP 0xE8048D08 | "The bits must flow" =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQE/htm7PtVx9OgEjQgRAhW2AJ9zNdUwEYHaCejUEP9p7Yb3t6W1EgCfWv/R ce9oyzEIXy6ikxaDvDs5rfo=3D =3DqrK2 =2D----END PGP SIGNATURE-----
