Using Pi Hole with AT&T U-Verse as the DCHP sever. There are duplicate leases in Pihole and AT&T, ads still being served. Help!

I have AT&T U-Verse and unfortunately have to use the Arris BGW210 so I can't edit DNS settings. So I'm using my Pi Hole as a DHCP server. I have DHCP disabled in AT&T and set up on my PiHole.

Expected Behaviour:

  • Ads are blocked on Macbook Pro, iPhone etc.
  • Devices show up only on the DHCP lease list in the PiHole console, not in the AT&T device list as well.

Actual Behaviour:

  • My devices show up in both the AT&T device list, and the PiHole DHCP lease list, but with different MAC addresses and IPs.
  • Ads are still shown on all devices. Even though I'm using /u/Wally3k's lists as well as the default, the dashboard shows only 81 blocks, 0.3% of total requests. Sites like nytimes.com have tons of ads on my MBP as well as my iPhone.

The below photos show my settings in AT&T.

Debug Token:

Please see the attached for my debug log:

Debug log removed by moderator - we only want the token, not the actual log

1 Like

After you made the changes to your DHCP server settings, did you reboot the router and renew the DHCP lease on all clients?

From a client that you believe should be connected to the Pi-Hole for DNS (the MBP in this case), from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of

nslookup pi.hole

Yes, I rebooted the router and renewed the leases. I've actually done this several times now in vain.

From my MBP, here's the output of nslookup pi.hole:

owner@OWNER-MBP-2 ~ % nslookup pi.hole
Server:		192.168.1.162
Address:	192.168.1.162#53

Name:	pi.hole
Address: 192.168.1.162

Please advise. Thank you so much jfb for taking the time to help!

That client is definitely using Pi-hole for DNS. Let's look a bit further.

Your debug log shows an abnormally low number of domains on blocklist - for the number of adlists you are using this should be in the hundreds of thousands.

*** [ DIAGNOSING ]: Info table
   property              value                                   
   --------------------  ----------------------------------------
   version               13                                      
   updated               1616298484                              
   gravity_count         2735                                    
   Last gravity run finished at: Sun Mar 21 03:48:04 GMT 2021

Run the following command and post the output:

pihole -g

Yes you're absolutely right, I had the same thought after adding the additional adlists. Here are the results for pihole -g :

[i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range

  [✓] Preparing new gravity database
  [i] Using libz compression

  [i] Target: https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
  [✓] Status: No changes detected
  [i] Received 34 domains

  [i] Target: https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
  [✓] Status: No changes detected
  [i] Received 2701 domains

  [i] Target: https://raw.githubusercontent.com/PolishFiltersTeam/KADhosts/master/KADhosts.txt
  [✓] Status: Retrieval successful
  [i] Received 19276 domains

  [i] Target: https://raw.githubusercontent.com/FadeMind/hosts.extras/master/add.Spam/hosts
  [✓] Status: Retrieval successful
  [i] Received 73 domains

  [i] Target: https://v.firebog.net/hosts/static/w3kbl.txt
  [✓] Status: Retrieval successful
  [i] Received 777 domains

  [i] Target: https://adaway.org/hosts.txt
  [✓] Status: Retrieval successful
  [i] Received 8677 domains

  [i] Target: https://v.firebog.net/hosts/AdguardDNS.txt
  [✓] Status: Retrieval successful
  [i] Received 36625 domains

  [i] Target: https://v.firebog.net/hosts/Admiral.txt
  [✓] Status: Retrieval successful
  [i] Received 662 domains

  [i] Target: https://raw.githubusercontent.com/anudeepND/blacklist/master/adservers.txt
  [✓] Status: Retrieval successful
  [i] Received 42296 domains

  [i] Target: https://v.firebog.net/hosts/Easylist.txt
  [✓] Status: Retrieval successful
  [i] Received 9887 domains

  [i] Target: https://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=0&mimetype=plaintext
  [✓] Status: Retrieval successful
  [i] Received 3561 domains

  [i] Target: https://raw.githubusercontent.com/FadeMind/hosts.extras/master/UncheckyAds/hosts
  [✓] Status: Retrieval successful
  [i] Received 10 domains

  [i] Target: https://raw.githubusercontent.com/bigdargon/hostsVN/master/hosts
  [✓] Status: Retrieval successful
  [i] Received 17265 domains

  [i] Target: https://v.firebog.net/hosts/Easyprivacy.txt
  [✓] Status: Retrieval successful
  [i] Received 6843 domains

  [i] Target: https://v.firebog.net/hosts/Prigent-Ads.txt
  [✓] Status: Retrieval successful
  [i] Received 3670 domains

  [i] Target: https://raw.githubusercontent.com/FadeMind/hosts.extras/master/add.2o7Net/hosts
  [✓] Status: Retrieval successful
  [i] Received 1286 domains

  [i] Target: https://raw.githubusercontent.com/crazy-max/WindowsSpyBlocker/master/data/hosts/spy.txt
  [✓] Status: Retrieval successful
  [i] Received 376 domains

  [i] Target: https://hostfiles.frogeye.fr/firstparty-trackers-hosts.txt
  [✓] Status: Retrieval successful
  [i] Received 56977 domains

  [i] Target: https://raw.githubusercontent.com/Kees1958/W3C_annual_most_used_survey_blocklist/master/TOP_EU_US_Ads_Trackers_HOST
  [✓] Status: Retrieval successful
  [i] Received 3620 domains

  [i] Target: https://raw.githubusercontent.com/DandelionSprout/adfilt/master/Alternate%20versions%20Anti-Malware%20List/AntiMalwareHosts.txt
  [✓] Status: Retrieval successful
  [i] Received 323 domains

  [i] Target: https://osint.digitalside.it/Threat-Intel/lists/latestdomains.txt
  [✓] Status: Retrieval successful
  [i] Received 177 domains

  [i] Target: https://s3.amazonaws.com/lists.disconnect.me/simple_malvertising.txt
  [✓] Status: Retrieval successful
  [i] Received 2735 domains

  [i] Target: https://v.firebog.net/hosts/Prigent-Crypto.txt
  [✓] Status: Retrieval successful
  [i] Received 13580 domains

  [i] Target: https://bitbucket.org/ethanr/dns-blacklists/raw/8575c9f96e5b4a1308f2f12394abd86d0927a4a0/bad_lists/Mandiant_APT1_Report_Appendix_D.txt
  [✓] Status: Retrieval successful
  [i] Received 2046 domains

  [i] Target: https://phishing.army/download/phishing_army_blocklist_extended.txt
  [✓] Status: Retrieval successful
  [i] Received 25338 domains

  [i] Target: https://gitlab.com/quidsup/notrack-blocklists/raw/master/notrack-malware.txt
  [✓] Status: Retrieval successful
  [i] Received 356 domains

  [i] Target: https://v.firebog.net/hosts/Shalla-mal.txt
  [✓] Status: Retrieval successful
  [i] Received 19230 domains

  [i] Target: https://raw.githubusercontent.com/Spam404/lists/master/main-blacklist.txt
  [✓] Status: Retrieval successful
  [i] Received 8090 domains

  [i] Target: https://raw.githubusercontent.com/FadeMind/hosts.extras/master/add.Risk/hosts
  [✓] Status: Retrieval successful
  [i] Received 2556 domains

  [i] Target: https://urlhaus.abuse.ch/downloads/hostfile/
  [✓] Status: Retrieval successful
  [i] Received 1248 domains, 1 domains invalid!
      Sample of invalid domains:
      - www.bausch.kr-atlas.monaxikoslykos@zytrox.tk

  [i] Target: https://zerodot1.gitlab.io/CoinBlockerLists/hosts_browser
  [✓] Status: Retrieval successful
  [i] Received 3553 domains

  [✓] Storing downloaded domains in new gravity database
  [✓] Building tree
  [✓] Swapping databases
  [i] Number of gravity domains: 293847 (241284 unique domains)
  [i] Number of exact blacklisted domains: 10
  [i] Number of regex blacklist filters: 6
  [i] Number of exact whitelisted domains: 4
  [i] Number of regex whitelist filters: 0
  [✓] Flushing DNS cache
  [✓] Cleaning up stray matter

  [✓] DNS service is listening
     [✓] UDP (IPv4)
     [✓] TCP (IPv4)
     [✓] UDP (IPv6)
     [✓] TCP (IPv6)

  [✓] Pi-hole blocking is enabled

Do you still see ads as you did before?

Unfortunately yes. Why would the dashboard only be showing a fraction of the blocked domains on the list?

Please generate a new debug log and post the new token.

I repeated the shut down & reset procedure one more time, and lo and behold its finally working! The restart procedure for the AT&T device is pretty weird and misleading, I had to log in/enter the device pw three times and it wasn't clear when it was actually restarting, so its possible I previously thought I restarted it when I hadn't.

Regardless, thank you so so much for your time and expertise, I really appreciate you helping me!

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