I am trying to apply the DNS mapping in godaddy. I am doing it for first time so there might me some silly things.
My application is hosted on heroku and have a link something like this www.example.herokuapp.com. I am trying to apply the dns mapping of www.something.com. Steps I have followed :-
heroku heroku domains:add something.com
Added CNAME host - www, Points To - example.herokuapp.com
Added Forwarding to example.herokuapp.com
Following these steps I am able to do the mapping or so but when I go to www.something.com it redirects to www.example.herokuapp.com which I do not want. I want it to be www.something.com. Please suggest something.
P.S. - I have also tried removing step 3 after seeing some tutorials but then it stops even to redirect.
Related
I have some struggles setting up a custom domain for my rails application. I followed the "Summary of steps" on Heroku
For example: i bought the domain "mydomain.com". I added the domain by running heroku domains:add "www.mydomain.com"
And gave all Informations shown when running heroku domains(Domain Name; DNS Record Type; DNS Target) to my Domain-provider. But it seems like these are not enough informations therefore my provider is asking for a so-called "host" or subdomain, for which the DNS target is to be deposited.
So my question is what is this "host" and why is it needed?
EDIT:
So to clarify, the Problem was that i did not really knew what heroku is doing when running heroku domains:add
"Host" probably means the bare domain, i.e. mydomain.com, excluding 'www' at the front or anything else.
The subdomain is the bit that comes before that.
In doing domains:add www.mydomain.com you are asking heroku to respond to www.mydomain.com.herokuapp.com, so you need point your DNS to that.
Hence, on your DNS provider you probably need a CNAME record like www.mydomain.com.herokudns.com
That basically means send everything that they receive on your actual domain to that one, instead, which is the one that heroku serves your app on.
Different DNS providers do use slightly different terms, so you need to get the concepts clear of what you're trying to achieve, then you'll work it out. Also, delays in records updating can make it annoying to debug when you're trying to get this working.
Let me keep this as simple as possible. I have looked at a bunch of other posts related to this but haven't found an answer :(. I am hosting my web app on Heroku and using Gandi as my domain provider.
Note: The top answer from this post is what I used as my basis.
A few days ago I set up web forwarding on Gandi so that my mydomain.gg forwards over to www.mydomain.gg. I also set up custom domains in Heroku. It looks like this:
*.mood.gg wildcard.mood.gg.herokudns.com
www.mood.gg www.mydomain.gg.herokudns.com
mood.gg mydomain.gg.herokudns.com
I then went into Gandi and added these to my zone file so it looks like this:
# A 217.70.184.38
* CNAME mydomain.gg.herokudns.com.
www CNAME www.mydomain.gg.herokudns.com.
The A tag is there for the web forwarding where the IP points to a Gandi IP. Heroku changes IP addresses frequently, which is why I use CNAME.
Cool!
This all worked perfectly for 3 days, where I didn't touch my zone file or Heroku app for those 3 days at all.
So here is where the oddness begins. I upgraded my Heroku server to a more expensive plan and pushed some new code to it as well. A few hours later, my root domain mydomain.gg breaks and doesn't forward over to www.mydomain.gg. If I go directly to www.mydomain.gg it works perfectly.
So my question comes down to, where did this break? I never touched my Gandi zone file. All I did was push to my Heroku server and it seemed to break the web forwarding with Gandi. How did pushing to Heorku cause something to mess up with Gandi where all I'm specifying is a Heroku DNS that didn't change at all?
Another thing is, Gandi says they don't support naked domain CNAMEs which is why I use web forwarding. But then whats the point of this line in my zone file:
* CNAME mood.gg.herokudns.com.
Any help would be appreciated!
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 am custom domain for my heroku app using zerigo dns.
www.domain.in is working fine.
domain.com should redirect to www.domain.in sometimes and sometimes giving application error.
Records in zerigo dns :
1) type: redirect, domain.in, http://www.domain.in
2) www.domain.in, cname, xxx.herokuapp.com
another 3 A type records
I think these are correct thats why sometimes it is working, but sometimes giving application error, as of now thinking that it is zerigo bug.
Related question I found - Root domain is not working properly
This setup should work on three conditions:
Your root DNS has A records pointing to Heroku's designated routing IPs
You have added your naked domain to your application (heroku domains:add example.com)
Your application supports your naked domain
Check all these points, a problem in each one can cause things not to work.
If you are redirecting on the DNS/host provider level from the naked domain to www. then none of this is needed, and you have a configuration problem with your host which is out of scope for this question.
EDIT2: Waiting to see if my changes were successful.
EDIT: I reinstalled everything using the command line Zerigo install command (the original question was for manual setup). THe problem now: the custom domains I set up do not work properly. Visiting the custom domain simply returns an error in Chrome: "Oops! Google Chrome could not find www.myapp.com" even though the custom domain I added was "www.myapp.com?
I've been trying to set up a custom domain on my Cedar Heroku app by following instructions at https://devcenter.heroku.com/articles/custom-domains and https://devcenter.heroku.com/articles/zerigo_dns.
In the tutorial for setting up a domain on Zerigo, one of the instructions for adding a host is to add the IP address of the webserver. How do I go about finding this information? I'm having trouble finding any resource that helps me with this.
Am I supposed to be adding the IP address of my app at _.herokuapp.com? When I try to do a look up of this address, I never get a consistent address (probably because of Heroku's many servers). Any help is appreciated.
Linking Zerigo and Heroku is a three step process.
(1) Use the heroku addons:add zerigo_dns:basic command or add Zerio manually through the add-ons page on your Heroku app.
(2) With your registrar or hosting provider to have the domain resolve properly. For Zerigo add all nameservers:
a.ns.zerigo.net
b.ns.zerigo.net
e.ns.zerigo.net
c.ns.zerigo.net
d.ns.zerigo.net
(3) And this is the step I think you may be missing. Log into Zerigo either through your Heroku configuration panel under "add-ons" or log into Zerigo directly. Select the DNS tab next to Account and Servers. On the left panel select the domain you have resolving to Zerigo: this domain will appear. Within this domain under "Nameservers" next to "Hosts" click "Add Snippet". Add both the recommended snippets proxy.heroku.com and the redirect record that excludes the www.
Wait the TTL period (usually 15 minutes) and your domains will work as expected.