A frustrating aspect of negative caches is that the user may put a great effort into troubleshooting the problem, and then after determining and removing the root cause, the error still does not vanish.
For instance, DNS requires that caching nameservers remember negative responses[1] as well as positive ones.
If an authoritative nameserver returns a negative response, indicating that a name does not exist, this is cached.
A negative cache is normally only desired if failure is very expensive and the error condition raises automatically without user's action.
It creates a situation where the user is unable to isolate the cause of the failure: despite fixing everything they can think of, the program still refuses to work.