I have not been able to determine what causes this.
The symptoms from the client are that queries are sent to the CeroWRT device but it never returns a response. Compare this failing lookup:
16:51:36.140676 IP 192.168.33.1.43897 > 192.168.33.254.53: 27175+ A?
debian.org. (28)
16:51:41.140752 IP 192.168.33.1.43897 > 192.168.33.254.53: 27175+ A?
debian.org. (28)
[no response]
With this successful lookup:
16:51:51.220838 IP 192.168.33.1.57704 > 192.168.33.254.53: 55242+ A?
psg.com. (25)
16:51:51.221277 IP 192.168.33.254.53 > 192.168.33.1.57704: 55242
1/0/0 A 147.28.0.62 (41)
Examples of domains that fail reliably are debian.org (as above) and lkml.org. I have not identified any specific feature of these domains’ records that may cause this, but I haven’t examined them closely.
No update planned to 2.73, which solved most of them.