On Jan 4, 2024, at 6:30 AM, G Hammer <gary....@gmail.com> 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.
--
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 weewx-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/6cdab24d-9998-4e39-b29a-d69a430ed45an%40googlegroups.com.
On Jan 4, 2024, at 8:06 AM, Joel Bion <jpb...@gmail.com> 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)
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
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/CA514115-415E-46DC-A543-A63D38E52838%40gmail.com.
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. =)
--
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 weewx-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/e3f4883b-aa69-4a4d-b223-28c599353a11n%40googlegroups.com.
On Jan 4, 2024, at 10:14 AM, G Hammer <gary....@gmail.com> wrote:
I am happy enough with sending the DNS lookups external.
Saves configuring pihole to not log/ignore those calls.If misconfigured, it ran for literally years with no warnings until the infernal WU lookups were pointed it way.Seems happy enough now.
<pihole.png>On Thursday, January 4, 2024 at 1:04:57 PM UTC-5 Vince Skahan wrote: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 compute I'd suggest your pihole is misconfigured somehow.(I'm running mine in docker on a several year old i3 NUC that is basically at zero load average)
--
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 weewx-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/1ad89bff-c8fe-4f37-a4f5-6ca4213fc322n%40googlegroups.com.
<pihole.png>
On Jan 9, 2024, at 6:29 AM, G Hammer <gary....@gmail.com> wrote:
As a happy end, I installed unbound on the WeeWX machine with an added local zone to allow the machine to see a couple of local targets needed for backup and NTP.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/6e63aabf-9451-4950-8878-0b11c8f1486an%40googlegroups.com.