InformAction Forums

Notice also that "timeout" is probably misleading here, since any standard-compliant name resolution software will likely answer immediately with a "name or service not known" response.
See https://en.wikipedia.org/wiki/.invalid

If this bothers you, I suppose it wouldn't hurt to point noscript-csp.invalid to 127.0.0.1 in your HOSTS file.

That's expected if you use NoScript 10.x. NoScript creates CSP reports to that intentionally-nonexistant domain to track what scripts have been blocked. NoScript also blocks those CSP reports from being sent, so no actual request should leave your browser. DNS lookups can sometimes be done before webRequest API (what NoScript uses to intercept and block the requests) kicks in, this is what you're seeing in those logs.

Name resolution for the name noscript-csp.invalid timed out after none of the configured DNS servers responded.
^That's the new error message