Re: a cname too much

Brandon Black <[email protected]> Tue, 7 Sep 2010 07:42:03 -0500
Newsgroups gmane.network.djbdns
Message-ID <[email protected]>
On Mon, Sep 6, 2010 at 9:34 AM, Schwarz <[email protected]> wrote:
> .ima.tinydnstestzone.org::ns3.nsentry.de::
> Cima.tinydnstestzone.org:fiction.externaldomain.org::
> Cwww.ima.tinydnstestzone.org:fiction.externaldomain.org::
> C*.ima.tinydnstestzone.org:fiction.externaldomain.org::
> &ima.tinydnstestzone.org::ns4.nsentry.de::
> @ima.tinydnstestzone.org:212.162.12.2:mail1.ima.tinydnstestzone.org:::

Casting aside whether or not how djbdns handles the situation is
technically a bug a or not, your data is illegal to begin with.  Per
the RFCs, a CNAME cannot co-exist with any other RR at the same name.
A CNAME RR, for example, cannot exist at the same name as A, MX, or
any other RRs.  This also automatically implies you can never have a
CNAME at the root level of a zone (because it cannot co-exist with the
necessary NS and SOA records).

Also: "." entries define a locally authoritative zone root (SOA, NS,
and the A record corresponding to the NS name), while "&" entries are
used to define nameservers for subzone delegations to other servers.
In both the ima subzone and the parent zone, you seem to be using "&"
to define the second nameserver name for an authoritative zone.

http://cr.yp.to/djbdns/tinydns-data.html

-- Brandon