Help: setting a CNAME record for the domain

[Erik Aronesty]

Dear Tal,

- adding a "com zone" is tricky - and no, you would have to add ALL of your records for "teiko.com" to the "com" zone (but that's OK since most of them are just cname's anyway).  Also, your server would no longer function as a recursive nameserver - and could only be used as authoritative.

- Secondary DNS servers *should* be able to handle this - but I'm not sure - yo may want to try and use 8.2.3 to secondary from a 8.2.2 server and see what happens.

- The BIND maintainers are obstinate about this feature - and feel it is some sort of terrible thing.  I have been arguing about it with them for months.  8.2.3 was supposed to be a maintenance release - and yet they severely altered the behavior of the server.  It's screwy.

- bear in mind that 8.2.2 supported this feature

Here's the minimalist patch:

  

			- Erik

-----Original Message-----
From:	Tal Dayan [SMTP:tal at zapta.com]
Sent:	Sunday, February 25, 2001 11:12 AM
To:	Erik Aronesty
Cc:	bind-users at isc.org
Subject:	RE: Help: setting a CNAME record for the domain

Hi Erik,

Thanks for the info. It is strange that we need to go through this just to
have such a simple thing (is there a deep issue here that I miss, can
anybody comment on this ?)

Your #2 suggestion is interesting but I need more help since I am a newbie
to
DNS. We don't have a .com zone file on our server. If we will add it, do we
need to remove the teiko.com zone file or is BIND smart enough to combine
the entries related to teiko.com from the two zone files ?

Also, if we go with the patch approach, what about our outsourced secondary
DNS servers, will they know how to handle this ?

And if this patch does not create a problem with the rest of the DNS world,
how about submitting your patch to the Bind maintainers, asking to include
this great feature with a runtime switch that enable / disabled it.

Thanks,

Tal

> -----Original Message-----
> From: Erik Aronesty [mailto:erik at primedata.org]
> Sent: Sunday, February 25, 2001 7:50 AM
> To: 'Tal Dayan'
> Cc: bind-users at isc.org
> Subject: RE: Help: setting a CNAME record for the domain
>
>
> Dear Tal,
>
> Dues to ISC's interpretation of the DNS specification, the fact
> that this zone happens to be at the "root" of a particular "text
> file" means it *can not have a CNAME* in 8.2.3.
>
> You can get around this in 3 ways:
>
> 1 - Copy all of the resource records from teiko.ontero.net. to
> your server on a regular basis (IE: don't use cnames).
> 2 - Make an entry in the ".com" zone for "teiko".
> 3 - Patch BIND to allow cnames - no matter where they occur in
> the tree of zone info (I have the source for load_db.c if you need it)
>
> 			- Erik
>
>
> -----Original Message-----
> From:	Tal Dayan [SMTP:tal at zapta.com]
> Sent:	Sunday, February 25, 2001 12:48 AM
> Cc:	bind-users at isc.org
> Subject:	Help: setting a CNAME record for the domain
>
>
> Hello,
>
> We are suing named 8.1.1 on Redhat 6.2
>
> We try to set in the zone file of the domain 'teiko.com' the
> following CNAME
> record:
>
> teiko.com.     CNAME   teiko.ontero.net.
>
> but get the error:
>
> teiko.com has CNAME and other data (invalid)
> Feb 24 21:32:51 dns1 named[2967]: zones/friends/teiko.com:47:teiko.com:
> CNAME and OTHER da
> ta error
>
> When we change the CNAME record to an A record:
>
> teiko.com.      A       205.162.50.66
>
> It works just fine. Are we doing anything wrong ?
>
> Since logically the record as an alias, we prefer to have a CNAME rather
> than
> A record.
>
> Thanks,
>
> Tal
>
>
>


-- Binary/unsupported file stripped by Listar --
-- Type: application/octet-stream
-- File: db_load.c


-- Binary/unsupported file stripped by Listar --
-- Type: application/octet-stream
-- File: db_update.c