Fwiw, I had the same response when my Meteobridge was talking to Pihole... it just hit DNS like crazy. Thankfully it's just DNS, and that's what DNS servers are meant to do. You can certainly install dnsmasq on whatever you have weewx running on and let it handle that load, but as Greg mentioned, you might end up with oddities. The "cloud" has made this all infinitely more complicated because of super low TTLs, DNS round robin, location based resolution, etc. So if you're adding caching, you may end up in the situation where WU takes an endpoint down and your rapidfires stop updating until the various caches all catch up.
My suggestion... just exclude those entries in pihole so they don't screw up the graph scaling (that was my issue with Meteobridge, it just made every other client queries counter impossible to judge). Good luck! -----Original Message----- From: Greg Troxel <[email protected]> Sent: Thursday, January 4, 2024 8:53 AM To: [email protected] Cc: 'Joel Bion' <[email protected]>; 'G Hammer' <[email protected]>; 'weewx-development' <[email protected]> Subject: Re: [weewx-development] WU Updates and DNS I agree with Ryan and Joel. It is normal to call gethostbyname when you need it, and if that's an issue the user should set up a caching resolver. It is a likely source of bugs and a definite source of complexity to have another caching layer in the daemon. Besides, WU should support mqtt with a long-lived connection. Someone who uses it should file a bug report with them :-) -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/02be01da3f34%2410e0d3f0%2432a27bd0%24%40gmail.com.
