Issue when configure Pi-hole like primary DNS on router

Hi All,
Please help me. When i configure Pihole like primary DNS on router. It can not ping any device.
If I dont use pihole like primary dns all works fine.

 ip addr
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 9c:eb:e8:60:ea:9c brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.9/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::9eeb:e8ff:fe60:ea9c/64 scope link
       valid_lft forever preferred_lft forever
 ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2000ms
 cat /etc/resolv.conf
**# Generated by dhcpcd from eth0**
**# /etc/resolv.conf.head can replace this line**
nameserver 127.0.0.1
**# /etc/resolv.conf.tail can replace this line**
 ip route
default via 192.168.1.1 dev eth0  metric 204
default via 192.168.1.1 dev eth0  proto static  metric 1024
169.254.0.0/16 dev eth0  scope link  metric 1000
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.9  metric 204
192.168.1.9 via 127.0.0.1 dev lo  metric 204
This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.

The intent of this script is to allow users to self-diagnose their installations.  This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected.  Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.

NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.

*** [ INITIALIZING ]
[i] 2017-12-10:17:04:00 debug log has been initiated.

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...

*** [ DIAGNOSING ]: Core version
[i] Core: v3.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v3.2-0-g5ba4135

*** [ DIAGNOSING ]: Web version
[i] Web: v3.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v3.2-0-gf74cd82

*** [ DIAGNOSING ]: FTL version
[✓] FTL: vDev-437af07 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)

*** [ DIAGNOSING ]: dnsmasq version
[i] 2.72

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.35

*** [ DIAGNOSING ]: php version
[i] 5.6.30

*** [ DIAGNOSING ]: Operating system
[✓] Debian GNU/Linux 8 (jessie)

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: Processor
/opt/pihole/piholeDebug.sh: line 474: $'[\E[32m✓\E[0m] \E[32marmv7l\E[0m': command not found

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
   192.168.1.9/24 matches the IP found in /etc/pihole/setupVars.conf

[✓] IPv6 address(es) bound to the eth0 interface:
   fe80::9eeb:e8ff:fe60:ea9c does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)

   ^ Please note that you may have more than one IP address listed.
   As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.

   The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.

[i] Default IPv4 gateway: 192.168.1.1
192.168.1.1
   * Pinging 192.168.1.1
192.168.1.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)


*** [ DIAGNOSING ]: Ports in use
[] is in use by
[22] is in use by sshd
[53] is in use by dnsmasq
[80] is in use by lighttpd
[4711] is in use by pihole-FTL
[6010] is in use by sshd

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

*** [ DIAGNOSING ]: Pi-hole processes
[✓] dnsmasq daemon is active
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=eth0
    IPV4_ADDRESS=192.168.1.9/24
    IPV6_ADDRESS=
    QUERY_LOGGING=true
    INSTALL_WEB=true
    LIGHTTPD_ENABLED=1
    DNSMASQ_LISTENING=single
    PIHOLE_DNS_1=194.50.85.5
    PIHOLE_DNS_2=194.50.85.7
    DNS_FQDN_REQUIRED=false
    DNS_BOGUS_PRIV=false
    DNSSEC=true

*** [ DIAGNOSING ]: Dashboard and block page
[✗] X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Date: Sun, 10 Dec 2017 15:07:19 GMT
Server: lighttpd/1.4.35

[✓] X-Pi-hole: The Pi-hole Web interface is working!

*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 23579643 Dec 10 15:32 /etc/pihole/gravity.list
   -----head of gravity.list------
   192.168.1.9 0.0.0.0
   192.168.1.9 000000-0.000webhostapp.com
   192.168.1.9 0-0-0-0-0-0proxy.tserv.se
   192.168.1.9 000007.ru

   -----tail of gravity.list------
   192.168.1.9 vipcasinoline.com
   192.168.1.9 vipcasinovip.net
   192.168.1.9 vipcheats.us
   192.168.1.9

*** [ DIAGNOSING ]: contents of /etc/pihole

-rw-r--r-- 1 root root 633 Dec 10 15:22 /etc/pihole/adlists.default
   https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
   https://mirror1.malwaredomains.com/files/justdomains
   http://sysctl.org/cameleon/hosts
   https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
   https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
   https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
   https://hosts-file.net/ad_servers.txt

-rw-r--r-- 1 root root 2625 Nov 27 23:14 /etc/pihole/adlists.list
   https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
   https://mirror1.malwaredomains.com/files/justdomains
   http://sysctl.org/cameleon/hosts
   https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
   https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
   https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
   https://hosts-file.net/ad_servers.txt
   https://hosts-file.net/grm.txt
   https://reddestdream.github.io/Projects/MinimalHosts/etc/MinimalHostsBlocker/minimalhosts
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/KADhosts/hosts
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/add.Spam/hosts
   https://v.firebog.net/hosts/static/w3kbl.txt
   https://adaway.org/hosts.txt
   https://v.firebog.net/hosts/AdguardDNS.txt
   https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
   https://hosts-file.net/ad_servers.txt
   https://v.firebog.net/hosts/Easylist.txt
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/SpotifyAds/hosts
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/UncheckyAds/hosts
   https://v.firebog.net/hosts/Airelle-trc.txt
   https://v.firebog.net/hosts/Easyprivacy.txt
   https://v.firebog.net/hosts/Prigent-Ads.txt
   https://raw.githubusercontent.com/quidsup/notrack/master/trackers.txt
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/add.2o7Net/hosts
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/tyzbit/hosts
   https://v.firebog.net/hosts/Airelle-hrsk.txt
   https://s3.amazonaws.com/lists.disconnect.me/simple_malvertising.txt
   https://mirror1.malwaredomains.com/files/justdomains
   https://hosts-file.net/exp.txt
   https://hosts-file.net/emd.txt
   https://hosts-file.net/psh.txt
   https://mirror.cedia.org.ec/malwaredomains/immortal_domains.txt
   https://www.malwaredomainlist.com/hostslist/hosts.txt
   https://bitbucket.org/ethanr/dns-blacklists/raw/8575c9f96e5b4a1308f2f12394abd86d0927a4a0/bad_lists/Mandiant_APT1_Report_Appendix_D.txt
   https://v.firebog.net/hosts/Prigent-Malware.txt
   https://v.firebog.net/hosts/Prigent-Phishing.txt
   https://raw.githubusercontent.com/quidsup/notrack/master/malicious-sites.txt
   https://ransomwaretracker.abuse.ch/downloads/RW_DOMBL.txt
   https://v.firebog.net/hosts/Shalla-mal.txt
   https://raw.githubusercontent.com/StevenBlack/hosts/master/data/add.Risk/hosts
   https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist

-rw-r--r-- 1 root root 38 Dec 10 15:32 /etc/pihole/local.list
   192.168.1.9 wrath
   192.168.1.9 pi.hole

-rw-r--r-- 1 root root 234 Dec 10 15:21 /etc/pihole/logrotate
   /var/log/pihole.log {
        su root root
        daily
        copytruncate
        rotate 5
        compress
        delaycompress
        notifempty
        nomail
   }
   /var/log/pihole-FTL.log {
        su root root
        weekly
        copytruncate
        rotate 3
        compress
        delaycompress
        notifempty
        nomail
   }

-rw-r--r-- 1 root root 252 Nov 27 23:16 /etc/pihole/whitelist.txt
   raw.githubusercontent.com
   mirror1.malwaredomains.com
   sysctl.org
   zeustracker.abuse.ch
   s3.amazonaws.com
   hosts-file.net
   reddestdream.github.io
   v.firebog.net
   adaway.org
   mirror.cedia.org.ec
   www.malwaredomainlist.com
   bitbucket.org
   ransomwaretracker.abuse.ch

*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d

-rw-r--r-- 1 root root 1608 Dec 10 16:30 /etc/dnsmasq.d/01-pihole.conf
   addn-hosts=/etc/pihole/gravity.list
   addn-hosts=/etc/pihole/black.list
   addn-hosts=/etc/pihole/local.list
   localise-queries
   no-resolv
   cache-size=10000
   log-queries
   log-facility=/var/log/pihole.log
   local-ttl=2
   log-async
   server=194.50.85.5
   server=194.50.85.7
   dnssec
   trust-anchor=.,19036,8,2,49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5
   interface=eth0

*** [ DIAGNOSING ]: contents of /etc/lighttpd

-rw-r--r-- 1 root root 3027 Dec 10 15:21 /etc/lighttpd/lighttpd.conf
   server.modules = (
        "mod_access",
        "mod_accesslog",
        "mod_auth",
        "mod_expire",
        "mod_compress",
        "mod_redirect",
        "mod_setenv",
        "mod_rewrite"
   )
   server.document-root        = "/var/www/html"
   server.error-handler-404    = "pihole/index.php"
   server.upload-dirs          = ( "/var/cache/lighttpd/uploads" )
   server.errorlog             = "/var/log/lighttpd/error.log"
   server.pid-file             = "/var/run/lighttpd.pid"
   server.username             = "www-data"
   server.groupname            = "www-data"
   server.port                 = 80
   accesslog.filename          = "/var/log/lighttpd/access.log"
   accesslog.format            = "%{%s}t|%V|%r|%s|%b"
   index-file.names            = ( "index.php", "index.html", "index.lighttpd.html" )
   url.access-deny             = ( "~", ".inc", ".md", ".yml", ".ini" )
   static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
   compress.cache-dir          = "/var/cache/lighttpd/compress/"
   compress.filetype           = ( "application/javascript", "text/css", "text/html", "text/plain" )
   include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
   include_shell "/usr/share/lighttpd/create-mime.assign.pl"
   include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"
' 2>/dev/null"
   $HTTP["url"] =~ "^/admin/" {

       setenv.add-response-header = (
           "X-Pi-hole" => "The Pi-hole Web interface is working!",
           "X-Frame-Options" => "DENY"
       )
       $HTTP["url"] =~ ".ttf$" {

           setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
       }
   }
   $HTTP["url"] =~ "^/admin/\.(.*)" {
        url.access-deny = ("")
   }
   include_shell "cat external.conf 2>/dev/null"

*** [ DIAGNOSING ]: contents of /etc/cron.d

-rw-r--r-- 1 root root 1418 Dec 10 15:21 /etc/cron.d/pihole
   2 4    * * 7   root    PATH="$PATH:/usr/local/bin/" pihole updateGravity
   00 00   * * *   root    PATH="$PATH:/usr/local/bin/" pihole flush once quiet
   @reboot root /usr/sbin/logrotate /etc/pihole/logrotate
   */10 *  * * *   root    PATH="$PATH:/usr/local/bin/" pihole updatechecker

*** [ DIAGNOSING ]: contents of /var/log/lighttpd

-rw-r--r-- 1 www-data www-data 3063 Dec 10 16:38 /var/log/lighttpd/error.log
   2017-11-27 21:08:30: (log.c.164) server started
   2017-11-27 21:09:01: (server.c.1558) server stopped by UID = 0 PID = 1
   2017-11-27 21:09:02: (log.c.164) server started
   2017-11-27 21:10:29: (server.c.1558) server stopped by UID = 0 PID = 1
   2017-11-27 21:10:51: (log.c.164) server started
   2017-11-27 21:11:57: (mod_fastcgi.c.2702) FastCGI-stderr: PHP Notice:  Undefined variable: timestamp in /var/www/html/admin/scripts/pi-hole/php/update_checker.php on line 79
   2017-11-27 21:18:41: (server.c.1558) server stopped by UID = 0 PID = 1
   2017-11-27 21:19:11: (log.c.164) server started
   2017-11-27 21:50:38: (server.c.1558) server stopped by UID = 0 PID = 1
   2017-11-27 21:51:10: (log.c.164) server started
   2017-12-01 00:17:19: (log.c.164) server started
   2017-12-09 23:19:58: (server.c.1558) server stopped by UID = 0 PID = 1
   2017-12-09 23:20:30: (log.c.164) server started
   2017-12-09 23:25:52: (server.c.1558) server stopped by UID = 0 PID = 1
   2017-12-09 23:26:22: (log.c.164) server started
   2017-12-09 23:30:14: (server.c.1558) server stopped by UID = 0 PID = 1
   2017-12-09 23:30:44: (log.c.164) server started
   2017-12-09 23:30:44: (log.c.164) server started
   2017-12-10 14:57:47: (server.c.1558) server stopped by UID = 0 PID = 1
   2017-12-10 14:57:49: (log.c.164) server started
   2017-12-10 15:04:35: (mod_fastcgi.c.2702) FastCGI-stderr: PHP Notice:  Undefined index: tab in /var/www/html/admin/settings.php on line 231
   2017-12-10 15:06:06: (mod_fastcgi.c.2702) FastCGI-stderr: PHP Notice:  Undefined index: tab in /var/www/html/admin/settings.php on line 231
   2017-12-10 15:30:01: (server.c.1558) server stopped by UID = 0 PID = 1
   2017-12-10 15:30:03: (log.c.164) server started
   2017-12-10 15:17:19: (log.c.164) server started

*** [ DIAGNOSING ]: contents of /var/log

-rw-r--r-- 1 pihole pihole 18026 Dec 10 16:39 /var/log/pihole-FTL.log
   [2017-12-10 15:17:27.019]
   [2017-12-10 15:17:27.019] FTL branch: (no branch)
   [2017-12-10 15:17:27.019] FTL hash: v2.12
   [2017-12-10 15:17:27.041] FTL date: 2017-12-06 21:35:44 -0600
   [2017-12-10 15:17:27.041] FTL user: pihole
   [2017-12-10 15:17:27.091] Notice: Found no readable FTL config file
   [2017-12-10 15:17:27.100]         Using default settings
   [2017-12-10 15:17:27.100] Starting config file parsing
   [2017-12-10 15:17:27.100]    SOCKET_LISTENING: only local
   [2017-12-10 15:17:27.100]    TIMEFRAME: Rolling 24h
   [2017-12-10 15:17:27.100]    QUERY_DISPLAY: Show queries
   [2017-12-10 15:17:27.100]    AAAA_QUERY_ANALYSIS: Show AAAA queries
   [2017-12-10 15:17:27.100]    MAXDBDAYS: max age for stored queries is 365 days
   [2017-12-10 15:17:27.100]    RESOLVE_IPV6: Resolve IPv6 addresses
   [2017-12-10 15:17:27.101]    RESOLVE_IPV4: Resolve IPv4 addresses
   [2017-12-10 15:17:27.101] Finished config file parsing
   [2017-12-10 15:17:27.184] Found no other running pihole-FTL process
   [2017-12-10 15:17:27.283] PID of FTL process: 508
   [2017-12-10 15:17:37.532] Gravity list entries: 694584
   [2017-12-10 15:17:37.532] No blacklist present
   [2017-12-10 15:17:37.533] No wildcard blocking list present
   [2017-12-10 15:17:37.585] Database initialized
   [2017-12-10 15:17:37.585] Starting initial log file parsing
   [2017-12-10 15:17:37.586] Reading from /var/log/pihole.log.1 (rw-r--r--)
   [2017-12-10 15:17:37.589] Notice: Increasing queries struct size from 0 to 10000 (320.10 KB)

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 dnsmasq root 398220 Dec 10 17:07 /var/log/pihole.log
   -----head of pihole.log------
   Dec 10 15:17:14 dnsmasq[312]: started, version 2.72 cachesize 10000
   Dec 10 15:17:14 dnsmasq[312]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect
   Dec 10 15:17:14 dnsmasq[312]: warning: interface eth0 does not currently exist
   Dec 10 15:17:14 dnsmasq[312]: using nameserver 194.50.85.7#53
   Dec 10 15:17:14 dnsmasq[312]: using nameserver 194.50.85.5#53
   Dec 10 15:17:14 dnsmasq[312]: read /etc/hosts - 5 addresses
   Dec 10 15:17:14 dnsmasq[312]: read /etc/pihole/local.list - 2 addresses
   Dec 10 15:17:14 dnsmasq[312]: failed to load names from /etc/pihole/black.list: No such file or directory
   Dec 10 15:17:50 dnsmasq[312]: bad name at /etc/pihole/gravity.list line 481843
   Dec 10 15:17:50 dnsmasq[312]: read /etc/pihole/gravity.list - 481843 addresses
   Dec 10 15:17:50 dnsmasq[312]: query[A] 0.ua.pool.ntp.org from 127.0.0.1
   Dec 10 15:17:50 dnsmasq[312]: forwarded 0.ua.pool.ntp.org to 194.50.85.7
   Dec 10 15:17:50 dnsmasq[312]: forwarded 0.ua.pool.ntp.org to 194.50.85.5
   Dec 10 15:17:50 dnsmasq[312]: query[AAAA] 0.ua.pool.ntp.org from 127.0.0.1
   Dec 10 15:17:50 dnsmasq[312]: forwarded 0.ua.pool.ntp.org to 194.50.85.7
   Dec 10 15:17:50 dnsmasq[312]: forwarded 0.ua.pool.ntp.org to 194.50.85.5
   Dec 10 15:17:50 dnsmasq[312]: query[A] 0.ua.pool.ntp.org from 127.0.0.1
   Dec 10 15:17:50 dnsmasq[312]: forwarded 0.ua.pool.ntp.org to 194.50.85.7
   Dec 10 15:17:50 dnsmasq[312]: forwarded 0.ua.pool.ntp.org to 194.50.85.5
   Dec 10 15:17:50 dnsmasq[312]: query[AAAA] 0.ua.pool.ntp.org from 127.0.0.1


********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **

    * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
    * For more information, see: https://pi-hole.net/2016/11/07/crack-our-medical-tricorder-win-a-raspberry-pi-3/
    * If available, we'll use openssl to upload the log, otherwise it will fall back to netcat.
ip -4 route | grep default | cut -d ' ' -f 3
192.168.1.1
192.168.1.1
 cat /etc/dhcpcd.conf
 cat /etc/dhcpcd.conf
**# A sample configuration for dhcpcd.**
**# See dhcpcd.conf(5) for details.**

**# Inform the DHCP server of our hostname for DDNS.**
hostname

**# Use the hardware address of the interface for the Client ID.**
#clientid
**# or**
**# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.**
**duid**

**# Rapid commit support.**
**# Safe to enable by default because it requires the equivalent option set**
**# on the server to actually work.**
option rapid_commit

**# A list of options to request from the DHCP server.**
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
**# Most distributions have NTP support.**
option ntp_servers
**# Respect the network MTU.**
**# Some interface drivers reset when changing the MTU so disabled by default.**
#option interface_mtu

**# A ServerID is required by RFC2131.**
require dhcp_server_identifier

**# A hook script is provided to lookup the hostname if not set by the DHCP**
**# server, but it should not be run by default.**
nodhcp
nohook lookup-hostname
interface eth0
  static ip_address=192.168.1.9/24
  static routers=192.168.1.1
  static domain_name_servers=127.0.0.1
 cat /etc/hosts
127.0.0.1       wrath
127.0.0.1       pi-hole
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters

Thanks for any help.

Your Pi-hole does not have access to the internet and cannot connect to the local network. Have you tried fixing the networking stack?

What do you mean fixing network stack? I use static dhcpcd.
I can not ping any address. only 127.0.0.1 and 192.168.1.9

 ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1005ms

ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
--- 192.168.1.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3008ms

ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.174 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.197 ms
^C
--- 127.0.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.174/0.185/0.197/0.017 ms
 ping 192.168.1.9
PING 192.168.1.9 (192.168.1.9) 56(84) bytes of data.
64 bytes from 192.168.1.9: icmp_seq=1 ttl=64 time=0.174 ms
64 bytes from 192.168.1.9: icmp_seq=2 ttl=64 time=0.182 ms
^C
--- 192.168.1.9 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.174/0.178/0.182/0.004 ms

Your static dhcpcd configuration must be broken, since you can't connect to any external device.

If I dont configure pihole as like primary DNS on my router it works fine.
I will try disable dhcpcd and use Network Manager.

Please close it. Problem with Debian Squeeze and NetworkManager.

Thanks a lot.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.