The database was reset. Try the same website (blocked above) and see if it registers.
Check out the query log. See if you have entries there.
Run a pihole -r and repair. I think there are some permission issues there and hopefuly a repair will fix that
done, no change
sudo ls -l /etc/pihole/ and uname -a ?
I wish i had good news with that.
Whats the output of those commands?
sudo ls -l /etc/pihole/ and uname -a
ls: cannot access and: No such file or directory
ls: cannot access uname: No such file or directory
/etc/pihole/:
total 11452
drwxr-xr-x 2 pihole pihole 4096 May 21 19:49 .
drwxr-xr-x 121 root root 12288 May 21 18:50 ..
-rw-r--r-- 1 root root 633 May 18 16:40 adlists.list
-rw-r--r-- 1 root root 17 May 21 16:37 GitHubVersions
-rw-r--r-- 1 root root 4353705 May 21 18:50 gravity.list
-rw-r--r-- 1 root root 1321 May 21 18:50 install.log
-rw------- 1 root root 1552348 May 21 18:50 list.0.raw.githubusercontent.com.domains
-rw------- 1 root root 480388 May 21 18:50 list.1.mirror1.malwaredomains.com.domains
-rw------- 1 root root 638705 May 21 18:50 list.2.sysctl.org.domains
-rw------- 1 root root 7128 May 21 18:50 list.3.zeustracker.abuse.ch.domains
-rw------- 1 root root 613 May 21 18:50 list.4.s3.amazonaws.com.domains
-rw------- 1 root root 43642 May 21 18:50 list.5.s3.amazonaws.com.domains
-rw------- 1 root root 1772023 May 21 18:50 list.6.hosts-file.net.domains
-rw-r--r-- 1 root root 2766470 May 21 18:50 list.preEventHorizon
-rw-r--r-- 1 root root 15 May 21 19:40 localbranches
-rw-r--r-- 1 root root 46 May 21 18:50 local.list
-rw-r--r-- 1 root root 41 May 21 19:40 localversions
-rw-r--r-- 1 root root 234 May 21 18:50 logrotate
-rw-r--r-- 1 pihole pihole 20480 May 21 19:49 pihole-FTL.db
-rw-r--r-- 1 pihole pihole 20480 May 21 18:34 pihole-FTL.db.old
-rw-r--r-- 1 root root 239 May 21 18:50 setupVars.conf
-rw-r--r-- 1 root root 239 May 21 18:50 setupVars.conf.update.bak
-rw-r--r-- 1 root root 117 May 18 16:40 whitelist.txt
What is the output of /var/log/pihole.log ?
File output is quite huge, is there a way to attach the file to you here?
I'd say the last 5-6 lines will be enough ...
May 22 08:56:13 dnsmasq[30177]: query[A] 00:11:32:2C:68:44 from 192.168.7.2
May 22 08:56:13 dnsmasq[30177]: cached 00:11:32:2C:68:44 is NXDOMAIN
May 22 08:56:14 dnsmasq[30177]: query[A] 00:12:3F:CF:E7:A9 from 192.168.7.2
May 22 08:56:14 dnsmasq[30177]: cached 00:12:3F:CF:E7:A9 is NXDOMAIN
May 22 08:56:14 dnsmasq[30177]: query[AAAA] dns.msftncsi.com from 192.168.7.1
May 22 08:56:14 dnsmasq[30177]: cached dns.msftncsi.com is fd3e:4f5a:5b81::1
May 22 08:56:14 dnsmasq[30177]: query[A] dns.msftncsi.com from 192.168.7.1
May 22 08:56:14 dnsmasq[30177]: cached dns.msftncsi.com is 131.107.255.255
May 22 08:56:19 dnsmasq[30177]: query[AAAA] dns.msftncsi.com from 192.168.7.1
May 22 08:56:19 dnsmasq[30177]: cached dns.msftncsi.com is fd3e:4f5a:5b81::1
May 22 08:56:19 dnsmasq[30177]: query[A] dns.msftncsi.com from 192.168.7.1
May 22 08:56:19 dnsmasq[30177]: cached dns.msftncsi.com is 131.107.255.255
Something is really jacked up there.
I've never seen MAC addresses to be "requested" for resolving (one is your Synology and the other is a Dell).
Something in your network is doing that and you need to fix it first.
Here's a good read about arp
http://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/arp.html
teah i wa wondering why the nxdomain stuff was in there too.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.