Devices not using pihole

[deHakkelaar]

Apparently no rogue directives.

So from below, lookup on the local host to the private address resolve:

@gino8807

sully@fedora:~$ nslookup -class=chaos -type=txt version.bind 192.168.50.77
Server: 192.168.50.77
Address: 192.168.50.77#53
version.bind text = "dnsmasq-pi-hole-vs.90+1"

And not from a Windows client addressing that private IP:

@gino8807

C:\Users\gino8>nslookup -class=chaos -type=txt version.bind 192.168.50.77
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  192.168.50.77

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out

But a lookup from that Windows PC addressing a public IP does resolve:

@gino8807

PS C:\WINDOWS\system32> nslookup flurry.com 116.203.32.217
Server:  dismail.de
Address:  116.203.32.217

Name:    flurry.com
Address:  0.0.0.0

Could this be DNS rebind protection?

Why won't Pi-hole work with DNS rebind protection enabled?

What is DNS rebind protection? If your router has an option called DNS rebind protection enabled, you may run into issues when trying to use Pi-hole as your DNS server. The reasons for this are quite technical, but to summarize what this option does in one sentence: DNS rebind protection does not allow DNS queries to be answered with a local IP address. Why does this interfere with Pi-hole? DNS rebind is meant to be a countermeasure to an attack on your network. So in many cases, it's actu…

Below a screenshot for Asus "DNS rebind protection":

https://www.asus.com/support/faq/1039292/