Blacklist is ignored

[xep22]

I am using some adlists to block ads. In "Blacklist" I added manually some websites, but I still can visit them... the problem is since many weeks. whats the point ? add-block works.

[yubiuser]

Please upload a debug log and post just the token that is generated after the log is uploaded by running the following command from the Pi-hole host terminal. Please share only the Token code, not the complete URL

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

[Blockhead]

Check ipconfig /all from a command prompt to confirm your pi-hole address is your only DNS server.

[xep22]

I added the dns server in my router

upload not possible:

[?] Would you like to upload the log? [y/N] y
* Using curl for transmission.
* curl failed, contact Pi-hole support for assistance.
* Error message: curl: (7) Failed to connect to tricorder.pi-hole.net port 443: Keine Route zum Zielrechner

[✗] There was an error uploading your debug log.

• Please try again or contact the Pi-hole team for assistance.
• A local copy of the debug log can be found at: /var/log/pihole_debug.log

[yubiuser]

Can you DM me the log?

[xep22]

how ? cant see dm button in your profile.

[yubiuser]

[xep22]

"Sorry, you cannot send a personal message to that user."

[jfb]

Try uploading the debug log again and post the token URL here. The problem at the other end is fixed.

[xep22]

nope.

[?] Would you like to upload the log? [y/N] y
    * Using curl for transmission.
    * curl failed, contact Pi-hole support for assistance.
    * Error message: curl: (7) Failed to connect to tricorder.pi-hole.net port 443: Keine Route zum Zielrechner

[✗]  There was an error uploading your debug log.
   * Please try again or contact the Pi-hole team for assistance.
   * A local copy of the debug log can be found at: /var/log/pihole_debug.log

pi@pihole:~$ tail /var/log/pihole_debug.log
Mar 5 10:22:53 dnsmasq[587]: query[A] edgedl.me.gvt1.com from 192.168.5.1
Mar 5 10:22:53 dnsmasq[587]: forwarded edgedl.me.gvt1.com to 2620:119:53::53
Mar 5 10:22:53 dnsmasq[587]: query[AAAA] edgedl.me.gvt1.com from 192.168.5.1
Mar 5 10:22:53 dnsmasq[587]: forwarded edgedl.me.gvt1.com to 2620:119:53::53
Mar 5 10:22:53 dnsmasq[587]: reply edgedl.me.gvt1.com is 2600:1900:4110:86f::
Mar 5 10:22:53 dnsmasq[587]: reply edgedl.me.gvt1.com is 34.104.35.123
Mar 5 10:22:54 dnsmasq[587]: query[A] bob-dispatch-prod-eu.amazon.com from 192.168.5.1
Mar 5 10:22:54 dnsmasq[587]: forwarded bob-dispatch-prod-eu.amazon.com to 2620:119:53::53
Mar 5 10:22:54 dnsmasq[587]: reply bob-dispatch-prod-eu.amazon.com is 52.95.119.186

[butchkemper]

After the client queries the DNS for the IP address, the client will not query the DNS again until the TTL for the original answer expires.

So, if you access a website and then add an entry to the black list, you can still access that website until the original query TTL expires. When the TTL expires, the DNS for the site will be queried and because it is on the black list, the query will be returned as not found.