Disabling regex blocklist results in continued blocking

Help
1

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

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

domain should not be blocked

Actual Behaviour:

domain is blocked.

Debug Token:

https://tricorder.pi-hole.net/DOaJIPbW/

2

Run from a client, what's the output for an affected domain that you expect not to be blocked:

nslookup affected.domain

where you substitute affected.domain with the respective actual domain.
Please share the full output, preferably as text.

5 
ipconfig /flushdns
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.

nslookup tplinkra.com
Server: dcs-vm-dc3.digserv.ext
Address: 192.168.200.55

Name: tplinkra.com
Addresses: ::
0.0.0.0

image001.png1455×839 123 KB

6

It sounds like you have that domain blocked either via another blacklist entry or via an adlist. When you look at the blocked domain in the Query Log, which of these does it say? This will reveal where the blocking is coming from.

  • Blocked (gravity)
  • Blocked (regex blacklist)
  • Blocked (exact blacklist)

If you wish to explicitly not block that domain, click the drop-down next to it, change it to Regex whitelist and click the slider to re-enable it.

7

Do you have more than one pi-hole?

The debug log you posted doesn't show the Regex Blacklist.

Also, the nslookup command is returning

Server: dcs-vm-dc3.digserv.ext
Address: 192.168.200.55

But your debug log shows your pi-hole is using a different IP:

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
    192.168.200.34/24
1 Like
8

Hi, I have regenerated a debug log here: https://tricorder.pi-hole.net/vBwFmt6a/

I was messing around and had deleted the entries. Sorry.

Configuration:

My computer 192.168.200.32

Domain controller running DNS 192.158.200.55

Domain controller DNS forwards to Pi-hole 192.168.200.34 and 192.168.200.35 (both are pi-holes).

I cleared the DNS server cache on the domain controller and the local cache on my computer.

I have also tried setting the Pi-hole as the DNS server.

k:>nslookup tplinkra.com

Server: pi.hole

Address: 192.168.200.34

*** No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for tplinkra.com

k:>

9

That is now actually correct. You are using your Pi-hole and the domain is not blocked or else it would have returned 0.0.0.0. That domain does not have any public A or AAAA records present and so it cannot be resolved to an IP. Earlier on you had a blocked result via your DC.

nslookup tplinkra.com
Server: dcs-vm-dc3.digserv.ext
Address: 192.168.200.55
Name: tplinkra.com
Addresses: ::
0.0.0.0

10

Ok thanks for all your help.

11

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