But also after and before DoH setup, was ok, now are 2 days that i have this issue, of slow dns solve is very very slow
I setup also dns cache to zero.
Here /etc/dnsmasq.d/01-pihole.conf
cache-size=0
Actual Behaviour:
Dns are very slow to resolve in windows 10.
In first, doesn't solve local dns, i can ping 192.168.178.47 that is my firestick. But on local dns in pi hole i set up firestick4k, and ping firestick4k, say: impossible to find host....
And also with chrome, is too slow to open webpage, like also youtube.
Is Pi-hole the upstream DNS of your router? Because it advertises itself via DHCP as DNS server
* Received 548 bytes from eth0:192.168.178.1
Offered IP address: 192.168.178.39
Server IP address: 192.168.178.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.178.1
lease-time: 864000 ( 10d )
renewal-time: 432000 ( 5d )
rebinding-time: 756000 ( 8d 18h )
netmask: 255.255.255.0
router: 192.168.178.1
dns-server: 192.168.178.1
domain-name: "fritz.box"
broadcast: 192.168.178.255
ntp-server: 192.168.178.1
Port Control Protocol (PCP) server: 192.168.178.1
Do you have anything accessing the gravity database?
2021-05-20 13:45:01.204 2232/T2236] ERROR: SQL query "END TRANSACTION" failed: database is locked
[2021-05-20 13:45:01.205 2232/T2236] END TRANSACTION failed when trying to store queries to long-term database
[2021-05-20 13:45:01.205 2232/T2236] Keeping queries in memory for later new attempt
[2021-05-20 13:45:01.206 2232/T2236] SQLite3 message: API call with invalid database connection pointer (21)
[2021-05-20 13:45:01.207 2232/T2236] SQLite3 message: misuse at line 125258 of [5d4c65779d] (21)
[2021-05-20 13:45:01.207 2232/T2236] ERROR: SQL query "BEGIN TRANSACTION IMMEDIATE" failed: bad parameter or other API misuse
[2021-05-20 13:45:01.207 2232/T2236] SQLite3 message: API call with invalid database connection pointer (21)
[2021-05-20 13:45:01.207 2232/T2236] SQLite3 message: misuse at line 165242 of [5d4c65779d] (21)
[2021-05-20 13:45:01.207 2232/T2236] Error while trying to close database: bad parameter or other API misuse
[2021-05-20 13:45:01.207 2232/T2236] ERROR: Storing devices in network table ("BEGIN TRANSACTION IMMEDIATE") failed
[2021-05-20 13:45:01.207 2232/T2236] SQLite3 message: API call with invalid database connection pointer (21)
[2021-05-20 13:45:01.207 2232/T2236] SQLite3 message: misuse at line 165242 of [5d4c65779d] (21)
[2021-05-20 13:45:01.207 2232/T2236] Error while trying to close database: bad parameter or other API misuse
1 - I use zero dns cache because i didn't like to use cache, that maybe isn't updated. So i prefer to user zero cache for this reason.
2 - I have my router and it is a dhcp server. Is a fritz box.
But in my windows 10 machine, i use pi hole dns ( on my rpi3 ).
So i didn't use dhcp from my pihole.
3 - About gravity , i'm going to tools - update gravity, but seems that no change nothing.
I don't know if there is an access in db gravity.
I remember that in the past, i have installed mysql / mariadb, to share kodi library, between my devices. But i didn't use it now. https://kodi.wiki/view/MySQL
So there isn't any devices that trying to have access into rpi, or into mysql or mariadb.
Maybe i need to delete it? how? and is safe for pi hole?
Internally, Pi-hole uses dnsmasq. It will cache dns answers as long as their TTL (time-to-live) specifies. This is the time the authoritative server wants this record to be valid, before it should be queries again. So there are no outdated cache entries.
When you ping the hostname, do you see the query in Pi-hole's query log?
Yes, i can see it and i guess is wrong, because there is fritz.box so maybe fritz box have something that block:
2021-05-21 21:30:31 A firestick4k.fritz.box 192.168.178.32 OK (forwarded to localhost#5053) NXDOMAIN (1.9ms)
Can you please post the output of ping 192.168.178.47
Yes, this is from my windows 10 machine, with pihole dns. ( and i can ping ip of my firestick as you can see )
C:\Users\rob>ping 192.168.178.47
Esecuzione di Ping 192.168.178.47 con 32 byte di dati:
Risposta da 192.168.178.47: byte=32 durata<1ms TTL=64
Risposta da 192.168.178.47: byte=32 durata<1ms TTL=64
Risposta da 192.168.178.47: byte=32 durata<1ms TTL=64
Risposta da 192.168.178.47: byte=32 durata<1ms TTL=64
Statistiche Ping per 192.168.178.47:
Pacchetti: Trasmessi = 4, Ricevuti = 4,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 0ms, Massimo = 0ms, Medio = 0ms
note. today I also install PiVPN with wireguard split tunneling, so i can use 2 profiles, one of them with full traffic, and another, with only dns. And works like a charm ! Only some things, like this local dns, not works for me, but i guess is fritz box and not pihole. Unfortunately i don't know where is the issue, of course.
