Networking and Pi-Hole.....

Question

Now THAT headline has GOT to get your attention.&nbsp; LOL!!!!!I purchased two Raspberry Pi Canakits from Amazon Canada. ( https://www.amazon.ca/CanaKit-Raspberry-Starter-Premium-Black/dp/B07BCC8PK7/ref=sr_1_6?ie=UTF8&amp;qid=1546727480&amp;sr=8-6&amp;keywords=canakit+raspberry+pi+3+b%2B ) and made one a Retropie Build and one a Pi-Hole build. ( For more information on Pi-Hole look here: https://pi-hole.net/ )I may be an excellent builder and storekeeper but I know next to nothing about networking.&nbsp; Setting DNS and IP addresses makes my head swim.&nbsp; Does anyone here know anything about that and what I am doing wrong with that software?here is the Pi-Hole Log if anyone is interested.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 ] 2019-01-05:17:22:43 debug log has been initialized.*** [ INITIALIZING ] Sourcing setup variables Sourcing /etc/pihole/setupVars.conf...*** [ DIAGNOSING ]: Core version Core: v4.1.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249) Branch: master Commit: v4.1.1-0-g8d85d46*** [ DIAGNOSING ]: Web version Web: v4.1.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249) Branch: master Commit: v4.1.1-0-gde7aa5a*** [ DIAGNOSING ]: FTL version[✓] FTL: v4.1.2*** [ DIAGNOSING ]: lighttpd version 1.4.45*** [ DIAGNOSING ]: php version 7.0.33*** [ DIAGNOSING ]: Operating system[✓] Raspbian GNU/Linux 9 (stretch)*** [ DIAGNOSING ]: SELinux SELinux not detected*** [ DIAGNOSING ]: Processor[✓] armv7l*** [ DIAGNOSING ]: Networking[✓] IPv4 address(es) bound to the eth0 interface:   192.168.1.105/24 matches the IP found in /etc/pihole/setupVars.conf[✓] IPv6 address(es) bound to the eth0 interface:   fe80::ee5d:eabd:2c7f:98a1 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. Default IPv4 gateway: 192.168.1.1192.168.1.1   * Pinging 192.168.1.1192.168.1.1...[✓] Gateway responded.*** [ DIAGNOSING ]: Ports in use*:22 sshd (IPv4)*:22 sshd (IPv6) is in use by lighttpd is in use by lighttpd is in use by pihole-FTL 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[✓] bob701.web3000.com is 0.0.0.0 via localhost (127.0.0.1)[✓] bob701.web3000.com is 0.0.0.0 via Pi-hole (192.168.1.105)[✓] doubleclick.com is 172.217.2.174 via a remote, public DNS server (8.8.8.8)*** [ DIAGNOSING ]: Pi-hole processes[✓] lighttpd daemon is active[✓] pihole-FTL daemon is active*** [ DIAGNOSING ]: Setup variables    PIHOLE_INTERFACE=eth0    IPV4_ADDRESS=192.168.1.105/24    IPV6_ADDRESS=    QUERY_LOGGING=true    INSTALL_WEB_SERVER=true    INSTALL_WEB_INTERFACE=true    LIGHTTPD_ENABLED=true    BLOCKING_ENABLED=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_ACTIVE=false    DNSMASQ_LISTENING=single    PIHOLE_DNS_1=1.1.1.1    PIHOLE_DNS_2=1.0.0.1    DNS_FQDN_REQUIRED=true    DNS_BOGUS_PRIV=true    DNSSEC=false    CONDITIONAL_FORWARDING=false*** [ 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 3221543 Jan  5 17:08 /etc/pihole/gravity.list   -----head of gravity.list------   -x3.vindicosuite.com   0-hjsochvj-ios-1-2-3.mobile-sdk-api.intercom.io   0-jovd32f9-ios-7-0-1.mobile-sdk-api.intercom.io   0.0.0.0   -----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 Jan  3 19:34 /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 12 Jan  5 17:07 /etc/pihole/blacklist.txt   addthis.com-rw-r--r-- 1 root root 48 Jan  5 17:08 /etc/pihole/local.list   192.168.1.105 raspberrypi   192.168.1.105 pi.hole-rw-r--r-- 1 root root 234 Jan  3 19:36 /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 Jan  3 20:50 /etc/pihole/whitelist.txt*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d-rw-r--r-- 1 root root 1438 Jan  5 17:00 /etc/dnsmasq.d/01-pihole.conf   addn-hosts=/etc/pihole/gravity.list   addn-hosts=/etc/pihole/black.list   addn-hosts=/etc/pihole/local.list   user=pihole   group=pihole   localise-queries   no-resolv   cache-size=10000   log-queries   log-facility=/var/log/pihole.log   local-ttl=2   log-async   server=1.1.1.1   server=1.0.0.1   domain-needed   bogus-priv   interface=eth0*** [ DIAGNOSING ]: contents of /etc/lighttpd-rw-r--r-- 1 root root 3102 Jan  3 19:36 /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&gt;/dev/null"   $HTTP["url"] =~ "^/admin/" {              setenv.add-response-header = (           "X-Pi-hole" =&gt; "The Pi-hole Web interface is working!",           "X-Frame-Options" =&gt; "DENY"       )       $HTTP["url"] =~ ".ttf$" {                      setenv.add-response-header = ( "Access-Control-Allow-Origin" =&gt; "*" )       }   }   $HTTP["url"] =~ "^/admin/\.(.*)" {        url.access-deny = ("")   }   include_shell "cat external.conf 2&gt;/dev/null"*** [ DIAGNOSING ]: contents of /etc/cron.d-rw-r--r-- 1 root root 1704 Jan  3 19:36 /etc/cron.d/pihole   24 3   * * 7   root    PATH="$PATH:/usr/local/bin/" pihole updateGravity &gt;/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   36 13  * * *   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 3389 Jan  5 17:07 /var/log/lighttpd/error.log   2019-01-03 19:35:26: (log.c.217) server started    2019-01-03 19:36:59: (server.c.1828) server stopped by UID = 0 PID = 1    2019-01-03 19:36:59: (log.c.217) server started    2019-01-03 19:36:59: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)    2019-01-03 19:41:23: (server.c.1828) server stopped by UID = 0 PID = 1    2019-01-03 19:41:30: (log.c.217) server started    2019-01-03 19:41:30: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)    2019-01-03 19:42:47: (server.c.1828) server stopped by UID = 0 PID = 1    2019-01-03 19:42:55: (log.c.217) server started    2019-01-03 19:42:55: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)    2019-01-03 20:27:54: (server.c.1828) server stopped by UID = 0 PID = 1    2019-01-03 20:28:01: (log.c.217) server started    2019-01-03 20:28:01: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)    2019-01-03 20:41:14: (server.c.1828) server stopped by UID = 0 PID = 1    2019-01-03 20:41:21: (log.c.217) server started    2019-01-03 20:41:21: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)    2019-01-03 20:50:49: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice:  Undefined variable: api in /var/www/html/admin/scripts/pi-hole/php/add.php on line 14   2019-01-03 20:50:54: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice:  Undefined variable: api in /var/www/html/admin/scripts/pi-hole/php/add.php on line 14   2019-01-03 20:50:58: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice:  Undefined variable: api in /var/www/html/admin/scripts/pi-hole/php/add.php on line 14   2019-01-03 20:51:26: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice:  Undefined variable: api in /var/www/html/admin/scripts/pi-hole/php/sub.php on line 16   2019-01-03 20:51:27: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice:  Undefined variable: api in /var/www/html/admin/scripts/pi-hole/php/sub.php on line 16   2019-01-03 20:54:00: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice:  Undefined variable: api in /var/www/html/admin/scripts/pi-hole/php/add.php on line 14   2019-01-03 20:54:41: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice:  Undefined variable: api in /var/www/html/admin/scripts/pi-hole/php/sub.php on line 16   2019-01-03 20:54:50: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice:  Undefined variable: api in /var/www/html/admin/scripts/pi-hole/php/add.php on line 14   2019-01-03 21:22:27: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Notice:  Undefined variable: api in /var/www/html/admin/scripts/pi-hole/php/add.php on line 14*** [ DIAGNOSING ]: contents of /var/log-rw-r--r-- 1 pihole pihole 14248 Jan  5 17:08 /var/log/pihole-FTL.log   -----head of pihole-FTL.log------   [2019-01-05 04:43:52.376] Notice: Increasing overTime struct size from 200 to 300   [2019-01-05 13:38:25.601] Notice: Increasing clients struct size from 10 to 20   [2019-01-05 17:00:28.522] Shutting down...   [2019-01-05 17:00:28.619] Finished final database update   [2019-01-05 17:00:28.619] ########## FTL terminated after 157325456.0 ms! ##########   [2019-01-05 17:00:30.062] Using log file /var/log/pihole-FTL.log   [2019-01-05 17:00:30.062] ########## FTL started! ##########   [2019-01-05 17:00:30.062] FTL branch: master   [2019-01-05 17:00:30.062] FTL version: v4.1.2   [2019-01-05 17:00:30.062] FTL commit: b06eedf   [2019-01-05 17:00:30.063] FTL date: 2018-12-21 14:43:34 -0600   [2019-01-05 17:00:30.063] FTL user: pihole   [2019-01-05 17:00:30.063] Starting config file parsing (/etc/pihole/pihole-FTL.conf)   [2019-01-05 17:00:30.063]    SOCKET_LISTENING: only local   [2019-01-05 17:00:30.063]    AAAA_QUERY_ANALYSIS: Show AAAA queries   [2019-01-05 17:00:30.063]    MAXDBDAYS: max age for stored queries is 365 days   [2019-01-05 17:00:30.063]    RESOLVE_IPV6: Resolve IPv6 addresses   [2019-01-05 17:00:30.063]    RESOLVE_IPV4: Resolve IPv4 addresses   [2019-01-05 17:00:30.063]    DBINTERVAL: saving to DB file every minute   [2019-01-05 17:00:30.063]    DBFILE: Using /etc/pihole/pihole-FTL.db   [2019-01-05 17:00:30.063]    MAXLOGAGE: Importing up to 24.0 hours of log data   [2019-01-05 17:00:30.063]    PRIVACYLEVEL: Set to 0   [2019-01-05 17:00:30.063]    IGNORE_LOCALHOST: Show queries from localhost   [2019-01-05 17:00:30.063]    BLOCKINGMODE: Null IPs for blocked domains   [2019-01-05 17:00:30.063]    REGEX_DEBUGMODE: Inactive   [2019-01-05 17:00:30.063]    ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries   [2019-01-05 17:00:30.063]    DBIMPORT: Importing history from database   [2019-01-05 17:00:30.063]    PIDFILE: Using /var/run/pihole-FTL.pid   [2019-01-05 17:00:30.063]    PORTFILE: Using /var/run/pihole-FTL.port   [2019-01-05 17:00:30.063]    SOCKETFILE: Using /var/run/pihole/FTL.sock   [2019-01-05 17:00:30.063]    WHITELISTFILE: Using /etc/pihole/whitelist.txt   [2019-01-05 17:00:30.063]    BLACKLISTFILE: Using /etc/pihole/black.list   [2019-01-05 17:00:30.064]    GRAVITYFILE: Using /etc/pihole/gravity.list   [2019-01-05 17:00:30.064]    REGEXLISTFILE: Using /etc/pihole/regex.list   [2019-01-05 17:00:30.064]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf   -----tail of pihole-FTL.log------   [2019-01-05 17:04:56.044] Notice: Increasing clients struct size from 0 to 10   [2019-01-05 17:04:56.044] New forward server: 8.8.4.4 (0/0)   [2019-01-05 17:04:56.044] Notice: Increasing forwarded struct size from 0 to 4   [2019-01-05 17:04:56.044] Notice: Increasing overTime struct size from 0 to 100   [2019-01-05 17:04:56.044] New forward server: 8.8.8.8 (1/4)   [2019-01-05 17:04:56.067] Notice: Increasing overTime struct size from 100 to 200   [2019-01-05 17:04:56.077] Notice: Increasing clients struct size from 10 to 20   [2019-01-05 17:04:56.085] New forward server: 1.0.0.1 (2/4)   [2019-01-05 17:04:56.085] New forward server: 1.1.1.1 (3/4)   [2019-01-05 17:04:56.087] Imported 4301 queries from the long-term database   [2019-01-05 17:04:56.087]  -&gt; Total DNS queries: 4301   [2019-01-05 17:04:56.087]  -&gt; Cached DNS queries: 873   [2019-01-05 17:04:56.087]  -&gt; Forwarded DNS queries: 2977   [2019-01-05 17:04:56.087]  -&gt; Exactly blocked DNS queries: 451   [2019-01-05 17:04:56.087]  -&gt; Unknown DNS queries: 0   [2019-01-05 17:04:56.087]  -&gt; Unique domains: 848   [2019-01-05 17:04:56.087]  -&gt; Unique clients: 12   [2019-01-05 17:04:56.087]  -&gt; Known forward destinations: 4   [2019-01-05 17:04:56.087] Successfully accessed setupVars.conf   [2019-01-05 17:04:56.096] PID of FTL process: 920   [2019-01-05 17:04:56.096] Listening on port 4711 for incoming IPv4 telnet connections   [2019-01-05 17:04:56.097] Listening on port 4711 for incoming IPv6 telnet connections   [2019-01-05 17:04:56.097] Listening on Unix socket   [2019-01-05 17:04:56.099] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)   [2019-01-05 17:04:56.102] /etc/pihole/black.list: parsed 1 domains (took 0.0 ms)   [2019-01-05 17:04:56.859] /etc/pihole/gravity.list: parsed 136632 domains (took 755.9 ms)   [2019-01-05 17:07:26.606] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)   [2019-01-05 17:07:26.792] /etc/pihole/black.list: parsed 2 domains (took 0.0 ms)   [2019-01-05 17:07:27.346] /etc/pihole/gravity.list: parsed 136632 domains (took 553.9 ms)   [2019-01-05 17:07:59.432] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)   [2019-01-05 17:07:59.618] /etc/pihole/black.list: parsed 1 domains (took 0.0 ms)   [2019-01-05 17:08:00.172] /etc/pihole/gravity.list: parsed 136632 domains (took 553.8 ms)   [2019-01-05 17:08:19.147] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)   [2019-01-05 17:08:19.333] /etc/pihole/black.list: parsed 1 domains (took 0.0 ms)   [2019-01-05 17:08:19.944] /etc/pihole/gravity.list: parsed 136428 domains (took 611.0 ms)*** [ DIAGNOSING ]: Locale    LANG=*** [ DIAGNOSING ]: Pi-hole log-rw-r--r-- 1 pihole pihole 1178382 Jan  5 17:22 /var/log/pihole.log   -----head of pihole.log------   Jan  5 00:00:29 dnsmasq[3765]: query cl3.apple.com from 192.168.1.147   Jan  5 00:00:29 dnsmasq[3765]: forwarded cl3.apple.com to 8.8.8.8   Jan  5 00:00:29 dnsmasq[3765]: reply cl3.apple.com is &lt;CNAME&gt;   Jan  5 00:00:29 dnsmasq[3765]: reply cl3-cdn.origin-apple.com.akadns.net is &lt;CNAME&gt;   Jan  5 00:00:29 dnsmasq[3765]: reply cl5.apple.com.edgekey.net is &lt;CNAME&gt;   Jan  5 00:00:29 dnsmasq[3765]: reply e14868.dsce9.akamaiedge.net is 23.197.155.175   Jan  5 00:00:29 dnsmasq[3765]: query time-ios.g.aaplimg.com from 192.168.1.147   Jan  5 00:00:29 dnsmasq[3765]: forwarded time-ios.g.aaplimg.com to 8.8.8.8   Jan  5 00:00:29 dnsmasq[3765]: reply time-ios.g.aaplimg.com is 17.253.14.253   Jan  5 00:00:29 dnsmasq[3765]: reply time-ios.g.aaplimg.com is 17.253.14.125   Jan  5 00:00:29 dnsmasq[3765]: reply time-ios.g.aaplimg.com is 17.253.20.125   Jan  5 00:07:11 dnsmasq[3765]: query e12930.ksd.akamaiedge.net from 192.168.1.147   Jan  5 00:07:11 dnsmasq[3765]: forwarded e12930.ksd.akamaiedge.net to 8.8.8.8   Jan  5 00:07:12 dnsmasq[3765]: reply e12930.ksd.akamaiedge.net is 23.197.108.236   Jan  5 00:11:36 dnsmasq[3765]: query time-ios.g.aaplimg.com from 192.168.1.127   Jan  5 00:11:36 dnsmasq[3765]: forwarded time-ios.g.aaplimg.com to 8.8.4.4   Jan  5 00:11:36 dnsmasq[3765]: forwarded time-ios.g.aaplimg.com to 8.8.8.8   Jan  5 00:11:36 dnsmasq[3765]: reply time-ios.g.aaplimg.com is 17.253.14.253   Jan  5 00:11:36 dnsmasq[3765]: reply time-ios.g.aaplimg.com is 17.253.14.125   Jan  5 00:11:36 dnsmasq[3765]: reply time-ios.g.aaplimg.com is 17.253.20.125****************************************************************************************[✓] ** FINISHED DEBUGGING! **    * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.    * For more information, see: https://pi-hole.net/2016/11/07/crack-our-medical-tricorder-win-a-raspberry-pi-3/    * If available, we'll use openssl to upload the log, otherwise it will fall back to netcat. Debug script running in automated mode    * Using openssl for transmission.**********************************************************************[✓] Your debug token is: wu2f2cobox**********************************************************************   * Provide the token above to the Pi-hole team for assistance at   * https://discourse.pi-hole.net   * Your log will self-destruct on our server after 48 hours.   * A local copy of the debug log can be found at: /var/log/pihole_debug-sanitized.log

Zenbane · Answer

kojack · Answer

What exactly is wrong?I've never heard of pihole, but the logs don't seem to show anything going wrong. It tested a known adware address and it was correctly routed to 0.0.0.0.I'm going to guess that the problem you have is that the PC isn't having ads blocked.(I don't know how much you know about what this is doing, so this is for anybody reading this)Pihole works as a DNS (Domain Name System). DNS servers are computers that convert URLs like www.oculus.com into IP addresses like 157.240.8.49.Normally you'd use a DNS from your internet provider, or Google's one (at 8.8.8.8). But instead you redirect your computer to use Pihole on a raspberry pi on your network instead. It passes DNS requests on to the real server, but any known ad address is blocked.It does look like Pihole is running. So I guess your PC isn't using it. There's a few way to set it up:- change router settings to redirect all DNS queries to the pihole- use the pihole as a DHCP server (also needs router changes)- manually set your devices to use the pihole.Since every router/cable modem/etc is different, it's hard to say how easy the first two options are. But they would let you block ads for smart tvs, phones, etc.The third is pretty easy on a PC, which might be a good idea for testing if the pihole is working.But that depends on which OS you have and if you are running on wifi or ethernet and ip4 or ip6.So we need a little more info.

Digikid1 · Answer

Exactly @kojack. Still seeing ads. It wanted me to make a static DCHP and static ip for it through my router. I use a Linksys WRT1900AC V2 with DRT. This is an area that I have no experience at all and would normally get my networking employee to do but unfortunately he passed a couple months ago due to a nasty car accident. I thought that I had done it right but nope.

Running it on ethernet and wifi as recommended. Some things are working....just not all. For example I go to oc3d.com and still get the ads. However On my iPhone the games that forces ads have diminished a bit but not completely.

Digikid1 · Answer

Oh and the Pi is running Raspbian.&nbsp;

Anonymous · Answer

Nothing better than watching two Raspbians making out. &lt;3

Forum Discussion

Networking and Pi-Hole.....

7 Replies

Related Content

Colocation with Networked Avatars

Network error only on meta apps

Meta Quest Pro WiFi setup fail on university network

Send network event to server

Making Quest 3 discoverable through local network