After Pihole configuration all connections and services on Raspberry itself became filtered.
I want to use Raspberry as Pihole DNS server for my navigation (on others devices) but I don't want that all connections on Raspberry itself and related hosted services are filtered by Pihole.
The IP I have configured as static in the pihole setup is 192.168.1.2 after the pihole installation seems It has been assigned to eth0 interface in dhcpcd.conf (I have selected wlan also during pihole setup, since I don't use any ethernet at all, not sure this is normal)
as you previously suggested now makes the output of cat /etc/resolv.conf
showing the Cloudflare DNS rather than router defaults
but all connections on Raspberry continue to remain filtered
The Pi is using Cloudflare for DNS. The last command for nslookup shows that Cloudflare responded, and the query was not blocked (if the nameserver were Pi-hole the query would be blocked).
To change this, run pihole -r and select the reconfigure option
however I have noticed another DNS config file in addition to dhcpcd.conf and resolv.conf this file is named resolvconf.conf
setting dhcpcd.conf as above but with static ip chosen in setup script manually set on wlan0 interface rather than eth0 (not sure why setup script hasn't done this considering my choice on the desired interface step selection) and commenting out resolvconf.conf nameserver line seems has addressed the problems.
The setup script should be refined to address these issues (and it should also ask for the lighttpd port rather than setup the webserver automatically on port 80 causing conflicts with existing configuration)