Pi-hole not blocking ads but active

Please follow the below template, it will help us to help you!

I installed Pi-hole on my raspberry Pi 3, set my router's only DNS option to be the raspberry pi's ip4 and ip6 address. Also tried setting my computer network settings to use the raspberry pi's ipv4 address as its DNS and that doesn't work either. On the admin page it shows the number of queries occurring but the number blocked remains 0 and I continue to have ads.

Expected Behaviour:

Pi-hole blocking all ads

Actual Behaviour:

Pi-hole receiving queries and showing connected clients but not blocking anything

Debug Token:

Installer log

  [i] Existing PHP installation detected : PHP version 5.6.40-0+deb8u6
  [i] Reconfigure option selected
  [✓] Disk space check
  [✓] Update local cache of available packages

  [✓] Checking apt-get for upgraded packages... 1 updates available
  [i] It is recommended to update your OS after installing the Pi-hole!

  [i] Installer Dependency checks...
  [✓] Checking for apt-utils
  [✓] Checking for dialog
  [✓] Checking for debconf
  [✓] Checking for dhcpcd5
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for whiptail

  [i] Using Google (ECS)
  [i] Static IP already configured
  [i] Found IPv6 GUA address, using it for blocking IPv6 ads
  [i] IPv4 address: 192.168.1.2/24
  [i] IPv6 address: 2600:6c44:c7f:ffe2:f894:5ac6:f294:12ca
  [i] Web Interface On
  [i] Web Server On
  [i] Logging On.
  [i] Privacy level 0  [i] Performing reconfiguration, skipping download of local repos
  [✓] Resetting repository within /etc/.pihole...
  [✓] Resetting repository within /var/www/html/admin...
  [i] Main Dependency checks...
  [✓] Checking for cron
  [✓] Checking for curl
  [✓] Checking for dnsutils
  [✓] Checking for iputils-ping
  [✓] Checking for lsof
  [✓] Checking for netcat
  [✓] Checking for psmisc
  [✓] Checking for sudo
  [✓] Checking for unzip
  [✓] Checking for wget
  [✓] Checking for idn2
  [✓] Checking for sqlite3
  [✓] Checking for libcap2-bin
  [✓] Checking for dns-root-data
  [✓] Checking for resolvconf
  [✓] Checking for libcap2
  [✓] Checking for lighttpd
  [✓] Checking for php5-common
  [✓] Checking for php5-cgi
  [✓] Checking for php5-sqlite

  [✓] Enabling lighttpd service to start on reboot...

  [i] FTL Checks...

  [✓] Detected ARM-hf architecture (armv7+)
  [i] Checking for existing FTL binary...
  [i] Latest FTL Binary already installed (v4.3.1). Confirming Checksum...
  [i] Checksum correct. No need to download!
  [✓] Checking for user 'pihole'
  [✓] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

  [i] Installing blocking page...
  [✓] Creating directory for blocking page, and copying files
  [✗] Backing up index.lighttpd.html
      No default index.lighttpd.html file found... not backing up

  [✓] Installing sudoer file

  [✓] Installing latest Cron script

  [✓] Installing latest logrotate script
  [i] Backing up /etc/dnsmasq.conf to /etc/dnsmasq.conf.old

  [i] Skipping firewall configuration
  [✓] man pages installed and database updated
  [i] Testing if systemd-resolved is enabled
  [i] Systemd-resolved is not enabled
  [✓] Restarting lighttpd service...
  [✓] Enabling lighttpd service to start on reboot...
  [i] Restarting services...
  [✓] Enabling pihole-FTL service to start on reboot...
  [✓] Restarting pihole-FTL service...
  [✓] Deleting existing list cache
  [i] Pi-hole blocking is enabled
  [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range

  [i] Target: raw.githubusercontent.com (hosts)
  [✓] Status: Retrieval successful

  [i] Target: mirror1.malwaredomains.com (justdomains)
  [✓] Status: Retrieval successful

  [i] Target: sysctl.org (hosts)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_tracking.txt)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_ad.txt)
  [✓] Status: Retrieval successful

  [i] Target: hosts-file.net (ad_servers.txt)
  [✓] Status: Retrieval successful

  [✓] Consolidating blocklists
  [✓] Extracting domains from blocklists
  [i] Number of domains being pulled in by gravity: 135667
  [✓] Removing duplicate domains
  [i] Number of unique domains trapped in the Event Horizon: 113448
  [i] Number of whitelisted domains: 0
  [i] Number of blacklisted domains: 0
  [i] Number of regex filters: 0
  [✓] Parsing domains into hosts format
  [✓] Cleaning up stray matter

  [✓] Force-reloading DNS service
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled
  [i] View the web interface at http://pi.hole/admin or http://192.168.1.2/admin

  [i] You may now configure your devices to use the Pi-hole as their DNS server
  [i] Pi-hole DNS (IPv4): 192.168.1.2
  [i] Pi-hole DNS (IPv6): 2600:6c44:c7f:ffe2:f894:5ac6:f294:12ca
  [i] If you set a new IP address, please restart the server running the Pi-hole

  [i] The install log is located at: /etc/pihole/install.log
Installation Complete!
pi@raspberrypi:~ $ pihole -d

*** [ INITIALIZING ]
[i] 2019-10-14:20:02:28 debug log has been initialized.

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...

*** [ DIAGNOSING ]: Core version
[i] Core: v4.3.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.3.2-0-ge41c4b5

*** [ DIAGNOSING ]: Web version
[i] Web: v4.3.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.3.2-0-g38d8e77

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v4.3.1

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.35

*** [ DIAGNOSING ]: php version
[i] 5.6.40

*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 8 (jessie)

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: Processor
[✓] armv7l

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
   192.168.1.2/24 matches the IP found in /etc/pihole/setupVars.conf

[✓] IPv6 address(es) bound to the eth0 interface:
   2600:6c44:c7f:ffe2:0:eba7:6033:5943 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)
   2600:6c44:c7f:ffe2:f894:5ac6:f294:12ca matches the IP found in /etc/pihole/setupVars.conf
   fe80::8026:cd5d:a3da:6947 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.1.1
   * Pinging 192.168.1.1...
[✓] Gateway responded.
[i] Default IPv6 gateway: fe80::5a90:43ff:fee0:7a50
   * Pinging fe80::5a90:43ff:fee0:7a50...
[✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
[::1]:631 cupsd (IPv6)
127.0.0.1:631 cupsd (IPv4)
*:5900 vncserver- (IPv6)
*:5900 vncserver- (IPv4)
*:22 sshd (IPv4)
*:22 sshd (IPv6)
*:6001 Xvnc-core (IPv6)
*:6001 Xvnc-core (IPv4)
*:5901 Xvnc-core (IPv6)
*:5901 Xvnc-core (IPv4)
[*:80] is in use by lighttpd
[*:80] is in use by lighttpd
[*:53] is in use by pihole-FTL
[*:53] is in use by pihole-FTL
[127.0.0.1:4711] is in use by pihole-FTL
[[::1]:4711] is in use by pihole-FTL

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] atdmt.com.46618.9304.302br.net is 0.0.0.0 via localhost (127.0.0.1)
[✓] atdmt.com.46618.9304.302br.net is 0.0.0.0 via Pi-hole (192.168.1.2)
[✓] doubleclick.com is 172.217.8.206 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] analsexhard.com is :: via localhost (::1)
[✓] analsexhard.com is :: via Pi-hole (2600:6c44:c7f:ffe2:f894:5ac6:f294:12ca)
[✓] doubleclick.com is 2607:f8b0:4009:816::200e via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Pi-hole processes
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

*** [ DIAGNOSING ]: Setup variables
    BLOCKING_ENABLED=true
    DHCP_ACTIVE=true
    DHCP_START=192.168.1.201
    DHCP_END=192.168.1.251
    DHCP_ROUTER=192.168.1.1
    DHCP_LEASETIME=24
    PIHOLE_DOMAIN=lan
    DHCP_IPv6=false
    DHCP_rapid_commit=false
    PIHOLE_INTERFACE=eth0
    IPV4_ADDRESS=192.168.1.2/24
    IPV6_ADDRESS=2600:6c44:c7f:ffe2:f894:5ac6:f294:12ca
    PIHOLE_DNS_1=8.8.8.8
    PIHOLE_DNS_2=8.8.4.4
    QUERY_LOGGING=true
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=true

*** [ 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 2654708 Oct 14 19:59 /etc/pihole/gravity.list
   -----head of gravity.list------
   0.0.0.0
   0.nextyourcontent.com
   0.r.msn.com
   0.start.bz

   -----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 313 Oct 14 19:58 /etc/pihole/adlists.list
   https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
   https://mirror1.malwaredomains.com/files/justdomains
   http://sysctl.org/cameleon/hosts
   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 Oct 14 19:04 /etc/pihole/blacklist.txt

-rw-r--r-- 1 root root 142 Oct 14 19:59 /etc/pihole/local.list
   192.168.1.2 raspberrypi
   2600:6c44:c7f:ffe2:f894:5ac6:f294:12ca raspberrypi
   192.168.1.2 pi.hole
   2600:6c44:c7f:ffe2:f894:5ac6:f294:12ca pi.hole

-rw-r--r-- 1 root root 234 Oct 14 19:58 /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 0 Oct 14 19:04 /etc/pihole/whitelist.txt

*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d

-rw-r--r-- 1 root root 1387 Oct 14 19:58 /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
   log-facility=/var/log/pihole.log
   local-ttl=2
   log-async
   server=8.8.8.8
   server=8.8.4.4
   interface=eth0

-rw-r--r-- 1 root root 483 Oct 14 19:58 /etc/dnsmasq.d/02-pihole-dhcp.conf
   dhcp-authoritative
   dhcp-range=192.168.1.201,192.168.1.251,24h
   dhcp-option=option:router,192.168.1.1
   dhcp-leasefile=/etc/pihole/dhcp.leases
   domain=lan

*** [ DIAGNOSING ]: contents of /etc/lighttpd

-rw-r--r-- 1 root root 3499 Oct 14 19:58 /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" )
   mimetype.assign   = ( ".png"  => "image/png",
                         ".jpg"  => "image/jpeg",
                         ".jpeg" => "image/jpeg",
                         ".html" => "text/html",
                         ".css" => "text/css; charset=utf-8",
                         ".js" => "application/javascript",
                         ".json" => "application/json",
                         ".txt"  => "text/plain",
                         ".svg"  => "image/svg+xml" )
   include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
   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 1703 Oct 14 19:58 /etc/cron.d/pihole
   4 4   * * 7   root    PATH="$PATH:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log
   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
   18 17  * * *   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 1791 Oct 14 19:58 /var/log/lighttpd/error.log
   2019-10-14 00:47:51: (log.c.164) server started 
   2019-10-14 00:48:18: (server.c.1558) server stopped by UID = 0 PID = 1 
   2019-10-14 00:48:19: (log.c.164) server started 
   2019-10-14 00:48:19: (server.c.1045) WARNING: unknown config-key: alias.url (ignored) 
   2019-10-14 00:50:33: (server.c.1558) server stopped by UID = 0 PID = 1 
   2019-10-14 00:50:38: (log.c.164) server started 
   2019-10-14 00:50:38: (server.c.1045) WARNING: unknown config-key: alias.url (ignored) 
   2019-10-14 00:50:38: (log.c.164) server started 
   2019-10-14 00:50:38: (server.c.1045) WARNING: unknown config-key: alias.url (ignored) 
   2019-10-14 18:34:43: https://dts.innovid.com/clktru/action/vclk?project_hash=1hcbsl&client_id=3997&video_id=485798&channel_id=1537374&publisher_id=888&placement_tag_id=0&project_state=2&r=1571096067036&placement_hash=1mn4e4&device_id=&action=clktru&click=https%3A%2F%2Fad.doubleclick.net%2Fddm%2Ftrackclk%2FN6344.646586TWITCHINTERACTIVEINC%2FB22910919.256721375%3Bdc_trk_aid%3D453033586%3Bdc_trk_cid%3D99808761%3Bdc_lat%3D%3Bdc_rdid%3D%3Btag_for_child_directed_treatment%3D%3Btfua%3D&ivc_exdata= is not a valid domain
   2019-10-14 18:54:46: (server.c.1558) server stopped by UID = 0 PID = 1 
   2019-10-14 18:54:51: (log.c.164) server started 
   2019-10-14 18:54:51: (server.c.1045) WARNING: unknown config-key: alias.url (ignored) 
   2019-10-14 19:55:15: (server.c.1558) server stopped by UID = 0 PID = 1 
   2019-10-14 19:55:15: (log.c.164) server started 
   2019-10-14 19:55:15: (server.c.1045) WARNING: unknown config-key: alias.url (ignored) 
   2019-10-14 19:58:40: (server.c.1558) server stopped by UID = 0 PID = 1 
   2019-10-14 19:58:41: (log.c.164) server started 
   2019-10-14 19:58:41: (server.c.1045) WARNING: unknown config-key: alias.url (ignored) 

*** [ DIAGNOSING ]: contents of /var/log

-rw-r--r-- 1 pihole pihole 31805 Oct 14 19:59 /var/log/pihole-FTL.log
   -----head of pihole-FTL.log------
   [2019-10-14 00:48:31.183 8390] Using log file /var/log/pihole-FTL.log
   [2019-10-14 00:48:31.183 8390] ########## FTL started! ##########
   [2019-10-14 00:48:31.183 8390] FTL branch: master
   [2019-10-14 00:48:31.183 8390] FTL version: v4.3.1
   [2019-10-14 00:48:31.183 8390] FTL commit: b60d63f
   [2019-10-14 00:48:31.183 8390] FTL date: 2019-05-25 21:37:26 +0200
   [2019-10-14 00:48:31.183 8390] FTL user: pihole
   [2019-10-14 00:48:31.183 8390] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
   [2019-10-14 00:48:31.184 8390]    SOCKET_LISTENING: only local
   [2019-10-14 00:48:31.184 8390]    AAAA_QUERY_ANALYSIS: Show AAAA queries
   [2019-10-14 00:48:31.184 8390]    MAXDBDAYS: max age for stored queries is 365 days
   [2019-10-14 00:48:31.184 8390]    RESOLVE_IPV6: Resolve IPv6 addresses
   [2019-10-14 00:48:31.184 8390]    RESOLVE_IPV4: Resolve IPv4 addresses
   [2019-10-14 00:48:31.184 8390]    DBINTERVAL: saving to DB file every minute
   [2019-10-14 00:48:31.184 8390]    DBFILE: Using /etc/pihole/pihole-FTL.db
   [2019-10-14 00:48:31.184 8390]    MAXLOGAGE: Importing up to 24.0 hours of log data
   [2019-10-14 00:48:31.184 8390]    PRIVACYLEVEL: Set to 0
   [2019-10-14 00:48:31.184 8390]    IGNORE_LOCALHOST: Show queries from localhost
   [2019-10-14 00:48:31.184 8390]    BLOCKINGMODE: Null IPs for blocked domains
   [2019-10-14 00:48:31.184 8390]    ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
   [2019-10-14 00:48:31.184 8390]    DBIMPORT: Importing history from database
   [2019-10-14 00:48:31.184 8390]    PIDFILE: Using /var/run/pihole-FTL.pid
   [2019-10-14 00:48:31.184 8390]    PORTFILE: Using /var/run/pihole-FTL.port
   [2019-10-14 00:48:31.185 8390]    SOCKETFILE: Using /var/run/pihole/FTL.sock
   [2019-10-14 00:48:31.185 8390]    WHITELISTFILE: Using /etc/pihole/whitelist.txt
   [2019-10-14 00:48:31.185 8390]    BLACKLISTFILE: Using /etc/pihole/black.list
   [2019-10-14 00:48:31.185 8390]    GRAVITYFILE: Using /etc/pihole/gravity.list
   [2019-10-14 00:48:31.185 8390]    REGEXLISTFILE: Using /etc/pihole/regex.list
   [2019-10-14 00:48:31.185 8390]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2019-10-14 00:48:31.185 8390]    AUDITLISTFILE: Using /etc/pihole/auditlog.list
   [2019-10-14 00:48:31.185 8390]    MACVENDORDB: Using /etc/pihole/macvendor.db
   [2019-10-14 00:48:31.185 8390]    PARSE_ARP_CACHE: Active
   [2019-10-14 00:48:31.185 8390] Finished config file parsing
   [2019-10-14 00:48:31.186 8390] SQLite3 message: cannot open file at line 38452 of [0eca3dd3d3] (14)
   [2019-10-14 00:48:31.186 8390] SQLite3 message: os_unix.c:38452: (2) open(/etc/pihole/pihole-FTL.db) -  (14)

   -----tail of pihole-FTL.log------
   [2019-10-14 19:58:44.626 6965]    GRAVITYFILE: Using /etc/pihole/gravity.list
   [2019-10-14 19:58:44.626 6965]    REGEXLISTFILE: Using /etc/pihole/regex.list
   [2019-10-14 19:58:44.626 6965]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2019-10-14 19:58:44.626 6965]    AUDITLISTFILE: Using /etc/pihole/auditlog.list
   [2019-10-14 19:58:44.626 6965]    MACVENDORDB: Using /etc/pihole/macvendor.db
   [2019-10-14 19:58:44.626 6965]    PARSE_ARP_CACHE: Active
   [2019-10-14 19:58:44.626 6965] Finished config file parsing
   [2019-10-14 19:58:44.628 6965] Database version is 3
   [2019-10-14 19:58:44.628 6965] Database successfully initialized
   [2019-10-14 19:58:44.629 6965] New forward server: 8.8.4.4 (0/512)
   [2019-10-14 19:58:44.629 6965] New forward server: 8.8.8.8 (1/512)
   [2019-10-14 19:58:44.643 6965] Imported 2242 queries from the long-term database
   [2019-10-14 19:58:44.644 6965]  -> Total DNS queries: 2242
   [2019-10-14 19:58:44.644 6965]  -> Cached DNS queries: 46
   [2019-10-14 19:58:44.644 6965]  -> Forwarded DNS queries: 2184
   [2019-10-14 19:58:44.644 6965]  -> Exactly blocked DNS queries: 0
   [2019-10-14 19:58:44.644 6965]  -> Unknown DNS queries: 12
   [2019-10-14 19:58:44.644 6965]  -> Unique domains: 32
   [2019-10-14 19:58:44.644 6965]  -> Unique clients: 3
   [2019-10-14 19:58:44.644 6965]  -> Known forward destinations: 2
   [2019-10-14 19:58:44.644 6965] Successfully accessed setupVars.conf
   [2019-10-14 19:58:44.672 6967] PID of FTL process: 6967
   [2019-10-14 19:58:44.672 6967] Listening on port 4711 for incoming IPv4 telnet connections
   [2019-10-14 19:58:44.672 6967] Listening on port 4711 for incoming IPv6 telnet connections
   [2019-10-14 19:58:44.672 6967] Listening on Unix socket
   [2019-10-14 19:58:44.674 6967] Received SIGHUP, reloading cache
   [2019-10-14 19:58:44.674 6967] Blocking status is enabled
   [2019-10-14 19:58:44.674 6967] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)
   [2019-10-14 19:58:44.675 6967] /etc/pihole/black.list: parsed 0 domains (took 0.1 ms)
   [2019-10-14 19:58:46.118 6967] /etc/pihole/gravity.list: parsed 113448 domains (took 1443.0 ms)
   [2019-10-14 19:59:54.897 6967] Received SIGHUP, reloading cache
   [2019-10-14 19:59:54.897 6967] Blocking status is enabled
   [2019-10-14 19:59:54.897 6967] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)
   [2019-10-14 19:59:55.134 6967] /etc/pihole/black.list: parsed 0 domains (took 0.1 ms)
   [2019-10-14 19:59:56.029 6967] /etc/pihole/gravity.list: parsed 113448 domains (took 895.1 ms)

*** [ DIAGNOSING ]: contents of /dev/shm
-rw------- 1 pihole pihole 323584 Oct 14 19:58 /dev/shm/FTL-clients
-rw------- 1 pihole pihole 108 Oct 14 19:58 /dev/shm/FTL-counters
-rw------- 1 pihole pihole 65536 Oct 14 19:58 /dev/shm/FTL-domains
-rw------- 1 pihole pihole 12288 Oct 14 19:58 /dev/shm/FTL-forwarded
-rw------- 1 pihole pihole 28 Oct 14 19:58 /dev/shm/FTL-lock
-rw------- 1 pihole pihole 53248 Oct 14 19:58 /dev/shm/FTL-overTime
-rw------- 1 pihole pihole 196608 Oct 14 19:59 /dev/shm/FTL-queries
-rw------- 1 pihole pihole 12 Oct 14 19:58 /dev/shm/FTL-settings
-rw------- 1 pihole pihole 4096 Oct 14 19:58 /dev/shm/FTL-strings

*** [ DIAGNOSING ]: Locale
    LANG=en_GB.UTF-8

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 546704 Oct 14 20:02 /var/log/pihole.log
   -----head of pihole.log------
   Oct 14 00:48:31 dnsmasq[8392]: started, version pi-hole-2.80 cachesize 10000
   Oct 14 00:48:31 dnsmasq[8392]: 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 dumpfile
   Oct 14 00:48:31 dnsmasq[8392]: using nameserver 8.8.4.4#53
   Oct 14 00:48:31 dnsmasq[8392]: using nameserver 8.8.8.8#53
   Oct 14 00:48:31 dnsmasq[8392]: read /etc/hosts - 5 addresses
   Oct 14 00:48:31 dnsmasq[8392]: failed to load names from /etc/pihole/local.list: No such file or directory
   Oct 14 00:48:31 dnsmasq[8392]: failed to load names from /etc/pihole/black.list: No such file or directory
   Oct 14 00:48:31 dnsmasq[8392]: failed to load names from /etc/pihole/gravity.list: No such file or directory
   Oct 14 00:48:31 dnsmasq[8392]: query[AAAA] raw.githubusercontent.com from 127.0.0.1
   Oct 14 00:48:31 dnsmasq[8392]: forwarded raw.githubusercontent.com to 8.8.4.4
   Oct 14 00:48:31 dnsmasq[8392]: forwarded raw.githubusercontent.com to 8.8.8.8
   Oct 14 00:48:31 dnsmasq[8392]: reply raw.githubusercontent.com is <CNAME>
   Oct 14 00:48:31 dnsmasq[8392]: reply github.map.fastly.net is NODATA-IPv6
   Oct 14 00:48:31 dnsmasq[8392]: query[A] raw.githubusercontent.com from 127.0.0.1
   Oct 14 00:48:31 dnsmasq[8392]: cached raw.githubusercontent.com is <CNAME>
   Oct 14 00:48:31 dnsmasq[8392]: forwarded raw.githubusercontent.com to 8.8.8.8
   Oct 14 00:48:31 dnsmasq[8392]: reply raw.githubusercontent.com is <CNAME>
   Oct 14 00:48:31 dnsmasq[8392]: reply github.map.fastly.net is 151.101.0.133
   Oct 14 00:48:31 dnsmasq[8392]: reply github.map.fastly.net is 151.101.64.133
   Oct 14 00:48:31 dnsmasq[8392]: reply github.map.fastly.net is 151.101.128.133

Your debug log shows that Pi-Hole is working properly. Let's look at the connectivity between the clients and Pi-Hole.

What is the output of this command from the Pi terminal:

echo ">stats" | nc localhost 4711

echo ">top-clients withzero" | nc localhost 4711

And from either the terminal or command prompt of a connected client:

nslookup pi.hole

domains_being_blocked 113448
dns_queries_today 2323
ads_blocked_today 4
ads_percentage_today 0.172191
unique_domains 39
queries_forwarded 2230
queries_cached 77
clients_ever_seen 6
unique_clients 6
dns_queries_all_types 2323
reply_NODATA 15
reply_NXDOMAIN 0
reply_CNAME 9
reply_IP 41
privacy_level 0
status enabled
---EOM---

0 2288 127.0.0.1 localhost
1 17 192.168.1.3
2 16 192.168.1.128
3 1 192.168.1.2 raspberrypi
4 1 ::1 localhost
5 1 2600:6c44:c7f:ffe2:f894:5ac6:f294:12ca raspberrypi
---EOM---

Server: 127.0.0.1
Address: 127.0.0.1#53

Name: pi.hole
Address: 192.168.1.2

That last command appears to have been run from the Pi Terminal or via ssh to the terminal, not directly on a connected client.

My bad, here is from a connected client, though something seems wrong here
Server: rns01.charter.com
Address: 2607:f428:ffff:ffff::1

*** rns01.charter.com can't find pi.hole: Non-existent domain

Your debug log shows that you are using Pi-Hole as DHCP, yet the client still has the ISP DNS assigned. After you made the change to use Pi-Hole DHCP, did you renew the DHCP lease on all clients?

Also, disable IPv6 on the router if you can, since the DNS address being pushed is the IPv6 DNS.

Ok, i turned off DHCP on my pi-hole and it appears to be working now, thank you so much for your help. I forgot that while I was trouble shooting I turned that setting on and forgot to turn it back off.

It now shows that it is blocking queries but I am still getting some ads on youtube, might be cached ads from me trying so much recently.

It us difficult to block YouTube ads in Pi-Hole since ads come from subdomains of the content domains. The subdomains and content domains change regularly.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.