DNS Issue with PLoS.org – Resolved
We had an outage on our PLoS.org domain resources yesterday due to a DNS issue. As a result, www.plos.org and all of the plos.org subdomains were intermittent as well. The issue was addressed promptly but there was a 2-10 hour delay while DNS servers were updated and ~24 hour delay before a comprehensive international DNS update. Most people were able to access www.plos.org within a few hours.
The DNS issue did not affect any of the PLoS journal websites.
Please be aware that if doi.plos.org is down, you can use CrossRef for DOI resolution.
What went wrong?
Could PLoS have prevented this?
How should the DNS Registrar rules be changed so this doesn’t happen?
How should the DNS system itself be modified to prevent such problems or to minimize their costs?
But of course, few people experienced an event of minor inconvenience or confusion, so the urgency of fixing these escalated problems is quite low. Still the gedanken experiment is of interest to me.
And how do I choose to justify this text left or right?