Ambiguous def of multiple CNAME

[timothy at erinet.com]

> oak	IN	CNAME	tree.foo.com.
> birch	IN	CNAME	tree.foo.com.

This is kosher since tree.foo.com can have as many CNAMEs associated with
it as you like.

> oak	IN	CNAME	tree1.foo.com.
> oak	IN	CNAME	tree2.foo.com.

This is forbidden IIRC.

> tree	IN	A	1.2.3.4
> tree	IN	A	5.6.7.8
> oak	IN	CNAME	tree.foo.com.

IIRC, This is allowable and oak.<origin> will be cached as whichever IP 
is resolved the first time around in this round-robin situation.

> server.foo.com.	IN	CNAME	server.blat.com.
> I am almost sure it's not kosher, but so far it's worked.  I'm on BIND8.2p1.

You certainly can.  we've done that for web.domain.com vs. www.domain.com vs.
www.domain.net, etc.  So that we only had to update one record for it to
propogate over all of our domains.

regards,

tim