_Originally created by @intrigeri on [#16956 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16956)_ Problems we already know about: - it would be nice to be able to reboot lizard without people suffering from the Tails website being down; - DDoS resistance: we’re in a very bad place when lizard or SeaCCP are DDoS’ed. So at least we would like to make our website hosted in more than one location. Hosting our website elsewhere too *might* require dropping the ikiwiki cgi, which itself requires: - [x] move blueprints out to a separate wiki - [x] switch to an external search engine - replace our usage of the ikiwiki `ping` plugin with something else → #17364 Depending on the outcome of the risk analysis, there’s probably things we should make more redundant, if this fits into our 2019-2020 sysadmin budget. ### Related issues - **Related to** tails/tails#12406 - ~~**Blocked by** tails/sysadmin#15097~~ (sysadmins already discussed internally the security implications and will document accordingly) **Note:** For S11, this fits in: - `B.2 - Keep our infrastructure up-to-date and secure`: Improving the redundancy of some parts of our infra benefits the availability of those parts and consequently the security and UX of the operating system. ## To-do - [x] Setup a copy of the website in a different network - [x] Wait for #17364+ - [x] Make the DNS point to that copy when `www.lizard` is down - [x] Make sure mirror stats are reported accordingly - [x] Document the setup - [x] Defer redundancy of `download.tails.net` to a separate issue → sysadmin#18124 - [x] Defer replacement of ikiwiki `ping` to #17364 - [x] Figure out about DDoS resistance - [x] Figure out about other bits of redundancy