Yes. And yeah, pihole is running dnsmasq itself, and just adding entries for known problems to 127.0.0.1.
And no, I’ve never seen pihole raise a “load too high” message or anything. I’ve got it running on same raspberry pi my weewx runs on… chugs along every day, all day, no issues. One of these days I’ll move pihole over to docker… maybe. =) From: [email protected] <[email protected]> On Behalf Of G Hammer Sent: Thursday, January 4, 2024 9:49 AM To: weewx-development <[email protected]> Subject: Re: [weewx-development] WU Updates and DNS I'm staying with my 'send it outside for DNS resolution'. I'm certain that pihole is doing caching, but it still needs to respond to the query. I've just never seen pihole raise an issue that there were too many requests and that it wanted more resources. Albeit the difference was instead of 2 cores, it wanted 2.8 cores <g>. On Thursday, January 4, 2024 at 12:33:04 PM UTC-5 [email protected] <mailto:[email protected]> wrote: 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] <mailto:[email protected]> > Sent: Thursday, January 4, 2024 8:53 AM To: [email protected] <mailto:[email protected]> Cc: 'Joel Bion' <[email protected] <mailto:[email protected]> >; 'G Hammer' <[email protected] <mailto:[email protected]> >; 'weewx-development' <[email protected] <mailto:[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] <mailto:[email protected]> . To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/e3f4883b-aa69-4a4d-b223-28c599353a11n%40googlegroups.com <https://groups.google.com/d/msgid/weewx-development/e3f4883b-aa69-4a4d-b223-28c599353a11n%40googlegroups.com?utm_medium=email&utm_source=footer> . -- 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/037501da3f37%2491edc180%24b5c94480%24%40gmail.com.
