Today we deployed a change to how the Heroku one-click service works. Heroku recently released their European region, and with that change they deprecated the "proxy" subdomain for Heroku apps. To make DNSimple's one-click service compatible with this change, we now require your Heroku app name, as it appears in your herokuapp.com subdomain. When you add Heroku just enter your app name part of the herokuapp.com domain and you should have an ALIAS for your apex domain and a CNAME for "www". You can always add or change these later.
In order to update several low level components of our software stack we have scheduled a maintenance window beginning Sunday, April 21 at 0400 UTC (Saturday, April 20th at 9PM Pacific time). It will remain open for two hours. We expect the DNSimple application and API to be unavailable for less than twenty minutes. Name service will not be affected. We apologize for any inconveniences this may cause our customers. Updates will be posted to our Twitter feed.
Post mortem of the ALIAS record resolution failure on April 6th.
Modern web applications benefit from fast DNS responses. DNS response times may still add anywhere from 10s to 100s of milliseconds to your applications overall latency. DNS providers are constantly working to reduce lookup times using technology such as caching and the use of BGP protocols. Even web browser makers like Google have joined in with fast public resolvers and even improvements in web browsers. You may have already heard of this term: pre-fetching. Well we've gone one step further…
We will be moving NS3 from its current IP address to a new IP address.