NOT really a pihole problem, but an explanation would be useful...
On my system, in belgium, a DNS query to dns.nextdns.io (a DOH server) returns the result:
nslookup dns.nextdns.io
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
dns.nextdns.io canonical name = steering.nextdns.io.
Name: steering.nextdns.io
Address: 194.110.115.97
Name: steering.nextdns.io
Address: 45.128.133.120
a quick check of the unbound log (used as recursive resolver) shows unbound uses ns1.nextdns.io an ns2.nextdns.io
on my system:
ns1.nextdns.io -> 45.90.28.1
ns2.nextdns.io -> 45.90.30.1
a more specific nslookup (nslookup dns.nextdns.io 45.90.28.1), thus using ns1.nextdns.io returns the identical result.
nslookup dns.nextdns.io 45.90.28.1
Server: 45.90.28.1
Address: 45.90.28.1#53
Non-authoritative answer:
dns.nextdns.io canonical name = steering.nextdns.io.
Name: steering.nextdns.io
Address: 45.128.133.120
Name: steering.nextdns.io
Address: 194.110.115.97
HOWEVER
the user (located in Switzerland) who reported this problem (using my DOH blocklist) gets different results for the more specific queries (same result on both nameservers, but different from my result):
nslookup dns.nextdns.io 45.90.28.1
Server: 45.90.28.1
Address: 45.90.28.1#53
Non-authoritative answer:
dns.nextdns.io canonical name = steering.nextdns.io.
Name: steering.nextdns.io
Address: 178.255.153.47
Name: steering.nextdns.io
Address: 159.100.248.193
What am I (are we) missing, that would explain this difference?
Thank you for your time and effort.