these days I’ll move pihole over to docker…
maybe. =)
From: weewx-development@googlegroups.com
On Behalf Of G Hammer
Sent: Thursday, January 4, 2024 9:49 AM
To: weewx-development
Subject: Re: [weewx-development] WU Updates and DNS
I'm staying with my 'send it outside for DNS
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
> Sent: Thursday, January 4, 2024 8:53 AM
&g
Message-
From: Greg Troxel
Sent: Thursday, January 4, 2024 8:53 AM
To: rcsta...@gmail.com
Cc: 'Joel Bion' ; 'G Hammer' ;
'weewx-development'
Subject: Re: [weewx-development] WU Updates and DNS
I agree with Ryan and Joel. It is normal to call gethostbyname when
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
Of Joel Bion
Sent: Thursday, January 4, 2024 8:11 AM
To: G Hammer
Cc: weewx-development
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
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
