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… 

 

Rightly or wrongly, DNS has become a huge underpinning of nearly everything on 
modern OSes and software. There’s a reason I have this image hanging on my wall 
in my office

https://images.app.goo.gl/TzCnAXacUgBRk5LDA

 

-Ryan Stasel

 

From: [email protected] <[email protected]> 
On Behalf Of Joel Bion
Sent: Thursday, January 4, 2024 8:11 AM
To: G Hammer <[email protected]>
Cc: weewx-development <[email protected]>
Subject: Re: [weewx-development] WU Updates and DNS

 

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 using tools like 
“dig”?

 

 

Sent from my iPhone





On Jan 4, 2024, at 8:06 AM, Joel Bion <[email protected] 
<mailto:[email protected]> > wrote:

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 
application, to do dns caching for you. For example, using unbound, or dnsmasq 
or if you use systemd, there’s a resolver with that, too. 

 

Are you running one?

 

Sent from my iPhone





On Jan 4, 2024, at 6:30 AM, G Hammer <[email protected] 
<mailto:[email protected]> > wrote:

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+ DNS calls daily!

rtupdate.wunderground.com     85026
wx.lan   87934

 

That number of lookups raised warnings on my pihole machines, they want more 
resources to handle the high volume of calls.

 

I reconfigured the WeeWX machine to use external DNS, but the issue is just 
being pushed elsewhere.

 

Nothing on my network makes that many DNS lookup calls, not even close.

Every OS I'm aware of has a DNS cache, WeeWX doesn't seem to use it though.

 

However, WU has a TTL of only 60 seconds, but that is still around 24X less.

 

Any thoughts?

 

-- 
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/6cdab24d-9998-4e39-b29a-d69a430ed45an%40googlegroups.com
 
<https://groups.google.com/d/msgid/weewx-development/6cdab24d-9998-4e39-b29a-d69a430ed45an%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] 
<mailto:[email protected]> .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/CA514115-415E-46DC-A543-A63D38E52838%40gmail.com
 
<https://groups.google.com/d/msgid/weewx-development/CA514115-415E-46DC-A543-A63D38E52838%40gmail.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/014301da3f2b%24d75eaa60%24861bff20%24%40gmail.com.

Reply via email to