You might be wondering why the official The Final Outpost blog reel is not presently using a finaloutpost.net hostname. Indeed, we fully plan to make it available using blog.finaloutpost.net eventually. Unfortunately, the setup with the current host of The Final Outpost means that the domain is effectively outside of Corteo’s control (and in control of the host).
While Corteo owns finaloutpost.net, its name servers currently point to a Cloudflare account he does not own.
What does that mean? That means that whenever you try to navigate to any address with a finaloutpost.net hostname – including forum.finaloutpost.net, or a hypothetical blog.finaloutpost.net – the information where on the internet your browser can find the underlying information is ultimately sourced from Cloudflare. This is how Cloudflare can provide a CDN (Content Delivery Network) to The Final Outpost.
Note that there’s nothing wrong with Cloudflare; they’re a good, reputable company. The trouble with our setup at the moment is that the Cloudflare account that defines where finaloutpost.net resides – and also how finaloutpost.net is cached – is firmly in control of the site’s current host. This means that any changes to finaloutpost.net hostnames (including adding new ones) would in theory have to go through the host’s support system. This is both error prone and riddled with past frustrations.
From a technical perspective, Corteo could absolutely change the domain’s name servers to something else that points somewhere he does control, but he would be violating an agreement he’s made with the current host.
For the moment, we’ll stay a little hobbled by this. Once the mythical recode is done (and we will update you with more information on said recode on this blog, so it stops being quite so mythical), we’ll be able to switch over to an infrastructure we have far better control over, at which point this blog will become blog.finaloutpost.net.