- To: wildcard-comments@xxxxxxxxx
- Subject: [wildcard-comments] comments
- From: "Mikey Wareing" <lightinthedark@xxxxxxxxxxx>
- Date: Sat, 27 Sep 2003 16:32:23 +0100
- Sender: owner-wildcard-comments@xxxxxxxxx
Verisign is in blatent breach of the original
contracts for .com and .net TLDs with it's
Under the Functional Specification section
"Nameserver operations for the Registry TLD
shall comply with RFC 1034, 1035, and 2182."
RFC 1034: Section 4.3.1
"If recursive service is requested and
available, the recursive response
to a query will be one of the following:
- The answer to the query, possibly preface by
one or more CNAME RRs that specify aliases
encountered on the way to an answer.
- A name error indicating that the name does
not exist. This may include CNAME RRs that
indicate that the original query name was an
alias for a name which does not exist.
- A temporary error indication."
"If recursive service is not requested or is
not available, the non-
recursive response will be one of the following:
- An authoritative name error indicating that
the name does not exist.
- A temporary error indication.
- Some combination of:
RRs that answer the question, together with an
indication whether the data comes from a zone
or is cached.
A referral to name servers which have zones
which are closer ancestors to the name than the
server sending the reply.
- RRs that the name server thinks will prove
useful to the requester."
RFC 1034: Section 4.3.3
"The contents of the wildcard RRs follows the
usual rules and formats for RRs. The wildcards
in the zone have an owner name that controls the
query names they will match. The owner name of
the wildcard RRs is of the
form "*.<anydomain>", where <anydomain> is any
<anydomain> should not contain other * labels,
and should be in the authoritative data of the
zone. The wildcards potentially apply to
descendants of <anydomain>, but not to
Care2 make the world greener!
Help the planet each day! It's free and easy: