cname quick question

Cricket Liu Cricket at VeriSign.com
Sun Feb 4 00:28:50 UTC 2001


> Interesting, so that means you cannot have a CNAME at the "zone top" in
any
> "file", but you can achieve this same exact effect by putting the CNAME in
> the file above it
>
> For example:
>
> I need to CNAME for myname.com to store.yahoo.com.
>
> I tested this and it works/validates - but it seems like a clumsy
> workaround.
>
> I had to put the "myname.com." CNAME record in a "com.dom" file. Then I
add
> "com.dom" as the zone file handling "com." in the conf. I then make sure
the
> nameserver is not being used by any machines for recursive service so it
> can't mislead people about the "com." zone.
>
> Is the only way to achieve a CNAME for myname.com to store.yahoo.com.?  I
> cannot replicate the canonical record set (no permissions).

No, you just plain can't have a CNAME record for myname.com.  If
myname.com exists at all, it needs to be delegated from com by NS
records.  (VeriSign GRS will not add a CNAME record to the com
zone for you.)  And if the domain name myname.com owns NS records,
it can't also own a CNAME record.

This whole "CNAMEing the domain name of a zone" business comes
up at least once a week because someone wants the domain name of
their zone to point to the domain name of their web server.  Some folks
even try to put URLs in the CNAME record.  The solution is to add an
address record pointing your zone's domain name to the the address of
your web server.

cricket



More information about the bind-users mailing list