That’s probably normal - or if it indicates a problem, the problem is going to be with the client machines - i.e. the cache only stores the results of the questsions that have been asked of it. So if a request from a LAN workstation comes in for something bogus, and the answer is bogus, then the bogus data is going to be cached. It’s not the cache’s problem and not an assault on the cache itself. If you see suspicious data, then you need to investigate the workstations to see if any of them is infected with some malware, or if some user is doing things they should not be doing.
Of course, you need to make sure that your router blocks incoming DNS queries from the outside world in order for this to be completely true.