Interesting theory - if I understand, you are suggesting that the IOT device’s DNS queries may have been routed to some other device, and that device was replying “Hey, I don’t allow port 53”? I suppose it’s possible, but that would still sound like a peplink bug to me, as the only thing that triggered this issue in the first place was updating from firmware 8.4.1 to 8.5.0.