Most home users won’t see this information. The DHCP server on their network routers are usually configured to pass the DNS entries from their ISP to their DHCP configured devices. So your cameras, etc. would then send these requests to the server at the ISP directly - bypassing most logging.
In answer to your question, can you? Yes. You can setup your own DNS server or DNS Proxy using Bind, Unbound, Acrylic DNS Proxy (like DNSMasq), etc. and change your router to instruct your devices to use your DNS for that traffic instead of the ISP’s - and the logs there would then tell you what every device on your network is looking up via DNS.
Not really something most novice users are going to undertake… and in many cases the juice isn’t worth the squeeze.
Alternatively, you could also setup a Docker install within Windows, and then inside a docker container install one of the supported operating systems for Pi-Hole and get it up and running giving you all the statistics you see from my posts above. Added bonus - you also get the ability to block Ads and more on all your devices (including In-app ads on your Phones and tablets that are on Wi-Fi), known malware domains, browser CryptoCoin scripts, etc.
I went the Raspberry Pi route because I do IT for a living and like to tinker - so I have a 7" touchscreen setup on the Pi that gives me the stats immediately with a single touch. Overkill, but to me… fun.
Oh, and the Pi is super cheap and energy efficient - so win-win.
Out of curiosity, where did these people work with you to identify this issue? Your post appears to be the first response from Wyze on this thread, I have also submitted a ticket on this with no response. I am just trying to find the best place that we can use to establish a line of communication to correct these issues in a better fashion. These threads often turn negative rather quickly as folks seem to feel that they are talking to themselves. Am I just looking in the wrong place?
Dear wyze friends, this is Chao from Wyze, the PM of v3. I am very sorry to hear that you are experiencing excessive DNS ping after 12 hours of use. We have identified the bug and released a firmware that has this issue fixed. The firmware version is 4.36.0.252 and it is currently at beta testing. As one of the users pointed out, it was a bug our developer introduced at firmware version 4.36.0.248 by mistake. We have removed the version 4.36.0.248 so it wont impact most of the users.
We would appreciate it if you could upgrade to the firmware 4.36.0.252 and let us know if that problem still occurs to you.
Again, I am very sorry for the inconvenience. This is a bug we should have taken care of but we didn’t. We will do more rigorous testing to avoid such problems occurring again.
Thank you for jumping on this and providing us with an update. I’m looking forward to hearing from some beta testers. In the mean time, I’ll just bounce/restart my v3 every 11.5 hours.
DNS is still acting up. One cam is behaving ok-ish but the other is still screaming into the void. Please see my writeup in the Beta section and alert the v2 PM, please.
My V3s have been behaving fine after the upgrade, only see request to api.wyzecam.com when I open the app. Not sure if this firmware was supposed to address this issue on the V2s as well.
In the mean time, I’ll just bounce/restart my v3 every 11.5 hours.