The Frontend going down, and in this manner, means the “bridging mechanism” is broken between the hosted folder/file (Apache ANT (JavaBased)) and the WebPool App (IPFS/IPNS) serving the requests from the NX Resolver (for DNS).
It is exposing the limitations of the technology that is built into different browsers. While, redirecting apps.ens.domains. <— that means ROOT from ‘https://app.ens.eth.limo.’ could and does help (… if it’s a metatag and that shell crashes?) not all users have Web 3 browsers like: Opera, Brave, or Metamask.
So integration into Web 1 Infrastructure Framework such as DNS, Name Service, OSI, TC(i)P Stack is absolutely necessary for complete network traversal.
That image above is telling the user that they will have to rely on Cloudflare’s DNS Name Servers, and they don’t have to be configured to the NSRoot Server the rest of the web uses-they have their own resolution in theory & in practice.
So it means that ultimately ENS’ must useful benefit is limited to the route designated by the underlying DNS layer, and to go more in depth, that means that in order for the route to be transmittable to the content it is trying to access, the IPFS store must also reside in a parallel node that does not have a link-state down making the entire framework and purpose of ENS moot and a universal tool.