This is a little strange that `DnsNotFoundAppErrorView` inherits from `DnsNotFoundFramedErrorView`, but cherry picks the `addHandlers` function from `AppErrorView`. Honestly, I think we are going to far with adding new class types for each error we want to handle. Right now, the only difference between these DnsNotFoundXXX views and their parent classes (App and Framed errors) is the error messages we are populating. Let's kill these DnsNotFoundXXX classes and instead put a switch statement in `populateMessages` that cases the error type.