I bought a myapp.app domain with OVH. I've also bought a Heroku hobby dyno in order to have a secure subdomain for my api (https://www.server.myapp.app instead of https://www.myapp.heroku.app).
In Heroku's dashboard/settings, I've added the domain server.myapp.app and copied the generated DNS target provided by Heroku. It looks like: hello-world-5fghjofz765h.herokudns.com.
Then, I added a CNAME record in OVH's DNS zone panel. The name is server.reapr.app. But when validating the entry, I notice the generated domain has an additional . in the end: server.reapr.app.
Is it normal? Should I enter the same name with a final dot in Heroku too?
Next. I added a CNAME record in my DNS zone panel.
When copy/pasting the DNS target in ovh, ovh claims that this is a relative notation that will point to hello-world-5fghjofz765h.herokudns.com.myapp.app..
They say I can add a . in the end to make this notation absolute and point to hello-world-5fghjofz765h.herokudns.com.. I don't understand what it means.
In any case, the DNS target is not strictly equal to the DNS provided by Heroku. There is either an additional . or a myapp.app. in the end of the url.
Anyway, I've tried both options. In each case, Heroku says they're unable to resolve DNS for server. The final error is: 1 domain failed validation.
How to fix this? I'm paying for a dyno I can't even access.
EDIT:
The ovh DNS Zone. I own the domain www.myapp.app (myapp is a random name for this example, and is hidden by a black rectangle on the images below).
The heroku subdomain settings:
Related
I am trying to use a custom domain name in Heroku. So I was following the general directions and I had a question about it.
So I want to get rid of the herokuapp.com in example.herokuapp.com, which requires that I buy the example.com domain name.
It says in the first step "Confirm that you own the custom domain name. If not, you can buy one with a domain registration service."
How does heroku know that I bought example.com in the domain registration service?
If you look at your Herokuapp.com dashboard, for your particular app, you'll find that heroku has issued you a specific domain name. Something like some-custom-string.herokudns.com. Notice that this is herokuDNS.com which is different from herokuapp.com (herokuapp.com is used to access your website publicly). Only you have access to this custom dns string.
When you buy a domain name from a registrar, it'll usually also provide a DNS server. You'll then add a CNAME record in your DNS settings to point to your heroku provided some-custom-string.herokudns.com url. Since only you've access to your DNS server settings, if Heroku finds that the cname entry is present in your DNS records, it'll be a confirmation that you own the domain. The steps to do this are described here.
I have purchased a domain with a DNS provider – Namecheap for my Heroku app and followed all of the steps given my Heroku and Namecheap for configuring the domain and the DNS target that was given by Heroku with Namecheap. But still my domain is not working, only by free domain provided my Heroku. I have contacted Namecheap and they have told me all of the settings are correct. I am not able to contact Heroku because I'm on the free service, and I have no idea what is missing here.
=== robertosullivan Custom Domains
Domain Name DNS Record Type DNS Target
─────────────────── ───────────────
────────────────────────────────────────────────────────────
robertosullivan.com ALIAS or ANAME concentric-cantaloupe-
koaxxlt4rixetcdacu1ebggn.herokudns.com
In the Advanced DNS settings of Namecheap, the CNAME record has a host of www and the value is set to the DNS target given above.
I just want my custom domain to work for my app, but when I try to access the domain I'm told by a Heroku message "nothing here yet".
Use www.robertosullivan.com instead of robertosullivan.com
I have successfully added my domain name of go daddy into my Heroku app .. but DNS target is getting something else . I have changed target in go daddy but still It is not showing the correct one . please help me out
Please read the Heroku doc on custom domain names.
Make sure you've done all of the steps below, and remember there can be a delay before DNS changes are noticeable.
Confirm that you own the custom domain name.
You can buy a custom domain name with a domain registration service.
Add the custom domain to your app with the heroku domains:add
command.
Look up the Heroku-supplied DNS target for the custom domain using
the heroku domains command.
Configure your app’s DNS provider to point to the Heroku-supplied
DNS target.
Confirm that your app is accessible via the custom domain.
There might be a delay while DNS changes propagate.
I am having troubles with setting up custom domain for my heroku app.
here is my heroku app:
https://evening-beyond-1234.herokuapp.com/
and let's say it is my domain:
my-fake-domain.com
So I want my app being able at this domain.
I've added this domain to heroku app domains:
$ heroku domains
=== evening-beyond-1234 Heroku Domain
evening-beyond-1234.herokuapp.com
=== evening-beyond-1234 Custom Domains
Domain Name DNS Target
---------------- ---------------------------------
my-fake-domain.com evening-beyond-1234.herokuapp.com
And on the site where I've bought the domain I can change DNS, so I did this:
1) Type of DNS -> DNS from other hosting provider
2) 1st DNS server (*required) -> evening-beyond-1234.herokuapp.com
3) 2nd DNS server (*required) -> evening-beyond-1234.herokuapp.com
I put the same for the second DNS, because it is marked as required, so I need to specify two DNS.
It's been a few days after these changes and it does not work.
There is also another option for changing DNS: extended DNS editor.
I can specify CNAME entries and others there.
Any ideas what I am doing wrong?
I am completely new to this area, it should be just a silly mistake from my side %)
Your configuration is incorrect. What you are doing is that you are changing the name server of your domain, hence moving the delegation to Heroku.
However, Heroku is not an authoritative name server, hence you can't delegate your domain to them.
What you need to do is restore the delegation at your hosting provider and, instead, check the documentation of your hosting/DNS provider to learn how to create an A or CNAME record to point your domain to Heroku.
Also note that you will not be able to point your apex domain (hence my-fake-domain.com to Heroku unless you use one of these DNS providers that support a CNAME-like capability for the apex domain.
Regardless who you use, you can create a CNAME record to point www.my-fake-domain.com to evening-beyond-1234.herokuapp.com.
For my-fake-domain.com you either create an ALIAS/ANAME according to one of those provider documentation, or you redirect the domain to the www version.
After reading about how a my-app.herokuapp.com cannot be referenced by an A Record by the simple fact that Heroku has a dynamic implementation of its servers, I chanced upon articles which extolled the uses of ALIAS functions in DNS services like Zerigo and DNsimple as a workaround for this issue.
This SO Post explains this problem has been solved, Point top level domain to heroku app
However I do not follow how exactly to implement the solution.
Assuming I have a functional ALIAS setup in Zerigo which points to my my-app.herokuapp.com how do I then have my current webhost point to this ALIAS for the root domain?
Here is my Hostgator Control Panel which shows how the root domain (fls.net) is directed to a particular server via an A Record. I would like to subistute that A Record with my Zerigo ALIAS. How do I do that? Do I change my A Record to a CName? and then just put the ALIAS name in?
Note:
This post: How to redirect a root (naked) domain to www - heroku and zerigo seemed to have the same issue, except I don't understand why he calls the solution of using an ALIAS as "temporary". Why would it be a temporary solution?
You have to change your domain's name servers to point to Zerigo's name servers. You do this through your HostGator config. Zerigo has an article on the name servers that your domain should use. This article from HostGator explains how to change your domain's name servers. Basically, you want to log in to the HostGator portal and change the name server's to the one's listed in Zerigo's article.
Zerigo can handle the DNS for your domains, but only if DNS resolvers know to look at Zerigo instead of HostGator. Right now, when a DNS resolver (such as the one used by your computer's operating system) looks up the IP address to which yourdomain.com resolves, it first looks for the name servers that handle yourdomain.com, and then queries them. If the name servers point to HostGator, it doesn't matter what records you put in Zerigo, because HostGator will be queried for the domain's associated IP address. If you want Zerigo to handle the DNS resolution, you have to point the name servers to those managed by Zerigo instead.