Changing dns manually on pc kills internet

[r8_w9]

Please follow the below template, it will help us to help you!

Expected Behaviour:

I want my pi-hole block ads.

Actual Behaviour:

I've installed pi-hole into my raspberry pi zero wh and in admin pannel it looks ok. Status is Active, pi-hole is up to date and also it gets queries but ads still persists.

My home network looks very simple. I got main router netis connected to internet and second router tp-link that's just serves as wifi signal extender.

I reserved ip adresses for my second router and raspberry to avoid ip conflicts on my main router netis. I also tried to set dns server to raspberry's ip adress but I can change only for WAN, not LAN

When I wasn't able to change dns server for lan in my main router I tried to change it manually on windows 10 computer and the result was that I lost my internet connection. After setting back to automatic dns server internet went back to normal.

Could you please help me guys?

Debug Token:

https://gist.githubusercontent.com/r8w9a5k/72f96081a830916de106d181f3ee0533/raw/32b85e8658fb2b90cc0a7de581afb562f0bc3fab/debuglog

[DanSchaper]

What does nslookup pi.hole 192.168.0.10 show?

[DanSchaper]

It doesn't look like Pi-hole is able to reach the internet:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] aaxdetect.com is 0.0.0.0 via localhost (127.0.0.1)
[✓] aaxdetect.com is 0.0.0.0 via Pi-hole (192.168.0.10)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

Queries are being forwarded to 8.8.8.8 and never getting a response:

-rw-r--r-- 1 pihole pihole 3248514 Apr 29 10:13 /var/log/pihole.log
   -----head of pihole.log------
   Apr 29 00:00:05 dnsmasq[493]: query[PTR] 4.0.168.192.in-addr.arpa from 127.0.0.1
   Apr 29 00:00:05 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.4.4
   Apr 29 00:00:05 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.8.8
   Apr 29 00:00:08 dnsmasq[493]: query[PTR] 4.0.168.192.in-addr.arpa from 127.0.0.1
   Apr 29 00:00:08 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.4.4
   Apr 29 00:00:08 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.8.8
   Apr 29 00:00:14 dnsmasq[493]: query[PTR] 4.0.168.192.in-addr.arpa from 127.0.0.1
   Apr 29 00:00:14 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.4.4
   Apr 29 00:00:14 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.8.8
   Apr 29 00:00:19 dnsmasq[493]: query[PTR] 4.0.168.192.in-addr.arpa from 127.0.0.1
   Apr 29 00:00:19 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.4.4
   Apr 29 00:00:19 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.8.8
   Apr 29 00:00:22 dnsmasq[493]: query[PTR] 4.0.168.192.in-addr.arpa from 127.0.0.1
   Apr 29 00:00:22 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.4.4
   Apr 29 00:00:22 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.8.8
   Apr 29 00:00:28 dnsmasq[493]: query[PTR] 4.0.168.192.in-addr.arpa from 192.168.0.10
   Apr 29 00:00:28 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.4.4
   Apr 29 00:00:28 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.8.8
   Apr 29 00:00:42 dnsmasq[493]: query[PTR] 4.0.168.192.in-addr.arpa from 192.168.0.10
   Apr 29 00:00:42 dnsmasq[493]: forwarded 4.0.168.192.in-addr.arpa to 8.8.4.4

You have malformed regex entries. DNS hostnames do not contain https:

   15       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?clicks\.beap\.bc\.yahoo\.com/                                            2021-04-27 18:51:53  2021-04-27 18:51:53                                                    
   16       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?secure\.footprint\.net/                                                  2021-04-27 18:51:59  2021-04-27 18:51:59                                                    
   17       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?match\.com/                                                              2021-04-27 18:52:05  2021-04-27 18:52:05                                                    
   18       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?clicks\.beap\.bc\.yahoo(\.\w{2}\.\w{2}|\.\w{2,4})/                       2021-04-27 18:52:16  2021-04-27 18:52:16                                                    
   19       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?sitescout(\.\w{2}\.\w{2}|\.\w{2,4})/                                     2021-04-27 18:52:28  2021-04-27 18:52:28                                                    
   20       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?appnexus(\.\w{2}\.\w{2}|\.\w{2,4})/                                      2021-04-27 18:52:41  2021-04-27 18:52:41                                                    
   21       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?evidon(\.\w{2}\.\w{2}|\.\w{2,4})/                                        2021-04-27 18:52:47  2021-04-27 18:52:47                                                    
   22       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?mediamath(\.\w{2}\.\w{2}|\.\w{2,4})/                                     2021-04-27 18:53:22  2021-04-27 18:53:22                                                    
   23       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?scorecardresearch(\.\w{2}\.\w{2}|\.\w{2,4})/                             2021-04-27 18:53:27  2021-04-27 18:53:27                                                    
   24       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?doubleclick(\.\w{2}\.\w{2}|\.\w{2,4})/                                   2021-04-27 18:53:42  2021-04-27 18:53:42                                                    
   25       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?flashtalking(\.\w{2}\.\w{2}|\.\w{2,4})/                                  2021-04-27 18:53:55  2021-04-27 18:53:55                                                    
   26       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?turn(\.\w{2}\.\w{2}|\.\w{2,4})/                                          2021-04-27 18:54:01  2021-04-27 18:54:01                                                    
   27       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?mathtag(\.\w{2}\.\w{2}|\.\w{2,4})/                                       2021-04-27 18:54:27  2021-04-27 18:54:27                                                    
   28       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?googlesyndication(\.\w{2}\.\w{2}|\.\w{2,4})/                             2021-04-27 18:57:00  2021-04-27 18:57:00                                                    
   29       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?s\.yimg\.com/cv/ae/us/audience/                                          2021-04-27 18:57:09  2021-04-27 18:57:09                                                    
   30       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?clicks\.beap/                                                            2021-04-27 18:57:14  2021-04-27 18:57:14                                                    
   31       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?.doubleclick(\.\w{2}\.\w{2}|\.\w{2,4})/                                  2021-04-27 18:59:23  2021-04-27 18:59:23                                                    
   32       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?yieldmanager(\.\w{2}\.\w{2}|\.\w{2,4})/                                  2021-04-27 18:59:41  2021-04-27 18:59:41                                                    
   33       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?w55c(\.\w{2}\.\w{2}|\.\w{2,4})/                                          2021-04-27 19:00:55  2021-04-27 19:00:55                                                    
   34       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?adnxs(\.\w{2}\.\w{2}|\.\w{2,4})/                                         2021-04-27 19:01:03  2021-04-27 19:01:03                                                    
   35       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?advertising\.com/                                                        2021-04-27 19:01:08  2021-04-27 19:01:08                                                    
   36       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?evidon\.com/                                                             2021-04-27 19:02:27  2021-04-27 19:02:27                                                    
   37       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?scorecardresearch\.com/                                                  2021-04-27 19:02:33  2021-04-27 19:02:33                                                    
   38       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?flashtalking\.com/                                                       2021-04-27 19:02:39  2021-04-27 19:02:39                                                    
   39       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?turn\.com/                                                               2021-04-27 19:02:47  2021-04-27 19:02:47                                                    
   40       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?mathtag\.com/                                                            2021-04-27 19:02:52  2021-04-27 19:02:52                                                    
   41       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?surveylink/                                                              2021-04-27 19:02:58  2021-04-27 19:02:58                                                    
   42       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?info\.yahoo\.com/                                                        2021-04-27 19:03:07  2021-04-27 19:03:07                                                    
   43       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?ads\.yahoo\.com/                                                         2021-04-27 19:03:14  2021-04-27 19:03:14                                                    
   44       3        1  0             ^https?://([A-Za-z0-9.-]*\.)?global\.ard\.yahoo\.com/                                                 2021-04-27 19:03:21  2021-04-27 19:03:21                                                    

[DanSchaper]

Your router is advertising multiple DNS servers and that will lead to clients picking 8.8.8.8 and 192.168.0.1.

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   * Received 282 bytes from wlan0:192.168.0.1
     Offered IP address: 192.168.0.10
     Server IP address: N/A
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.0.1
      lease-time: Infinite
      netmask: 255.255.255.0
      router: 192.168.0.1
      dns-server: 192.168.0.10
      dns-server: 8.8.8.8
      dns-server: 192.168.0.1
      --- end of options ---
    

Why should Pi-hole be my only DNS server?

Reduced Ad Blocking Capability The main reason you should Pi-hole as your only DNS server is that you will see increased performance in the blocking of ads. If you have two DNS servers (Pi-hole and something else), your network clients may not always query Pi-hole for name resolution. If a query happens to be answered from a non-Pi-hole DNS server, your block lists will not apply (since that DNS server doesn't know about them). All Queries Need To Go Through Pi-hole First Since other DNS se…

[r8_w9]

Hi,
you are correct about that. How can I change dns to only have 192.168.0.10? On my both routers I have dns set to 192.168.0.10 both primary and secondary servers.

Ipconfig /all now shows these dns servers:
192.168.0.10
192.168.0.10
8.8.8.8
192.168.0.1

I don't understand why I have 4 dns servers Maybe it's there because I changed it manually on my windows 10 pc. I set only primary dns server to 192.168.0.10 and I left secondary option blank. After inspecting I spotted that windows gave me secondary dns server automatically to 192.168.0.1. Even though I now get automatic dns because I want internet I still have 4 dns servers.

[r8_w9]

Server: raspberrypi
Address: 192.168.0.10

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Name: pi.hole
Address: 192.168.0.10

[r8_w9]

It should be connected. I see my raspberry on router's ARP list with correct mac and ip adress.

Thank you for pin pointing https over regex. I will fix that.

[r8_w9]

Hello @DanSchaper , do you need more info?

[Bucking_Horn]

Are you still running into the same troubles as initially stated?
What has changed since your last message?
Did you fix your regex and multiple local DNS server issues?

[r8_w9]

Hello @Bucking_Horn , thank you for your reply. Right now I'm not at home but as soon as I arrive I will post updated state. I didn't change anything but my regex list.

[r8_w9]

Hello again, I just checked ipconfig /all and I still see those dns servers:
192.168.0.10
192.168.0.10
8.8.8.8
192.168.0.1

On both my routers I have only 2 dns servers - primary and secondary both 192.168.0.10 but why I still see 8.8.8.8 and 192.168.0.1 ?

[deHakkelaar]

Thats your router misbehaving.
You can check what DNS servers your router is dishing out with below one:

pi@ph5b:~ $ pihole-FTL dhcp-discover
Scanning all your interfaces for DHCP servers
[..]
   dns-server: 10.0.0.2
   dns-server: 10.0.0.4

Some routers can be flashed with custom firmware so via additional settings, it doesnt advertise itself or other DNS servers to the clients.
But this is not without risks as you could brick your router if goes wrong!!!
Safer to do below:

How do I use Pi-hole's built in DHCP server (and why would I want to)?

Using Your Existing Router For Network-wide Ad Blocking You might not need to use Pi-hole's DHCP server: In many home environments, your router also functions as your DHCP server. In this case, you can often set Pi-hole to be the DNS server for your network clients in the router's DHCP (or LAN) settings page, which allows all of your network clients to block ads simply by connecting to the network. Setting it up this way is also what makes Pi-hole very powerful for network-wide ad blocking. …

[r8_w9]

Hello @deHakkelaar , I did pihole-FTL dhcp-disover and I see those dns servers:

• Received 286 bytes from wlan0:192.168.0.1
  Offered IP address: 192.168.0.10
  Server IP address: N/A
  Relay-agent IP address: N/A
  BOOTP server: (empty)
  BOOTP file: (empty)
  DHCP options:
  Message type: DHCPOFFER (2)
  server-identifier: 192.168.0.1
  lease-time: Infinite
  netmask: 255.255.255.0
  router: 192.168.0.1
  dns-server: 192.168.0.10
  dns-server: 192.168.0.10
  dns-server: 8.8.8.8
  dns-server: 192.168.0.1
  --- end of options ---

Then I followed your advice to turn on DHCP server in pi-hole and disabling DHCP server on router. I was successful. After running ipconfig /all I finally saw correct dns servers both 192.168.0.10 which belongs to raspberry pi ! Nice but I completely lost internet connection

Any suggestions?

[deHakkelaar]

@r8_w9

Then I followed your advice to turn on DHCP server in pi-hole and disabling DHCP server on router. I was successful. After running ipconfig /all I finally saw correct dns servers both 192.168.0.10 which belongs to raspberry pi !

That solves one of the two problems:

@r8_w9

Nice but I completely lost internet connection

Any suggestions?

The other issue is that your Pi-hole instance cant communicate whith DNS servers residing on the Internet (or at least the 8.8.8.8 one):

@DanSchaper

It doesn't look like Pi-hole is able to reach the internet:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] aaxdetect.com is 0.0.0.0 via localhost (127.0.0.1)
[✓] aaxdetect.com is 0.0.0.0 via Pi-hole (192.168.0.10)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

Queries are being forwarded to 8.8.8.8 and never getting a response:

Below is the one you need to get working/fix (need to get an ANSWER SECTION with an IP):

pi@ph5b:~ $ dig @8.8.8.8 doubleclick.com

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Raspbian <<>> @8.8.8.8 doubleclick.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41584
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;doubleclick.com.               IN      A

;; ANSWER SECTION:
doubleclick.com.        299     IN      A       142.250.179.206

;; Query time: 16 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri May 14 03:51:06 CEST 2021
;; MSG SIZE  rcvd: 60

Check if a local firewall is blocking (below is permissive allowing all):

pi@ph5b:~ $ sudo iptables -nL
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Check if you have a route to Google's public DNS service at 8.8.8.8:

pi@ph5b:~ $ traceroute -n 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  10.0.0.1  1.177 ms  0.896 ms  0.644 ms
 2  192.168.1.1  1.160 ms  0.808 ms  0.955 ms
 3  62.58.240.1  8.833 ms  8.242 ms  7.787 ms
 4  212.53.25.201  10.155 ms  10.173 ms  10.685 ms
 5  * * *
 6  * * *
 7  8.8.8.8  7.928 ms  7.719 ms  7.291 ms

Check your router for any kind of security settings that might hinder/block DNS queries (53 TCP+UDP) against Google's 8.8.8.8 (and possibly other public DNS servers).
You could try for example to resolve via Cloudflare's public DNS service at 1.1.1.1 to diagnose:

pi@ph5b:~ $ dig @1.1.1.1 doubleclick.com

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Raspbian <<>> @1.1.1.1 doubleclick.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43562
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;doubleclick.com.               IN      A

;; ANSWER SECTION:
doubleclick.com.        300     IN      A       172.217.169.46

;; Query time: 23 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri May 14 03:57:32 CEST 2021
;; MSG SIZE  rcvd: 60

[r8_w9]

Below is the one you need to get working/fix (need to get an ANSWER SECTION with an IP):

I've tried dig @8.8.8.8 doubleclick.com and here's the result:

; <<>> DiG 9.11.5-P4-5.1+deb10u3-Raspbian <<>> @8.8.8.8 doubleclick.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

Check if a local firewall is blocking (below is permissive allowing all):
I did sudo iptables -nL and here's the result:

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
 
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
 
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Check if you have a route to Google's public DNS service at 8.8.8.8 :

I did traceroute -n 8.8.8.8 and here's the result:

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Check your router for any kind of security settings that might hinder/block DNS queries (53 TCP+UDP) against Google's 8.8.8.8 (and possibly other public DNS servers).
You could try for example to resolve via Cloudflare's public DNS service at 1.1.1.1 to diagnose:

I did dig @1.1.1.1 doubleclick.com and here's the result:

; <<>> DiG 9.11.5-P4-5.1+deb10u3-Raspbian <<>> @1.1.1.1 doubleclick.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

It looks like it doesn't have internet connection but after running iwgetid I see correct wlan0 ESSID.

[Bucking_Horn]

Your results indicate something is preventing your client from talking to public DNS servers.
As your local on-device firewall seems to be clear, it's highly likely that your router is responsible.

If you haven't already done so in the meantime, you should follow deHakkelaar's advice:

@deHakkelaar

Check your router for any kind of security settings that might hinder/block DNS queries (53 TCP+UDP) against Google's 8.8.8.8 (and possibly other public DNS servers).

[deHakkelaar]

Also, below shows your Pi-hole host doesnt have a route to 8.8.8.8 and most likely also no route to other public IP addresses:

@r8_w9

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
[..]
23  * * *

This might indicate a wrong IP configuration on the Pi-hole host.
Below file (should) contain the static IP configuration for the network interface(s):

pi@ph5b:~ $ tail /etc/dhcpcd.conf
[..]
interface eth0
  static ip_address=10.0.0.4/24
  static routers=10.0.0.1
  static domain_name_servers=10.0.0.1

Make sure the static routers field reflects the IP of your router and resides in the same subnet as the static ip_address field.
You can change these settings by editing that file with below:

sudo nano /etc/dhcpcd.conf

And run below after save/exit to apply:

sudo service dhcpcd restart

Validate by running below two (the default via IP should be the router IP):

pi@ph5b:~ $ ip route show default
default via 10.0.0.1 dev eth0 src 10.0.0.4 metric 202

pi@ph5b:~ $ ip route get 8.8.8.8
8.8.8.8 via 10.0.0.1 dev eth0 src 10.0.0.4 uid 1000

And if you changed anything, test again with the traceroute -n 8.8.8.8 command.
And check if the dig commands are successful after changing anything.

[r8_w9]

I' changed /etc/dhcpd.conf and after running tail command I see this configuration which seems correct:

interface wlan0
static ip_address=192.168.0.10/24
static routers=192.168.0.1
static domain_name_servers=192.168.0.1

I didn't set eth0 as you mentioned because I have pi WH connected wirelessly so I'm playing around with wlan0.

It seems ok in my eyes. 192.168.0.10 is my pi ip address and it's reserved in my router. 192.168.0.1 is my router's ip and 192.168.0.1 is also my default gateway.

I tried command route -ne and cat /etc/resolv.conf and I see this configuration and I don't think it's correct.

Even though I changed dhcpcd.conf the results are same. I still see 4 DNS servers and traceroute with dig commands are still the same

[deHakkelaar]

@r8_w9

I' changed /etc/dhcpd.conf

What did you change?

@r8_w9

I didn't set eth0 as you mentioned because I have pi WH connected wirelessly so I'm playing around with wlan0 .

Thats correct.
You dont have any other network interfaces besides wlan0 connected right?

@r8_w9

I tried command route -ne and cat /etc/resolv.conf and I see this configuration and I don't think it's correct.

These are correct.
It shows the default route to the Internet 0.0.0.0 is via your router IP 192.168.0.1.
But I prefer you use below to check:

ip route show default

ip route get 8.8.8.8

And also, please copy/paste the text output to here instead of those screenshots?
I also like to copy/paste instead of typing over your screenshot data

@r8_w9

Even though I changed dhcpcd.conf the results are same. I still see 4 DNS servers and traceroute with dig commands are still the same

What client operating systems do you have connected to this same WiFi AP segment?
And can these clients browse the Internet?
What IP details does one of these clients show (IP address, subnet mask, gateway)?

Currently, you have to focus on getting the traceroute working properly as that one will show if your route to 8.8.8.8 is working or not!

EDIT: Ow ps. can you ping the router from the Pi-hole host?

ping 192.168.0.1

traceroute does something similar both using the ICMP protocol.

EDIT2: Could you post output for one more:

ip -4 neighbor show | awk '{print $1}'

[r8_w9]

What did you change?

I wrote this configuration into /etc/dhcp.conf

interface wlan0
static ip_address=192.168.0.10/24
static routers=192.168.0.1
static domain_name_servers=192.168.0.1

Thats correct.
You dont have any other network interfaces besides wlan0 connected right?

My home network is quite simple. I have 1 main router connected to internet 192.168.0.1 and second router 192.168.0.2 as wifi signal extender (bridge) with dhcp turned off. Raspberry PI Zero is connected thru wifi and I have only one wired connection from main router to TV only. So I guess it's correct.

But I prefer you use below to check:

ip route show default

ip route get 8.8.8.8

After ip route show default I see this:

default via 192.168.0.1 dev wlan0 src 192.168.0.10 metric 302

After ip route get 8.8.8.8 I see this:

8.8.8.8 via 192.168.0.1 dev wlan0 src 192.168.0.10 uid 1000
    cache

And also, please copy/paste the text output to here instead of those screenshots?
I also like to copy/paste instead of typing over your screenshot data

No more screenshots, sorry for that!

What client operating systems do you have connected to this same WiFi AP segment?
And can these clients browse the Internet?
What IP details does one of these clients show (IP address, subnet mask, gateway)?

I'm connected with 2 android phones, 2 iphones, 2 iPads, 3 windows laptops and 1 I hope 1 raspberry pi zero wh with this no gui os Raspberry Pi OS – Raspberry Pi

EDIT: Ow ps. can you ping the router from the Pi-hole host?

ping 192.168.0.1

Ping doesn't seem to be ok

PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
^C
--- 192.168.0.1 ping statistics ---
102 packets transmitted, 0 received, 100% packet loss, time 184ms

EDIT2: Could you post output for one more:

ip -4 neighbor show | awk '{print $1}'

Yes, here's the result

192.168.0.20
192.168.0.18
192.168.0.11
192.168.0.13
192.168.0.1
192.168.0.5
192.168.0.3
192.168.0.7
192.168.0.4

Hmm I don't see 192.168.0.10 which should belong to raspberry pi.