Unable to configure Zerigo with Heroku

Question

I have added the Zerigo add-on with heroku. I have followed the steps in the answer here.

Except for the third step. When I attempted to do that, I got an info message that I don't need to do that if I am using the add-on in heroku.

However, if I try to access my custom domain, I get an application error. Executing the command

$ heroku logs

I get the following output (pasted partially):

at=error code=H70 desc="Access to bamboo HTTP endpoint denied" method=GET

I went through this article which says that I need to replace proxy.heroku.com with myapp.herokuapp.com - but I don't understand how I need to do that. I tried adding the snippet as suggested in that stackoverflow answer linked earlier, but in that it points to proxy.herokuapp.com

I got this confirmed when I executed a ping command on my custom domain and got the following output:

64 bytes from proxy.heroku.com : icmp_req=68 ttl=46 time=289 ms

How do I get this working?

Answer 1

1. Go to https://dashboard.heroku.com/apps
2. Click on the name of your app
3. Click on "Zerigo DNS Zerigo Basic" and click "Configure". You should see your custom domain name listed under "Host Records."
4. Click "Add Snippet". Choose "Heroku" from the dropdown menu.
5. Click "Add Selected Records".
6. Go to the CNAME entry under host records and click "Edit". Change data from proxy.heroku.com to YOURAPP.herokuapp.com

I also had to do the following:

1. Go back to https://dashboard.heroku.com/apps
2. Click on the name of your app
3. Click on Settings
4. Under "Domains" add your custom domains e.g. mydomain.com. I also had to add one starting with "www."

You may have to wait 10-15 min for the settings to propagate.

Answer 2

If the error is ..

Access to bamboo HTTP endpoint denied"

Change your CNAME entry ..

yourdomain.heroku.com -> yourdomain.herokuapp.com

Answer 3

Is it possible is IT working, but you need to flush your DNS cache on your machine? That's a commmon problem, that your local machine has old/bad DNS data cached when you make a DNS change.

Quick test: try looking up the DNS record on your custom domain using

http://www.mydnstools.info/nslookup

If that looks correct, then google how to flush your DNS cache on whatever OS you are using.