I know this is a month+ out, but I’m curious about the noblogredirect/404 issue.
I too have a multisite (subdomains) and originally defined noblogredirect as instructed on the network settings page when registration is disabled.
The good news is that I’m not having any of the 404s on the subdomains redirected; but the main domain is another matter… all 404s on the main redirect to the front page vs. the 404 page. This is an issue with Google, apparently, which is interpreting these as “soft 404s” – a no-no.
Deleting the noblogredirect definition fixes the problem on the local version of my multisite install – I get the expected 404 page on the main domain as well.
Thus, this seems like an obvious and easy fix… but before I make it live, I thought I’d better double check to see if there are any issues with this that I’m not seeing. I want to keep user registration disabled AND get a normal 404 response. And since this particular multisite is a reproduction of what used to be a static HTML site, there shouldn’t be any issues with users visiting a non-existent site – there are zero plans to alter the existing site structure.
Thoughts?