Updates

Migrating away from the old Heroku legacy routing layer

Jacobo García López de Araujo's profile picture Jacobo García López de Araujo on

Heroku has set an end-of-life date for their legacy routing layer and if you're using Heroku, this could affect you and your applications. Starting September 29th, they will no longer support applications use their legacy routing. Here is the criteria for determining if you are using their legacy routing layer:

  • Has and uses example-app.heroku.com domain
  • Has any DNS records with values that are subdomains of .heroku.com (typically proxy.heroku.com or example-app.heroku.com)
  • Has DNS A records with values that are IP addresses of infrastructure maintained by Heroku
  • Uses SSL termination add-ons of types ssl:ip or ssl:hostname

Heroku has published an excellent article explaining how to handle the move. We recommend reading through that first before making any changes.

At DNSimple we'be been making very easy to work with Heroku for several years, and we already support the ALIAS record required by Heroku if you want to use a root domain.

You can find more information on setting up your DNS to work with Heroku in our support pages. If you have any questions please feel free to contact us and we'll be happy to help.

Share on Twitter and Facebook

Jacobo García López de Araujo's profile picture

Jacobo García López de Araujo

Devops, infrastructure, urban cyclist, music nerd.

We think domain management should be easy.
That's why we continue building DNSimple.

Try us free for 30 days
4.5 stars

4.3 out of 5 stars.

Based on Trustpilot.com and G2.com reviews.