internal error: looping module stopped

Aleš Rygl ales at
Mon Oct 16 06:45:50 UTC 2017

Hi all,

I have just tested domains mentioned by Jacob below in order to reproduce this 
issue on my system - unbound 1.6.5-1, Debian, use-caps-for-id, validator 
enabled. Though I have some occurrences of looping module stopped error too, 
none of the domains caused this error.


On sobota 14. října 2017 12:51:15 CEST Jacob Hoffman-Andrews via Unbound-users 
> I tested without use-caps-for-id, and did not get the "looping module
> stopped" error.
> I also upgraded to 1.6.7 and applied your patch. Here is a sample of
> some of the queries and log messages I got. I was loading Unbound with a
> mixture of A and CAA queries pulled from the logs of all names in
> certificates issued by Let's Encrypt.
> Oct 14 18:43:22 unbound[8613:0] error: internal error: looping module
> (iterator) stopped
> Oct 14 18:43:22 unbound[8613:0] info: pass error for qstate
> A IN
> --

More information about the Unbound-users mailing list