The issue I am facing:
Is this pretty much normal behaviour that will get eventually fixed by an update or do I have a unique issue?
I think lately there are too many weird .local domains in the log
and a lot of "Unknown (12) status
DOMAIN.......................................................STATUS
wpad.local.............................. OK (forwarded to IPFire#5353)
isatap.local.................. ........... OK (forwarded to IPFire#5353)
1.debian.pool.ntp.org.local.................... Unknown(12)
push.services.mozilla.com.local.................. OK (forwarded to IPFire#5353)
raw.githubusercontent.com.local.................. OK (forwarded to IPFire#5353)
Details about my system:
Pihole running on Rpi Zero with upstream DNS Unbound/IPFire
What I have changed since installing Pi-hole:
Updated recently
- Pi-hole [v5.2.1]
- **Web Interface v5.2.1
- FTL [v5.3.2]
I didn't want to hijack someone else's topic but I think my issue could be related to this
what would you suggest using instead of " .local "
I have most of my local devices named pihole.local,
wifirouter.local
and IPFire.local
Only since last 1-2 updates I started to see in the Pihole log some weird domains, so I think I might have an issue
wpad.local OK (forwarded to IPFire#5353)
isatap.local OK (forwarded to IPFire#5353)
1.debian.pool.ntp.org.local Unknown (12)
push.services.mozilla.com.local OK (forwarded to IPFire#5353)
raw.githubusercontent.com.local OK (forwarded to IPFire#5353)
My pihole's only upstream DNS server is IPfire.local#5353 which is Unbound DNS.
The unknown(12) issue looks very similar to this