DNS leak test shows Google IP addresses when using unbound

I dont think its a smart move removing the openresolv package?
Most network managers address openresolv to populate /etc/resolv.conf.
Better comment out below line:

pi@ph5b:~ $ cat /etc/resolvconf.conf
[..]
#unbound_conf=/etc/unbound/unbound.conf.d/resolvconf_resolvers.conf

Above will prevent that resolvconf_resolvers.conf file being created in the first place.
And make sure that file doesnt exist (delete it and restart unbound):

pi@ph5b:~ $ sudo stat /etc/unbound/unbound.conf.d/resolvconf_resolvers.conf
stat: cannot statx '/etc/unbound/unbound.conf.d/resolvconf_resolvers.conf': No such file or directory

Or remove the openresolv package and replace it with resolvconf instead which wont create above config file:

pi@ph5b:~ $ apt depends dhcpcd5
[..]
 |Recommends: openresolv
  Recommends: resolvconf

With that config file included:

pi@ph5b:~ $ sudo unbound-control list_forwards
. IN forward 10.0.0.1
home.dehakkelaar.nl. IN forward 10.0.0.1
pi@ph5b:~ $ sudo unbound-control lookup pi-hole.net
The following name servers are used for lookup of pi-hole.net.
forwarding request:
Delegation with 0 names, of which 0 can be examined to query further addresses.
It provides 1 IP addresses.
10.0.0.1                not in infra cache.

Without:

pi@ph5b:~ $ sudo unbound-control list_forwards
pi@ph5b:~ $
pi@ph5b:~ $ sudo unbound-control lookup pi-hole.net
The following name servers are used for lookup of pi-hole.net.
;rrset 2853 4 1 11 5
pi-hole.net.    2853    IN      NS      ns1.pi-hole.net.
pi-hole.net.    2853    IN      NS      ns3.pi-hole.net.
pi-hole.net.    2853    IN      NS      ns2.pi-hole.net.
pi-hole.net.    2853    IN      NS      ns4.pi-hole.net.
[..]

EDIT: Aha, noticed this being discussed below: