I have a domain bought from godaddy and it is currently pointed at hostinger. I need to setup a subdomain (api.myapp.com) will point this subdomain as my hostname to AWS. Im not sure if where should i set the subdomain. Is it in godaddy or hostinger?
You could try setting the api.myapp.com subdomain in godaddy and point it to your AWS.
As juanshotman said, point your subdomain to the server that you have set up in AWS.
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.
My heroku app is not linking to my godaddy custom domain
I've tried changing the cname to host to "www" and the "points to" to the heroku dns target I was given. Still it has not worked. I've also tried putting the url of the heroku app:
https://agile-thicket-51202.herokuapp.com/
I've tried the forwarding settings in godaddy as well but was unsuccessful.
(My custom domain has already been verified on heroku)
This is how it appears on my godaddy dns settings:
CNAME www "herokudnstarget"
Could other dns settings be interfering with this?
While working with cname GoDaddy only allows you to point www subdomain.For naked domain pointing use cloudflare or heroku add-on pointDNS.
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.
We purchased and installed an SSL Certificate on our Heroku app, and install the SSL endpoint. The domain is using nameservers that point to a separate cPanel hosting account. I have tried to add a CNAME record in cPanel that points to our Heroku secure endpoint.
I setup the CNAME like this:
Name: *.domain.com.
Type: CNAME
Record: example-7245.herokussl.com
But is has been a whole day and the url still doesn't to heroku. Is this even possible to do this way? We need the email to run off the cpanel host so if we could just use a cname record for the domain server it was perfect.
Thanks for any help.
Not sure why but when I added the DNS add-on Zerigo DNS Zerigo Tier 1, it started to work.
(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.