My Pihole can't resolv anymore and blocking is offline

[anon62498003]

When I set in SetupVars.con IPV4_ADDRESS=192.168.178.21/24

pihole -d says:

Failed to resolve www.pbsi.stkippersada.ac.id via Pi-hole (192.168.178.21)
IPv4 address(es) bound to the enp4s0 interface:
192.168.178.21/24 does not match the IP found

When I set in SetupVars.conf IPV4_ADDRESS=0.0.0.0

all "green":
Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] mg-multimedia-services.com is via localhost (127.0.0.1)
[✓] mg-multimedia-services.com is via Pi-hole (0.0.0.0)
[✓] doubleclick.com is 172.217.19.78 via a remote, public DNS server (8.8.8.8)

and:
IPv4 address(es) bound to the enp4s0 interface:
192.168.178.21/24 does not match the IP found

In Pihole Dashboard:
Network Information
Pi-hole Ethernet Interface: unknown
Pi-hole IPv4 address: unknown
Pi-hole IPv6 address: unknown
Pi-hole hostname: flashgordon

I don't know why pihole is nothing to block.

[technicalpyro]

@anon62498003

enp4s0

What is the result of ip a ?

[PromoFaux]

@anon62498003 would you mind sharing a debug token so that we may take a closer look?

[anon62498003]

ip a:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether c6:2e:d0:75:80:88 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.21/24 brd 192.168.178.255 scope global noprefixroute enp4s0
valid_lft forever preferred_lft forever
inet 169.254.140.105/16 brd 169.254.255.255 scope global enp4s0
valid_lft forever preferred_lft forever

debug token is: 4nz4bp6dc2

hmm...
nslookup pi.hole
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find pi.hole: NXDOMAIN

[anon62498003]

Netstat_Results:

Active Network Services

[PromoFaux]

@anon62498003, correct me if I'm wrong here, but it appears like you're trying to accomplish a couple of things here:

• null routing via 0.0.0.0
• Locally hosted dnscrypt servers as your upstream. (Presumably listening on a port other than 53?)

Might I be so bold as to suggest trying out the FTLDNS beta? You will be able to acheieve these things without the "hacky" workarounds that you are currently using!

echo "FTLDNS" | sudo tee /etc/pihole/ftlbranch
pihole checkout core FTLDNS
pihole checkout web FTLDNS

Once you're on that branch, you will be able to set BLOCKINGMODE=NULL in /etc/pihole/pihole-FTL.conf, which solves the first issue. You can also set ports on upstream servers. E.g, I have unbound running on my machine, listening on port 5353, which I simply tell Pi-hole about like this: