Google Domains blocking all Gitbook URLS: post-mortem
Aside from the Google domain issue (which is obviously a problem) -- why on earth would GitBook be hosting user-generated content under their corporate gitbook.com domain?<p>The registrar issue is one problem here -- but I don&#x27;t see this addressed in their post-mortem. I thought this was a well-known issue. You don&#x27;t host user-generated content on the same domain that handles your corporate email. Because things like this can and do happen, so you want to make sure that your company isn&#x27;t also down while you&#x27;re busy fixing a problem with your customers.<p>I know the exposure risks are different, but isn&#x27;t this is one of the reasons why Github moved hosting Github Pages content to github.io from their primary github.com site? Or why raw data is hosted from githubusercontent.com (in addition to mitigating cookie security issues).<p>The registrar was an issue that was largely out of their hands. But this was something that they could control. And I think it&#x27;s something that is missing from their post-mortem. If they had split their domains, then while <i>serving</i> user-content was disrupted, <i>accepting</i> users to gitbook.com and their email (!?!?) would have still been working. Also, depending on if they had a 3rd domain for hosting their CDN, users that had custom domains would also have been protected.This goes along with the idea that you don&#x27;t use email from your primary domain (cto@gitbook.com) to register your domain (gitbook.com). Or host your status page on the same infrastructure as your site.<p>If I were them, after migrating registrars, this would be the next engineering change I&#x27;d make.<p><i>(Maybe they do this, I don&#x27;t know enough about GitBook to know. But based on the thread here, I don&#x27;t think they do, or at least it isn&#x27;t mentioned in their post-mortem that I saw.)</i>