9

Heroku custom domains

I've setup two custom domains for my Heroku app.

example.com        example.com.herokudns.com
*.example.com      wildcard.example.com.herokudns.com

Domain configuration

I configured my domain as follows:

  1. I added a CNAME Record for * pointing to wildcard.example.com.herokudns.com.
    Works fine.

  2. I forwarded my URL using GoDaddy's Domain Forwarding tool, because I can only specify IP addresses as A records.

Problem

The domain forwarding points to example.com.herokudns.com. Unfortunately GoDaddy automatically prepends http://, so it actually does not open my app and instead shows a Heroku message:

There's nothing here, yet.

Goal

Setting up my GoDaddy root domain to point to my Heroku app.

Note: GoDaddy automatically added an A record for @ pointing to >>++FWD1++<<

jonhue
  • 1,085
  • 1
  • 15
  • 47

3 Answers3

15

Cloudflare does the job!

Finally, I achieved my goal of using my naked domain as host by choosing CloudFlare to handle my DNS configuration.

Resources:

Note: CloudFlare has a pretty good documentation and setup process, you just need to:

  1. add your domain to CloudFlare
  2. follow the CloudFlare setup guide
    • updating your nameservers (in my case GoDaddy) to point to CloudFlare
temporary_user_name
  • 30,801
  • 41
  • 120
  • 186
jonhue
  • 1,085
  • 1
  • 15
  • 47
  • make sure that you have Heroku set to receive ssl on it's dashboard, then on CloudFlare set the sll to **full** instead of _flexible_ – CelsoDeSa Sep 01 '19 at 13:16
2

What did you set your DNS to forward to? I had this same problem, but solved this creating a Heroku DNS entry for www.myapp.com. Heroku creates a DNS target of www.myapp.com.herokudns.com.

Here is my setup:

  • DNS forwarding to www.myapp.com
  • DNS CName of www to www.myapp.com.herokudns.com
  • Heroku DNS added www.myapp.com
Mathew Kleppin
  • 172
  • 1
  • 7
  • 3
    Tell me if I am wrong, but that way I have to use the subdomain `www` and that's what I try to circumvent :-) – jonhue Jan 08 '17 at 11:24
  • This still has the problem that `https://myapp` doesn't redirect correctly – jfloff Apr 09 '18 at 15:52
-4

In Setup Heroku and GoDaddy? allegutta solves the issue by masking the heroku-app-name domain with the .com domain. Instead of slooob.com.herokudns.com, use your original heroku app url ([heroku-app].herokuapp.com) and it should work. Just worked for me.

Community
  • 1
  • 1
Eduardo Roxius
  • 45
  • 3
  • For me that does show the url `[heroku-app].herokuapp.com` in the browser address bar, if I redirect to `http://[heroku-app].herokuapp.com`. Is it possible to use `slooob.com`? – jonhue Jan 08 '17 at 12:22
  • You mean when you enter sloob.com the user is redirected to the real app url? That shouldn't happen. – Eduardo Roxius Jan 15 '17 at 15:52
  • 1
    I mean the redirection shouldn't happen. Is it still like that? If so, can you post a picture of your CNAME records? – Eduardo Roxius Jan 15 '17 at 20:12
  • Ah, yea the point was that I want to prevent redirecting from `slooob.com` to `www.slooob.com`. I achieved this at the end by using CloudFlare's Alias Record. – jonhue Jan 15 '17 at 20:35