Further thoughts:When I think of even the more complexly configured servers, they may support email, web services, things like that. This means they are, for network use purposes, frequently responsive to a remote request vs. primarily generative of traffic for their own reasons.Many data generativ
I might add that I've been running 'dig' a lot on my system this morning
while constructing my previous answer, and I 'do' see my pihole caching.
Many answers are from cache. When the TTL has expired it looks up to
google. So it's working as expected. Again, if your pihole is out of
comput
Your pihole is misconfigured if it is out of resources with that few a
number of queries.
If WU sets their TTL short, all consumers are going to query often because
nobody's caching nameserver (pihole, local, google, or anybody else) will
have a valid cache. That is just how DNS works. Things
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
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 c
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,
y
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
Short of weewx including a dnscacher, which would only solve the issue for
weewx on a computer, not everything else, not sure what can be done. Maybe
include a note that users may want to install dnsmasq on their weewx box if
they use rapidfire? At least then the traffic is all local to the box…
To make my point more precisely, unless weewx is somehow explicitly indicating it wants a fresh, not cached, entry (can an app even do that?!) I don’t see how weewx can be at fault here. Does your weewx-running machine run a local caching DNS resolver? Have you verified its use and configuration us
Should WeeWX, or any application, be aware of how DNS gets the address, including the use of a cache? I tend to think “no” as that breaks “layering” (leaving the network details out of the application, in this case)Usually you get the operating system’s networking stack, or DNS supporting applicati
I recently regraded my LAN and in doing so forgot to have my WeeWX machine
use external DNS. It was pointed to my pihole DNS servers.
Because of that, I see that the WU update is not very well behaved.
It seems to call for a new DNS lookup every time it fires.
With rapid fire on, that is 85000+
11 matches
Mail list logo
