Hi there We operate webmail services for the .name TLD (MX and DNS resolution are handled by the nic.name people). After the recent Verisign brouhaha, several of y'all patched their nameservers to stop believing Verisign (so did we). Just that quite a few of you also seem to have set up your resolvers to do the same thing with other wildcarded TLDs. .name is a wildcarded TLD and does have legit domains on it. Right now we are seeing a lot of problems with .name domains being treated as unresolvable thanks to this, and mail from .name users is not getting through as mailservers are configured not to accept mail from unresolvable domains. I know, .name domains don't have zones or NS records attached to them - but yes, this is a legit wildcard (kind of like .museum, but this one is for vanity domains). I'd request DNS admins here to not treat .name as delegation-only. thanks --srs -- srs (postmaster|suresh)@outblaze.com // gpg : EDEDEFB9 manager, outblaze.com security and antispam operations
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 <Peter_Losher@isc.org>
Organization: ISC To: bind-announce@isc.org 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: <200310100909.31565.Peter_Losher@isc.org> X-Approved-By: Peter_Losher@isc.org X-ecartis-version: Ecartis v1.0.0 Sender: bind-announce-bounce@isc.org Errors-To: bind-announce-bounce@isc.org X-original-sender: Peter_Losher@isc.org Precedence: bulk List-unsubscribe:
<mailto:bind-announce-request@isc.org?Subject=unsubscribe>
List-Id: <bind-announce.isc.org> X-List-ID: <bind-announce.isc.org> X-RCPT-TO: <LConrad@Go2France.com> 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 Peter_Losher@isc.org | 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-----
participants (1)
-
Suresh Ramasubramanian