I have a domain set with a CNAME alias to point to Heroku, but it is not resolving.

Here is a link to a screenshot: http://awesomescreenshot.com/03226ntoc4

And here is the output from nslookup:

$ nslookup -query=any tyger.ac. dns1.name-services.com
Server:  dns1.name-services.com

tyger.ac        nameserver = dns3.name-services.com
        primary name server = dns1.name-services.com
        responsible mail addr = info.name-services.com
        serial  = 2002050701
        refresh = 10800 (3 hours)
        retry   = 3600 (1 hour)
        expire  = 604800 (7 days)
        default TTL = 3600 (1 hour)
tyger.ac        nameserver = dns2.name-services.com
tyger.ac        MX preference = 5, mail exchanger = eforwardct.name-services.com
tyger.ac        MX preference = 5, mail exchanger = eforwardct3.name-services.com
tyger.ac        MX preference = 5, mail exchanger = eforwardct2.name-services.com
tyger.ac        nameserver = dns4.name-services.com
tyger.ac        nameserver = dns5.name-services.com
tyger.ac        nameserver = dns1.name-services.com
dns2.name-services.com  internet address =
dns3.name-services.com  internet address =
dns1.name-services.com  internet address =
dns4.name-services.com  internet address =
dns5.name-services.com  internet address =

Here is the destination host:

$ nslookup mie-6031.herokussl.com
Non-authoritative answer:
Server:  google-public-dns-a.google.com

Name:    elb033514-473924049.us-east-1.elb.amazonaws.com

Aliases:  mie-6031.herokussl.com

1 Answer 1


If you have a CNAME alias then you must not have other DNS records (e.g., NS) for that name - see rfc1912 - section 2.4.

I guess that eNom interface just filters out this "CNAME for the whole domain". You must point your root domain name to IP addresses (or make the operator of .ac add a CNAME in their records - probably impossible).

If you use Amazon services, then this information about Amazon Route53 and its alias extension might also be interesting for you (see number 3).

  • Heroku doesn't support A name records. devcenter.heroku.com/articles/…. They only support using CNAME aliases, and ENom appears to support CNAME for root domains. I am guessing they emulate it or something. When I had CNAME pointed to the non-SSL Heroku server, it was working fine.
    – Chloe
    Jan 9, 2014 at 22:44
  • Here is more about Heroku and root domains. devcenter.heroku.com/articles/custom-domains#root-domain. "Zone apex domains (aka “naked”, “bare” or “root” domains), e.g., example.com, using conventional DNS A-records are not supported on Heroku." And more: devcenter.heroku.com/articles/apex-domains.
    – Chloe
    Jan 9, 2014 at 22:47
  • If DNS provider allow aliasing of root domain then they usually use special record name for this (alias as Route53 or something like this as heroku say here: devcenter.heroku.com/articles/… ). If ENom support just CNAME and you have other domains with same configuration that just works then maybe they emulate this by scripting and not serve multiple IP for heroku? Can you give me a domain name on ENom with CNAME for root and rest of record similar to this one?
    – dsznajder
    Jan 9, 2014 at 23:04
  • Ok I turned off mail forwarding (I needed it to get my SSL) and set and reset the A and CNAME records and now it is working!
    – Chloe
    Jan 10, 2014 at 0:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.