As said above, this may be perfectly normal (as in: it has always happened, not as in: it is expected). Before this rather recent change, we simple have not logged such events. Interestingly, I do too have a local unbound running receiving both UDP and TCP traffic and haven't had a single occurrence of this warning in almost three weeks since this was added.