Re-Post: CNAME Configuration Behaviour

[Ravi Kondamuru]

I dont think I quite follow what you are saying. There is no breaking of
heirarchy that has happened, as I see it.

The name servers for cs.abc.com are defined in the abc.com name server,
which is where they should be.

The A record for www.cs.abc.com is with the name server of cs.abc.com, which
is where it should be.

its just that in the name server for domain abc.com, there is an entry
www.abc.com		1D IN CNAME www.cs.abc.com

Is this breaking any of the name server rules? saying the name is actually
an alias of name in the sub-domain?

I am reproducing the configuration again:

Configuration on ns.abc.com (name server for abc.com)

www			1D IN CNAME www.cs
cs			1D IN NS	ns.cs
ns.cs			1D IN A		1.2.3.4

Configuration on ns.cs.abc.com (name server for the sub-domain cs.abc.com)

www			1D IN A 2.3.4.5
ns			1D IN A 1.2.3.4

thanks,
- Ravi.

-----Original Message-----
From: Stephen Jacob [mailto:Stephen.Jacob at nominum.com]
Sent: Monday, April 16, 2001 1:25 PM
To: bind-users at isc.org
Subject: Re: Re-Post: CNAME Configuration Behaviour



On Mon, Apr 16, 2001 at 11:05:58AM -0700, Ravi Kondamuru wrote:
> I am trying to alias www.abc.com to www.cs.abc.com
> The problem is arising as cs.abc.com is a delegated sub-domain to a
> different name server.

I assume that you realise that you're breaking the heirarchical
paradigm here...? By delegating a zone to someone else, you are
giving them authority for the delegated zone. You shouldn't be
serving data for names within that zone except as a slave to
them or recursively (maybe from cached data).

Why don't you add the record for www.cs.abc.com to the cs.abc.com
DNS server? That's the way you should be doing it.

Regards,
sj