DNS forwarding used to point GoDaddy DNS to Heroku app: this doesn't work from a corporate network, why?

Question

My domain on GoDaddy is set up with DNS forwarding to the Heroku app.

This works fine from all the internet connections I've tried except for the one at work. How can I troubleshoot this issue? Is it a case of ports being blocked? Why might that matter?

Answer 1

Can you share your GoDaddy records? I assume what is going on is this:

1. You are pointing a www record to your app on Heroku. For example www.yoursite.com to mysite.heroku.com
2. Chances are you dont have an A record, since heroku does not give you real static IP addresses
3. On regular networks, you are using public dns services like Comcast, ATT or Google. These DNS services will correct dns mistakes for visitors. So when a visitor types an incorrect domain, they try their best to find the correct site.
4. Your company domain is using its own DNS service that does not have this correction feature.

The above is speculation, but this is usually the case with Heroku, Azure and EC2 without a static IP. If you are using Heroku use a DNS service that works with app domains. dnsmadeeasy.com has a service called ANAME (not CNAME, but ANAME) records that will work with both Heroku and Azure. It's paid, but it's cheap.