Adding CNAME for the root domain issue

John Miller johnmill at
Wed Apr 27 14:30:31 UTC 2016

If your domain is, and you're looking to have
the apex record    CNAME     some.other.domain.

but still host other records in the zone, you
can't.  That's not how CNAME records work.  A CNAME record is an alias
for a particular _label_ within a zone.  It's meant to do things like   CNAME   some.other.domain.

What you're saying here is that the name "myserver" will always point
to "some.other.domain" __regardless_of_record_type__.  If you're
trying to do this for the __apex_record__ of your zone (just your
domain name, no hostname), you're saying that you don't need SOA or NS
records for your zone--it's a contradiction in terms.  You _must_ use
an A or AAAA record.  Period.

If you're running a web site on a host whose IP address changes
frequently, may I suggest that you let someone else manage your DNS
for you?  Plenty of DNS companies do this:

Otherwise, I suggest that you read

If you want to manage your own DNS, you need to understand how DNS
works and what its limitations are.


On Wed, Apr 27, 2016 at 10:05 AM, Daniel Dawalibi
<daniel.dawalibi at> wrote:
> Hello John
> The below is not working on our BIND version BIND 9.10.0-P2 unless it is working on other version
> www     CNAME
> Errors returned when adding these records:
> general: dns_master_load: CNAME and other data
> If we proceed with the below work around by replacing the CNAME with A record, It will resolve but our setup requires a CNAME record.
>  A  IPaddress
> www     CNAME

More information about the bind-users mailing list