DNS to always resolve
DNS requests stop resolving for no reason.
Side note: This has happened before, about 2 months ago, at that time i updated all of the PI linux (apt-get upgrade) apps, and reinstalled Pihole. But there has to be a logical answer why DNS requests stop resolving.
fstom1x43j
Nothing appears wrong in your debug log. But there are some possible avenues to explore:
You use DNSSEC. If the time on your Pi drifts significantly, this may cause problems with DNSSEC.
If you are tight on SD card space, logs could grow over time and fill up your card.
If it is time drift causing the problem it is easy to install ntp on your Pi and let it keep your clock correct.
All, thanks for replies.
I've had this issue before, when i wasn't using DNSSEC.
I've got enough space free on the PI SD card, about 24GB free. So far i've changed the NTP servers to be closer to me.
Some more info, when the client side (Windows pc, tablet, etc) DNS resolution fails, i can SSH into the PI and notice i cannot ping to say google.ca, but i can ping fine by IP.
I may consider rebuilding my PI with Raspbian Stretch (current is Jessie). But i just want some answer as to whats causing this. Rebuilding shouldn't be the answer.
Thanks all.
Another possibility - a hardware issue. Power supply (inadequate current), degrading SD card, physical damage to the SD card or insertion pins, etc.
Wouldn't any of that crash the PI as a whole? It's been up for weeks without a crash.
This was happening constantly to me on an older setup with a Raspberry Pi3 that was running also ADS-B. Now I got a dedicated OrangePi One (Debian Stretch), and installed only the PiHole on it. In an hour of working I had the same issues. Stopped resolving, multiple F5 eventually made that site resolve.
This is the latest FTL 4.0. Before (Pi) I was on the beta FTL branch.
Soooooo did you resolve it at all or what?
What triggered this issue? Did you ever find out?
I did not find out why is doing that. Almost like is going to sleep.
Did you take a look at the logs on that device and see if there were any clues in there?
/var/log/syslog
/var/log/pihole-FTL.log
Nothing, new clues.
I had the DNS resolutions quit at 3pm my time, up to 3:05pm. Here are the relevant logs
Pihole-FTL Log:
[2018-10-23 00:07:26.455] Notice: Increasing domains struct size from 10000 to 11000
[2018-10-23 12:00:02.262] Notice: Increasing overTime struct size from 1100 to 1200
Thats all there was.
Syslog for the relevant time and date.
Oct 23 14:40:01 pihole CRON[711]: (root) CMD ( PATH="$PATH:/usr/local/bin/" pihole updatechecker local)
Oct 23 14:50:01 pihole CRON[732]: (root) CMD ( PATH="$PATH:/usr/local/bin/" pihole updatechecker local)
Oct 23 15:00:01 pihole CRON[754]: (root) CMD ( PATH="$PATH:/usr/local/bin/" pihole updatechecker local)
Oct 23 15:03:52 pihole systemd[1]: Starting Session c80 of user pi.
Oct 23 15:03:52 pihole systemd[1]: Started Session c80 of user pi.
Oct 23 15:07:45 pihole systemd[1]: Starting Session c81 of user pi.
Oct 23 15:07:45 pihole systemd[1]: Started Session c81 of user pi.
Oct 23 15:09:01 pihole CRON[1100]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Oct 23 15:10:01 pihole CRON[1150]: (root) CMD ( PATH="$PATH:/usr/local/bin/" pihole updatechecker local)
Oct 23 15:16:34 pihole systemd[1]: Starting Session c82 of user pi.
Oct 23 15:16:34 pihole systemd[1]: Started Session c82 of user pi.
Oct 23 15:17:01 pihole CRON[1376]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)What were the symptoms when this happened? And what did you do to get DNS resolution working again?
The next time this happens, run a debug log while the problem exists. You may not be able to upload it then, but take a look through it and see if an errors are shown.
Almost all of my open apps quit on me, like Skype, Youtube stopped playing, and i couldn't ping anything by DNS names.
I waited about 5 minutes and everything resumed to work.
Since you're considering upgrading your Raspbian to Stretch, now is probably a good time. Export your Pi-Hole settings with teleporter, then they are available for importing on your new installation.
Ok i'll give Stretch a shot and see what happens.
Pi1 B+ should be powerful enough to run PiHole? I don't see a high RAM or CPU usage at all.
This is roughly equivalent to a Pi Zero (slower clock speed) and a Pi Zero does nicely on a home network.
Just to bring an update: I took out the DNS IP from the router and put in in my PC network settings - the settings accepted just one IP. My router doesn't, so one IP was external.
No more "glitches".
Guys, it happened again. Fresh install of Raspbian Stretch, fresh install of pihole.
below is the log,
This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.
The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.
NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.
*** [ INITIALIZING ]
[i] 2018-11-08:22:23:49 debug log has been initialized.
*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...
*** [ DIAGNOSING ]: Core version
[i] Core: v4.0 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.0-0-gddbdb51
*** [ DIAGNOSING ]: Web version
[i] Web: v4.0 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.0-0-gaf8c926
*** [ DIAGNOSING ]: FTL version
[✓] FTL: v4.0
*** [ DIAGNOSING ]: dnsmasq version
[i] 340:
*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.45
*** [ DIAGNOSING ]: php version
[i] 7.0.30
*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 9 (stretch)
*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected
*** [ DIAGNOSING ]: Processor
[✓] armv6l
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.0.4/24 matches the IP found in /etc/pihole/setupVars.conf
[✓] IPv6 address(es) bound to the eth0 interface:
fe80::814a:5856:ef1b:cf8f does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
^ Please note that you may have more than one IP address listed.
As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.
The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.
[i] Default IPv4 gateway: 192.168.0.1
* Pinging 192.168.0.1...
[✓] Gateway responded.
[i] Default IPv6 gateway: eth0
* Pinging eth0...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
*** [ DIAGNOSING ]: Ports in use
*:22 sshd (IPv4)
*:22 sshd (IPv6)
*:80 lighttpd (IPv4)
*:80 lighttpd (IPv6)
*:53 pihole-FTL (IPv4)
*:53 pihole-FTL (IPv6)
127.0.0.1:4711 pihole-FTL (IPv4)
[::1]:4711 pihole-FTL (IPv6)
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] www.e-zeeinternet.com is 0.0.0.0 via localhost (127.0.0.1)
[✓] www.e-zeeinternet.com is 0.0.0.0 via Pi-hole (192.168.0.4)
[✓] doubleclick.com is 172.217.0.238 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is inactive
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active
*** [ DIAGNOSING ]: Setup variables
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.0.4/24
IPV6_ADDRESS=
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
DNSMASQ_LISTENING=single
PIHOLE_DNS_1=149.112.112.112
PIHOLE_DNS_2=1.1.1.1
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSSEC=true
CONDITIONAL_FORWARDING=true
CONDITIONAL_FORWARDING_IP=192.168.0.1
CONDITIONAL_FORWARDING_DOMAIN=gabriclan.ca
CONDITIONAL_FORWARDING_REVERSE=0.168.192.in-addr.arpa
*** [ DIAGNOSING ]: Dashboard and block page
[✓] Block page X-Header: X-Pi-hole: A black hole for Internet advertisements.
[✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!
*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 2940895 Nov 4 03:43 /etc/pihole/gravity.list
-----head of gravity.list------
0.0.0.0
0.r.msn.com
0.start.bz
00.creativecdn.com
-----tail of gravity.list------
zzz.clickbank.net
zzzezeroe.fr
zzzpooeaz-france.com
zzzrtrcm2.com
*** [ DIAGNOSING ]: contents of /etc/pihole
-rw-r--r-- 1 root root 381 Oct 25 23:35 /etc/pihole/adlists.list
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://hosts-file.net/ad_servers.txt
-rw-r--r-- 1 root root 0 Nov 2 04:53 /etc/pihole/blacklist.txt
-rw-r--r-- 1 root root 39 Nov 4 03:43 /etc/pihole/local.list
192.168.0.4 pihole
192.168.0.4 pi.hole
-rw-r--r-- 1 root root 234 Oct 25 23:44 /etc/pihole/logrotate
/var/log/pihole.log {
su root root
daily
copytruncate
rotate 5
compress
delaycompress
notifempty
nomail
}
/var/log/pihole-FTL.log {
su root root
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}
-rw-r--r-- 1 root root 999 Nov 2 04:53 /etc/pihole/whitelist.txt
clients4.google.com
clients2.google.com
s.youtube.com
video-stats.l.google.com
android.clients.google.com
www.msftncsi.com
outlook.office365.com
products.office.com
c.s-microsoft.com
i.s-microsoft.com
login.live.com
dl.delivery.mp.microsoft.com
geo-prod.do.dsp.mp.microsoft.com
displaycatalog.mp.microsoft.com
s.gateway.messenger.live.com
ui.skype.com
pricelist.skype.com
apps.skype.com
m.hotmail.com
sa.symcb.com
s1.symcb.com
s2.symcb.com
s3.symcb.com
s4.symcb.com
s5.symcb.com
officeclient.microsoft.com
services.sonarr.tv
skyhook.sonarr.tv
download.sonarr.tv
apt.sonarr.tv
forums.sonarr.tv
placehold.it
placeholdit.imgix.net
widget-cdn.rpxnow.com
imagesak.secureserver.net
delivery.vidible.tv
img.vidible.tv
videos.vidible.tv
edge.api.brightcove.com
cdn.vidible.tv
dev.virtualearth.net
ecn.dev.virtualearth.net
t0.ssl.ak.dynamic.tiles.virtualearth.net
t0.ssl.ak.tiles.virtualearth.net
connectivitycheck.android.com
clients3.google.com
connectivitycheck.gstatic.com
msftncsi.com
ipv6.msftncsi.com
*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
-rw-r--r-- 1 root root 1810 Nov 7 20:52 /etc/dnsmasq.d/01-pihole.conf
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=10000
log-queries=extra
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=149.112.112.112
server=1.1.1.1
domain-needed
bogus-priv
dnssec
trust-anchor=.,19036,8,2,49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5
trust-anchor=.,20326,8,2,E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D
interface=eth0
server=/gabriclan.ca/192.168.0.1
server=/0.168.192.in-addr.arpa/192.168.0.1
*** [ DIAGNOSING ]: contents of /etc/lighttpd
-rw-r--r-- 1 root root 3027 Oct 25 23:44 /etc/lighttpd/lighttpd.conf
server.modules = (
"mod_access",
"mod_accesslog",
"mod_auth",
"mod_expire",
"mod_compress",
"mod_redirect",
"mod_setenv",
"mod_rewrite"
)
server.document-root = "/var/www/html"
server.error-handler-404 = "pihole/index.php"
server.upload-dirs = ( "/var/cache/lighttpd/uploads" )
server.errorlog = "/var/log/lighttpd/error.log"
server.pid-file = "/var/run/lighttpd.pid"
server.username = "www-data"
server.groupname = "www-data"
server.port = 80
accesslog.filename = "/var/log/lighttpd/access.log"
accesslog.format = "%{%s}t|%V|%r|%s|%b"
index-file.names = ( "index.php", "index.html", "index.lighttpd.html" )
url.access-deny = ( "~", ".inc", ".md", ".yml", ".ini" )
static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
compress.cache-dir = "/var/cache/lighttpd/compress/"
compress.filetype = ( "application/javascript", "text/css", "text/html", "text/plain" )
include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
include_shell "/usr/share/lighttpd/create-mime.assign.pl"
include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"
' 2>/dev/null"
$HTTP["url"] =~ "^/admin/" {
setenv.add-response-header = (
"X-Pi-hole" => "The Pi-hole Web interface is working!",
"X-Frame-Options" => "DENY"
)
$HTTP["url"] =~ ".ttf$" {
setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
}
}
$HTTP["url"] =~ "^/admin/\.(.*)" {
url.access-deny = ("")
}
include_shell "cat external.conf 2>/dev/null"
*** [ DIAGNOSING ]: contents of /etc/cron.d
-rw-r--r-- 1 root root 1496 Oct 25 23:44 /etc/cron.d/pihole
43 3 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity
00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet
@reboot root /usr/sbin/logrotate /etc/pihole/logrotate
*/10 * * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker local
49 15 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
@reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot
*** [ DIAGNOSING ]: contents of /var/log/lighttpd
-rw-r--r-- 1 www-data www-data 1261 Nov 8 00:00 /var/log/lighttpd/error.log
2018-11-05 06:25:06: (server.c.1534) logfiles cycled UID = 0 PID = 11607
2018-11-06 06:26:39: (server.c.1828) server stopped by UID = 0 PID = 1
2018-11-06 06:27:06: (log.c.217) server started
2018-11-06 10:17:35: (log.c.217) server started
2018-11-06 23:28:07: (log.c.217) server started
2018-11-07 20:42:34: (server.c.1828) server stopped by UID = 0 PID = 1
2018-11-07 20:43:00: (log.c.217) server started
2018-11-07 22:35:37: (server.c.1828) server stopped by UID = 0 PID = 1
2018-11-07 22:36:06: (log.c.217) server started
2018-11-07 22:41:07: (server.c.1828) server stopped by UID = 0 PID = 1
2018-11-07 22:41:40: (log.c.217) server started
2018-11-07 22:50:42: (server.c.1828) server stopped by UID = 0 PID = 1
2018-11-07 22:51:11: (log.c.217) server started
2018-11-07 22:57:24: (server.c.1828) server stopped by UID = 0 PID = 1
2018-11-07 22:57:55: (log.c.217) server started
2018-11-07 23:01:34: (server.c.1828) server stopped by UID = 0 PID = 1
2018-11-07 23:02:01: (log.c.217) server started
2018-11-07 23:53:51: (server.c.1828) server stopped by UID = 0 PID = 1
2018-11-07 23:54:18: (log.c.217) server started
2018-11-07 23:59:39: (server.c.1828) server stopped by UID = 0 PID = 1
2018-11-08 00:00:07: (log.c.217) server started
*** [ DIAGNOSING ]: contents of /var/log
-rw-r--r-- 1 pihole pihole 3920 Nov 8 22:16 /var/log/pihole-FTL.log
-----head of pihole-FTL.log------
[2018-11-08 00:00:11.942] ########## FTL started! ##########
[2018-11-08 00:00:11.943] FTL branch:
[2018-11-08 00:00:11.943] FTL version: v4.0
[2018-11-08 00:00:11.944] FTL commit: 8493df4
[2018-11-08 00:00:11.944] FTL date: 2018-08-05 13:40:30 -0700
[2018-11-08 00:00:11.944] FTL user: pihole
[2018-11-08 00:00:11.944] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2018-11-08 00:00:11.945] SOCKET_LISTENING: only local
[2018-11-08 00:00:11.945] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2018-11-08 00:00:11.945] MAXDBDAYS: max age for stored queries is 365 days
[2018-11-08 00:00:11.946] RESOLVE_IPV6: Resolve IPv6 addresses
[2018-11-08 00:00:11.946] RESOLVE_IPV4: Resolve IPv4 addresses
[2018-11-08 00:00:11.946] DBINTERVAL: saving to DB file every minute
[2018-11-08 00:00:11.947] DBFILE: Using /etc/pihole/pihole-FTL.db
[2018-11-08 00:00:11.947] MAXLOGAGE: Importing up to 24.0 hours of log data
[2018-11-08 00:00:11.947] PRIVACYLEVEL: Set to 0
[2018-11-08 00:00:11.948] IGNORE_LOCALHOST: Show queries from localhost
[2018-11-08 00:00:11.948] BLOCKINGMODE: Null IPs for blocked domains
[2018-11-08 00:00:11.948] REGEX_DEBUGMODE: Inactive
[2018-11-08 00:00:11.949] Finished config file parsing
[2018-11-08 00:00:11.960] Compiled 0 Regex filters and 49 whitelisted domains in 11.0 msec (0 errors)
[2018-11-08 00:00:12.014] Database successfully initialized
[2018-11-08 00:00:12.031] Notice: Increasing queries struct size from 0 to 10000
[2018-11-08 00:00:12.032] Notice: Increasing domains struct size from 0 to 1000
[2018-11-08 00:00:12.032] Notice: Increasing clients struct size from 0 to 10
[2018-11-08 00:00:12.032] New forward server: 1.0.0.1 (0/0)
[2018-11-08 00:00:12.033] Notice: Increasing forwarded struct size from 0 to 4
[2018-11-08 00:00:12.033] Notice: Increasing overTime struct size from 0 to 100
[2018-11-08 00:00:12.033] New forward server: 1.1.1.1 (1/4)
[2018-11-08 00:00:12.186] New forward server: 192.168.0.1 (2/4)
[2018-11-08 00:00:12.256] Notice: Increasing queries struct size from 10000 to 20000
[2018-11-08 00:00:12.285] Notice: Increasing overTime struct size from 100 to 200
[2018-11-08 00:00:12.288] New forward server: 149.112.112.112 (3/4)
[2018-11-08 00:00:12.289] New forward server: 84.200.70.40 (4/4)
[2018-11-08 00:00:12.289] Notice: Increasing forwarded struct size from 4 to 8
-----tail of pihole-FTL.log------
[2018-11-08 00:00:12.032] Notice: Increasing domains struct size from 0 to 1000
[2018-11-08 00:00:12.032] Notice: Increasing clients struct size from 0 to 10
[2018-11-08 00:00:12.032] New forward server: 1.0.0.1 (0/0)
[2018-11-08 00:00:12.033] Notice: Increasing forwarded struct size from 0 to 4
[2018-11-08 00:00:12.033] Notice: Increasing overTime struct size from 0 to 100
[2018-11-08 00:00:12.033] New forward server: 1.1.1.1 (1/4)
[2018-11-08 00:00:12.186] New forward server: 192.168.0.1 (2/4)
[2018-11-08 00:00:12.256] Notice: Increasing queries struct size from 10000 to 20000
[2018-11-08 00:00:12.285] Notice: Increasing overTime struct size from 100 to 200
[2018-11-08 00:00:12.288] New forward server: 149.112.112.112 (3/4)
[2018-11-08 00:00:12.289] New forward server: 84.200.70.40 (4/4)
[2018-11-08 00:00:12.289] Notice: Increasing forwarded struct size from 4 to 8
[2018-11-08 00:00:12.290] New forward server: 8.8.4.4 (5/8)
[2018-11-08 00:00:12.290] New forward server: 8.8.8.8 (6/8)
[2018-11-08 00:00:12.291] New forward server: 4.2.2.2 (7/8)
[2018-11-08 00:00:12.303] Imported 11803 queries from the long-term database
[2018-11-08 00:00:12.304] -> Total DNS queries: 11803
[2018-11-08 00:00:12.305] -> Cached DNS queries: 1299
[2018-11-08 00:00:12.305] -> Forwarded DNS queries: 10478
[2018-11-08 00:00:12.305] -> Exactly blocked DNS queries: 2
[2018-11-08 00:00:12.306] -> Unknown DNS queries: 24
[2018-11-08 00:00:12.306] -> Unique domains: 19
[2018-11-08 00:00:12.306] -> Unique clients: 5
[2018-11-08 00:00:12.306] -> Known forward destinations: 8
[2018-11-08 00:00:12.307] Successfully accessed setupVars.conf
[2018-11-08 00:00:12.360] PID of FTL process: 515
[2018-11-08 00:00:12.361] Listening on port 4711 for incoming IPv4 telnet connections
[2018-11-08 00:00:12.362] Listening on port 4711 for incoming IPv6 telnet connections
[2018-11-08 00:00:12.363] Listening on Unix socket
[2018-11-08 00:00:12.368] Compiled 0 Regex filters and 49 whitelisted domains in 0.8 msec (0 errors)
[2018-11-08 00:00:12.389] /etc/pihole/black.list: parsed 0 domains (took 0.1 ms)
[2018-11-08 00:00:14.947] /etc/pihole/gravity.list: parsed 126723 domains (took 2555.3 ms)
[2018-11-08 09:10:09.116] Notice: Increasing overTime struct size from 200 to 300
[2018-11-08 20:02:07.880] Notice: Increasing domains struct size from 1000 to 2000
[2018-11-08 22:16:44.356] Notice: Increasing clients struct size from 10 to 20
*** [ DIAGNOSING ]: Locale
LANG=en_US.UTF-8
*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 8257074 Nov 8 22:25 /var/log/pihole.log
-----head of pihole.log------
Nov 8 00:00:12 dnsmasq[515]: started, version pi-hole-2.79 cachesize 10000
Nov 8 00:00:12 dnsmasq[515]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC loop-detect inotify
Nov 8 00:00:12 dnsmasq[515]: DNSSEC validation enabled
Nov 8 00:00:12 dnsmasq[515]: warning: failed to change owner of /var/log/pihole.log: Operation not permitted
Nov 8 00:00:12 dnsmasq[515]: using nameserver 1.1.1.1#53
Nov 8 00:00:12 dnsmasq[515]: using nameserver 149.112.112.112#53
Nov 8 00:00:12 dnsmasq[515]: read /etc/hosts - 5 addresses
Nov 8 00:00:12 dnsmasq[515]: read /etc/pihole/local.list - 2 addresses
Nov 8 00:00:12 dnsmasq[515]: read /etc/pihole/black.list - 0 addresses
Nov 8 00:00:14 dnsmasq[515]: read /etc/pihole/gravity.list - 253446 addresses
Nov 8 00:00:26 dnsmasq[515]: 1 127.0.0.1/60209 query[A] 2.debian.pool.ntp.org from 127.0.0.1
Nov 8 00:00:26 dnsmasq[515]: 1 127.0.0.1/60209 forwarded 2.debian.pool.ntp.org to 1.1.1.1
Nov 8 00:00:26 dnsmasq[515]: 1 127.0.0.1/60209 forwarded 2.debian.pool.ntp.org to 149.112.112.112
Nov 8 00:00:26 dnsmasq[515]: 2 127.0.0.1/60209 query[AAAA] 2.debian.pool.ntp.org from 127.0.0.1
Nov 8 00:00:26 dnsmasq[515]: 2 127.0.0.1/60209 forwarded 2.debian.pool.ntp.org to 1.1.1.1
Nov 8 00:00:26 dnsmasq[515]: 2 127.0.0.1/60209 forwarded 2.debian.pool.ntp.org to 149.112.112.112
Nov 8 00:00:26 dnsmasq[515]: * 127.0.0.1/60209 dnssec-query[DS] org to 1.1.1.1
Nov 8 00:00:26 dnsmasq[515]: * 127.0.0.1/60209 dnssec-query[DS] org to 1.1.1.1
Nov 8 00:00:26 dnsmasq[515]: * 127.0.0.1/60209 dnssec-query[DNSKEY] . to 1.1.1.1
Nov 8 00:00:26 dnsmasq[515]: * 127.0.0.1/60209 dnssec-query[DNSKEY] . to 1.1.1.1Your debug log again is normal.
Where are some other places i could look to see whats happening?