Freek, et al -- ...and then Freek de Kruijf said... % % It works as expected, but this only happens occasionally, normally the % command works OK. Yesterday it occurred 4 times out of 24 and today it % already occurred 4 times out of 16. That's very odd indeed. It doesn't sound like it's related to runnimg under cron but instead something transient in the system. I was going to suggeat that you strace dig, but i don't think that;s worth it. % % It may be important to mention: this is with Leap 15.4 on a Raspberry Pi 4B. I would lean next toward a resource limitation, and although a Pi is awesome :-) perhaps it's struggling. What does top tell you? What's the uptime? Carlos usually has great ideas here :-) You might try adding some debug info into the script to give you a picture of the world each time cron kicks it off. What if you run the command manually oh, say, 1000 times with no waiting? :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt