BIND 9 CNAME propagation issue

rahmad · 08-13-2008, 11:11 AM

hi,

I have a problem with configuring CNAME record. CNAME is working fine but when i use it to configure CNAME for the zone name its not propagated to the secondary server. below is a sample of my configuration:

#mydomain.com zone file.
IN CNAME test.com

please note the configuration on the named.conf is correct on primary and secondary servers.

thx
rahmad

kenoshi · 08-13-2008, 05:52 PM

You can't CNAME entire domains.

Use DNAME.

http://tools.ietf.org/html/rfc2672

rahmad · 08-14-2008, 02:26 AM

great! I haven't heard before about DNAME RR

but I would like to know if there is no impact on the other defined RRs, for example:
I have the following defined

IN DNAME test.cim
www IN A 1.2.3.4
ftp IN A a.b.c.d

www and ftp subdomains are remain intact after I add the DNAME record for the entire domain? please confirm?? because I have a live setup and I don't want to do anything wrong.

rahmad · 08-14-2008, 04:09 AM

After I read thoroughly about DNAME it seems that

www.mydomain.com will be redirected to www.test.com
ftp.mydomain.com will be redirected to ftp.test.com

but I dont need this, I only want to redirect my domain only like below

mydomain.com will be redirected to test.com ONLY

what do you think?? any thoughts??

CNAME works fine but the problem it is not propagated to my secondary server!!

rahmad · 08-14-2008, 05:26 AM

I found that in RFC 1034 that if you configure CNAME on the node no other data should be configured please see below:

http://www.ietf.org/rfc/rfc1034.txt

anyone has faced this before?? any ideas?? shall I remove the other RRs??

chort · 08-15-2008, 02:35 AM

Trying to CNAME an entire domain is pretty ugly IMO. Better off to use HTTP redirects for the website, but whatever... meh.

If the RFC says only the CNAME should exist, than yes remove the other RRs.