DNSimple: ALIAS resolution errors
Timeline of updates
- resolved
We have been able to determine the exact cause and advise the following solution: Switching from the Heroku SSL Endpoint add-on to the new Heroku SSL offering should provide a solution. This can be done by switching to the new SSL implementation on Heroku and then removing any SSL Endpoint records on your domain and reapplying the new records either with our one-click service or by manually adding the records you need.
From DNSimple’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on dnsimple.statuspage.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by DNSimple, started 2016-10-21 17:39 UTC, resolved after 2.2 h, 1 update(s).
- Title
- ALIAS resolution errors
- Vendor
- DNSimple
- Date
- URL
- https://rewindex.com/company/dnsimple/incidents/s1lq3dhw4d58
DNSimple profileRecent DNSimple incidentsAll outages on October 21, 2016DNSimple in October 2016MarkdownJSON