Hello there here is my problem.
I've a domain example.com and example.herokuapp.com. It is not recommended by the website to install A records pointing to heroku and this makes the naked domains not possible, so I'm forced to use www.example.com instead of example.com.
I've seen on internet that this is actually possible to do, so far I heard of Zerigo.
Do you have any workaround to that?
Thanks,
n
Yes, you either need to point your A-records for example.com at the Heroku Ips, or better still use DNSimple's ALIAS to do it with a CNAME.
More info here: https://devcenter.heroku.com/articles/avoiding-naked-domains-dns-arecords
Related
I have a CNAME record for www.example.com with value of www.example.com.herokudns.com, and also for example.com with the value of example.com.herokudns.com.
The problem is that I do not know how to make MX records for a mail server on my domain provider server without losing the above functionality.
If I try to create MX records, the domain provider server complains that CNAME exists for example.com and I must remove it. If I remove it and create records for MX as instructed by mail server provider, the mail starts working but browsing to example.com is not possible. Only www.example.com continues to work.
How I could solve this? I tried to google and read about CNAME similar questions here, but can't find any solution.
This is a direct incompatibility with DNS based PaaS like Heroku which doesn't have a single static IP endpoint, and the nature of DNS. You do have options, but you need to assess how each one compliments or counters the very reason you chose an integrated platform like Heroku in the first place. Fortunately, there does look like there's some simple and effective solutions, depending on your exact configuration and providers:
The long and short of it is:
It's not standard to CNAME the apex '#'
See here, here, and here for more details.
Heroku explain that you need to use a DNS provider that supports CNAME functionality at the apex, or use sub-domains exclusively
See https://devcenter.heroku.com/articles/custom-domains#add-a-custom-root-domain
There's a good write-up on this specific topic here:
Heroku and Root (aka “apex” or “naked”) Domains
At face value, the PointDNS addon looks dead simple:
heroku domains:add example-domain.com
NOTE: I've never tried PointDNS and have no opinion of them at all. The suggestion is merely a copy/paste from a heroku article based on simplicity.
I have been struggling to configure my Heroku to point to my domain name registered with GoDaddy.
I've setup my Heroku domain:
And I've configured my CNAME www to point to www.ithhero.com.herokudns.com
So far all tutorials/examples I've seen have had a different DNS target e.g. www.ithero.herokuapp.com . And even though I have followed the steps no results have been yielded. Godaddy and Heroku have been bouncing responsibility between them when raising an issue with either.
What am I doing wrong?
You postet it a while ago so I assume you found a solution already, but you should only change your CNAME value from:
www.ithehero.com.herokudns.com
to
ithehero.com.herokudns.com
This is definitely an issue on GoDaddy.
If you try the following, you can see that the domain has been setup correctly from Heroku's side:
curl -v -H "Host: www.ithehero.com" www.ithehero.com.herokudns.com
Also, if you check your DNS resolution, your CNAME's haven't been propagated at all: https://www.whatsmydns.net/#CNAME/www.ithehero.com
I would go back to GoDaddy and get them to have a look at this.
I'm having some problems configuring the DNS settings for my custom domain to work correctly on Heroku.
I have set the DNS records as follows:
Host Type Points to
example.com WR www.example.com
www.example.com CNAME example.herokuapp.com
www.example.com.au CNAME example.herokuapp.com
However, the 'www.example.com' domain sometimes fails to load on my computer, as well as my client's phone. It seems rare for this domain to fail (it works fine on everyone else's computers that I've asked), but the fact that it doesn't work on mine and my client's computers is a problem.
However, the '.com.au' domain (and the heroku one) always works. Why is this?
Is there anything wrong with the configuration above? I followed the 'custom domain names' article on heroku to reach this configuration (I don't have much experience with DNS, unfortunately). The DNS provider I am using does not support ANAME or ALIAS so I went with the above config instead.
Thanks. Any help in getting the '.com' domain working on every device would be appreciated.
I'm not really sure, it may be a lot of things, DNS caching and other stuff.
But if you don't have a lot of DNS records, I suggest you use a heroku add-on like PointDNS (https://addons.heroku.com/pointdns) as it supports ALIAS.
I am moving my rails applications form DreamHost to Heroku.
Name servers are still on DreamHost.
Here's how I set up:
www.mydomain.com: CNAME to mydomain.herokuapp.com
mydomain.com redirected to www.mydomain.com
This sort of works.
But mydomain.com/admin doesn't work.
I must go to www.mydomain.com/admin.
How can I make mydomain.com/admin work?
Thanks.
mydomain.com is forwarded to www.mydomain.com correct? Then mydomain.com/admin wont work, everything mydomain.com is forwarded.
If you want this behavior then you need to remove your forwarding at the DNS and do this kind of redirection (or not) at the application level.
(tried on Server fault, so going to try here)
Hi I recently setup my octopress blog at http://davidmjohnson.me. This domain works fine, but when I try http://www.davidmjohnson.me I get a "heroku no app found." Why is the www not working. Would really appreciate an explanation. I bought my domain name at dnsimple. Do I need to add a redirect from "http://www.dav..." to just "http://dav..." ?
Thanks
I'm guessing you need to configure this domain (and any subdomain) in the heroku CLI application (equiv. of ssh-ing into the machine and changing the nginx/apache location/virtualhost configuration).
I see they have an entry about this in their reference:
https://devcenter.heroku.com/articles/custom-domains
To elaborate a bit from the documentation:
Subdomains ( www.mydomain.com)
For each subdomain you want to setup configure your DNS provider using
a CNAME record pointing the subdomain to the applicable Heroku
hostname.
If the app is on Cedar, then CNAME the subdomain to myapp.herokuapp.com
If Bamboo, then myapp.heroku.com
In DNSimple a CNAME
record entry for a Cedar app would look like:
You can confirm that your DNS is configured correctly with the host
command:
$ host www.example.com
www.example.com is an alias for myapp.herokuapp.com.
myapp.herokuapp.com is an alias for ar.herokuapp.com.
ar.herokuapp.com is an alias for argon-stack-1879049447.us-east-1.elb.amazonaws.com.
argon-stack-1879049447.us-east-1.elb.amazonaws.com has address 107.20.157.144
...
Actually, it should really be the other way around. It is much better practice to point CNAMEs at Heroku apps, since Heroku apps have no real "static" IP. Since naked domains need an A-record, pointing a naked domain to a Heroku app makes everything much less stable. So the best practice is to forward your naked domain to a "www" subdomain, and then point the "www" CNAME to your Heroku app.
Heroku goes into detail about this here.