I'm trying to point my GoDaddy domain to Heroku app. I followed the steps given here: https://devcenter.heroku.com/articles/custom-domains#add-a-custom-root-domain but I'm unable to access my Heroku app. Here are my DNS records settings:
Can someone tell me where I'm going wrong?
cname only allow you to point subdomain, so this case you should be able to see www subdomain pointed to Heroku, can you try to remove the A record.
I would recommend using DNS service like DNSimple/Cloudflare or in case you don't want to go out of Heroku you can try pointDNS
Related
I have a domain name with GoDaddy: example.com.
I want example.com to point to my front-end app on Netlify (currently doing so fine with the nameservers pointing to Netlify).
I have created a subdomain on GoDaddy, api.example.com. I want to point this to my back-end app on Heroku (currently working with Heroku’s free (and rather whacky) subdomain name.
I am struggling getting my subdomain on GoDaddy to point to my app on Heorku. The DNS Target given by Heroku is to be added into the DNS. But in GoDaddy, the DNS is unable to be managed because my nameservers are already pointing towards Netlify - and it is my assumption, I cannot point a subdomain to Heroku via Netlify (unless I’m mistaken). I have checked other answers on here, but none seem to face this problem of nameservers already pointing elsehwere.
I’m pretty new to this back-end deployment, so any help would be gratefully appreciated. Thank you in advance.
So I want to host my front-end React app on Netlify and I want it to be at www.mydomainname.com.
I also want to host my back-end on Heroku and I want it to be at api.mydomainname.com.
The problem is that if I set NameCheap DNS settings to use NamCheapDNS I can point it to Heroku, but I can't find a way to point it to Netlify as well since Netlify tells me to set NameCheap DNS to Custom DNS and I should point it to Netlify DNS with dns1.p07.nsone.net from 1 to 4.
Is there a way to have front-end on Netlify and back-end on Heroku, or at the end I have to transfer my React front-end to Heroku as well? And would that use the extra dyno or not?
Thanks!
In the end, I added dns1.p04.nsone.net. as the NS Record for "www" host in the Advanced DNS tab under my domain name.
Belatedly,
You can add a CNAME in Netlify's DNS records that points to Heroku's DNS. It looks like this
Record Type=CNAME
Name=api
Value=asdfasfd.herokudns.com
TTL=(blank)
I have a domain registered on bluehost and Im trying to point the DNS to my heroku app. I have changed the www entry to the provided target. I also added the domain in heroku (once with the www and once without). The domain name is still responded to with the bluehost hosted app and not redirecting to the heroku instance. Please advise?
Please check if there is any A record.
Currently i have an app on Heroku with a wildcard subdomain working like this:
client1.myapp.com, client2.myapp.com, ...
This is working fine.
Then, i'd like that each client can access this apps using their own personal domains. So, testing this on my personal domain, i would like to configure test.mydomain.com like this:
CNAME test --- client1.myapp.com
But, this is not working yet. I keep getting the heroku error 'No such app, There's nothing here, yet.'.
Not sure what i am missing. Is it a problem related to my actual Laravel app? Heroku config? DNS?
Thanks in advance for any help.
Assuming your application will provide an hostname for each client (actually, it would probably be preferable to have a single hostname as in any case it looks like they will all point to the same Heroku app), then you have to complete all these tasks in order to make it work:
Add the subdomain client1.myapp.com as domain attached to the Heroku app
Configure the DNS record for client1.myapp.com
Ensure client1.myapp.com resolves (dig client1.myapp.com)
Add the customer subdomain/domain to your Heroku app, otherwise Heroku will reject routing the requests for that domain
Configure the DNS record for the customer subdomain/domain to CNAME client1.myapp.com
Ensure the customer subdomain/domain resolves
According to your issue description, I assume you probably did not configure the customer subdomain/domain as domain to your Heroku app.
(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.