I'm having trouble with my DNS and I don't know where to start troubleshooting

#1

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

Expected Behaviour:

All local devices using pihole as DNS on router level

Actual Behaviour:

The internet on my laptop works but not on my phone. When I run cat /etc/resolv.conf it says nameserver sis 127.0.0.1, is that normal?

Debug Token:

I get this when I try to upload the log:

[?] Would you like to upload the log? [y/N] y
* Using openssl for transmission.
[✗] There was an error uploading your debug log.

  • Please try again or contact the Pi-hole team for assistance.
  • A local copy of the debug log can be found at: /var/log/pihole_debug-sanitized.log
0 Likes

#2

Is your gateway set properly? The Pi-hole needs to know how to get out to the Internet–usually your router in most cases.

0 Likes

#3

Where can I chceck?

this is the output of resolvconf -l:

resolvconf -l
# resolv.conf from lo.dnsmasq
nameserver 127.0.0.1

# resolv.conf from eth0.dhcp
# Generated by dhcpcd from eth0.dhcp
nameserver 127.0.0.1

and pihole -c:

Hostname: raspberrypi (Raspberry Pi 3, Model B)
Uptime: 10:57:19
Task Load: 0.62 0.68 0.58 (Active: 3 of 76 tasks)
CPU usage: 7% (4x 1.2 GHz @ 328k)
RAM usage: 26% (Used: 237 MB of 927 MB)
HDD usage: 36% (Used: 4 GB of 13 GB)
LAN addr: 192.168.0.102 (Gateway: 192.168.0.1)
DHCP usage: 1% (Leased: 1 of 51)
Pi-hole: Active (Blocking: 121805 sites)
Ads Today: 2% (Total: 146 of 8198)
Local Qrys: 1% (2 DNS servers)
Blocked: by.uservoice.com
Top Advert: graph.instagram.com
Top Domain: clients1.google.com
Top Client: localhost

0 Likes

#4

debug log:

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] 2018-04-07:11:27:28 debug log has been initialized.

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

*** [ DIAGNOSING ]: Core version
[i] Core: v3.3.1 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v3.3.1-0-gfbee18e

*** [ DIAGNOSING ]: Web version
[i] Web: v3.3 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v3.3-0-ge48aa29

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v3.0 (How do I update Pi-hole?)

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

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

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

*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 9 (stretch)

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

*** [ DIAGNOSING ]: Processor

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

[✓] IPv6 address(es) bound to the eth0 interface:
fe80::c02f:57ae:35c:cb6b does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)

^ 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.0.1

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

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] aio.lp.mydas.mobi is 192.168.0.102 via localhost (127.0.0.1)
[✓] aio.lp.mydas.mobi is 192.168.0.102 via Pi-hole (192.168.0.102)
[✗] 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
DNSMASQ_LISTENING=local
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSSEC=false
CONDITIONAL_FORWARDING=false
HOSTRECORD=
DHCP_ACTIVE=true
DHCP_START=192.168.0.201
DHCP_END=192.168.0.251
DHCP_ROUTER=192.168.0.1
DHCP_LEASETIME=24
PIHOLE_DOMAIN=lan
DHCP_IPv6=false
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.0.102/24
IPV6_ADDRESS=
PIHOLE_DNS_1=208.67.222.222
PIHOLE_DNS_2=208.67.220.220
QUERY_LOGGING=true
INSTALL_WEB=true
LIGHTTPD_ENABLED=1

*** [ DIAGNOSING ]: Dashboard and block page
[✓] X-Pi-hole: A black hole for Internet advertisements.
[✓] X-Pi-hole: The Pi-hole Web interface is working!

*** [ DIAGNOSING ]: Gravity list
-rw-r–r-- 1 root root 4455247 Apr 7 02:24 /etc/pihole/gravity.list
-----head of gravity.list------
192.168.0.102 0.0.0.0
192.168.0.102 0.r.msn.com
192.168.0.102 0.start.bz
192.168.0.102 000.gaysexe.free.fr

-----tail of gravity.list------
192.168.0.102 zzsyw.com
192.168.0.102 zztxdown.com
192.168.0.102 zzz.clickbank.net
192.168.0.102 zzzrtrcm2.com

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

-rw-r–r-- 1 root root 633 Apr 6 23:55 /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

-rw-r–r-- 1 root root 13 Apr 7 10:24 /etc/pihole/blacklist.txt
moltkskyltyn

-rw-r–r-- 1 root root 48 Apr 7 02:24 /etc/pihole/local.list
192.168.0.102 raspberrypi
192.168.0.102 pi.hole

-rw-r–r-- 1 root root 234 Apr 7 02:24 /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 0 Apr 7 00:39 /etc/pihole/whitelist.txt

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

-rw-r–r-- 1 root root 1546 Apr 7 02:24 /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=extra
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=208.67.222.222
server=208.67.220.220
domain-needed
bogus-priv
local-service

-rw-r–r-- 1 root root 483 Apr 7 02:24 /etc/dnsmasq.d/02-pihole-dhcp.conf
dhcp-authoritative
dhcp-range=192.168.0.201,192.168.0.251,24h
dhcp-option=option:router,192.168.0.1
dhcp-leasefile=/etc/pihole/dhcp.leases
domain=lan

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

-rw-r–r-- 1 root root 3027 Apr 7 02:24 /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 1496 Apr 7 02:24 /etc/cron.d/pihole
58 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 local
31 16 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
@reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot

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

-rw-r–r-- 1 www-data www-data 2129 Apr 7 02:24 /var/log/lighttpd/error.log
2018-04-06 23:54:49: (log.c.217) server started
2018-04-06 23:55:51: (server.c.1828) server stopped by UID = 0 PID = 1
2018-04-06 23:55:51: (log.c.217) server started
2018-04-06 23:55:51: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2018-04-07 00:10:19: (server.c.1828) server stopped by UID = 0 PID = 1
2018-04-07 00:10:19: (log.c.217) server started
2018-04-07 00:10:19: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2018-04-07 00:13:41: (server.c.1828) server stopped by UID = 0 PID = 1
2018-04-07 00:14:23: (log.c.217) server started
2018-04-07 00:14:23: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2018-04-07 00:16:09: (server.c.1828) server stopped by UID = 0 PID = 1
2018-04-07 00:16:30: (log.c.217) server started
2018-04-07 00:16:30: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2018-04-07 01:00:50: (server.c.1828) server stopped by UID = 0 PID = 1
2018-04-07 01:01:05: (log.c.217) server started
2018-04-07 01:01:05: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2018-04-07 01:04:54: (server.c.1828) server stopped by UID = 0 PID = 1
2018-04-07 01:05:19: (log.c.217) server started
2018-04-07 01:05:19: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2018-04-07 01:17:34: (server.c.1828) server stopped by UID = 0 PID = 1
2018-04-07 01:17:49: (log.c.217) server started
2018-04-07 01:17:49: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)
2018-04-07 01:28:10: (server.c.1828) server stopped by UID = 0 PID = 1
2018-04-07 01:28:37: (log.c.217) server started
2018-04-07 01:28:37: (server.c.1295) WARNING: unknown config-key: alias.url (ignored)

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

-rw-r–r-- 1 pihole pihole 52250 Apr 7 10:34 /var/log/pihole-FTL.log
[2018-04-07 00:00:02.536] Gravity list entries: 121803
[2018-04-07 00:00:02.536] No blacklist present
[2018-04-07 00:00:02.536] No wildcard blocking list present
[2018-04-07 00:00:02.537] Notice: Increasing queries struct size from 0 to 10000 (440.17 KB)
[2018-04-07 00:00:02.537] Notice: Increasing domains struct size from 0 to 1000 (460.17 KB)
[2018-04-07 00:00:02.537] Notice: Increasing clients struct size from 0 to 10 (460.33 KB)
[2018-04-07 00:00:02.537] New client: 127.0.0.1 localhost (0/10)
[2018-04-07 00:00:02.537] Notice: Increasing forwarded struct size from 0 to 4 (460.44 KB)
[2018-04-07 00:00:02.646] New forward server: 208.67.220.220 resolver2.opendns.com (0/4)
[2018-04-07 00:00:02.646] Notice: Increasing overTime struct size from 0 to 100 (464.48 KB)
[2018-04-07 00:00:02.646] Imported 22 queries from the long-term database
[2018-04-07 00:00:02.646] Reading from /var/log/pihole.log (rw-r–r--)
[2018-04-07 00:01:30.693] New forward server: 208.67.222.222 resolver1.opendns.com (1/4)
[2018-04-07 00:03:32.601] NOTICE: Received signal SIGHUP - re-reading gravity files
[2018-04-07 00:03:32.847] Gravity list entries: 121803
[2018-04-07 00:03:32.847] No blacklist present
[2018-04-07 00:03:32.847] No wildcard blocking list present
[2018-04-07 00:03:32.847] -> Total DNS queries: 33
[2018-04-07 00:03:32.847] -> Cached DNS queries: 7
[2018-04-07 00:03:32.847] -> Forwarded DNS queries: 26
[2018-04-07 00:03:32.847] -> Exactly blocked DNS queries: 0
[2018-04-07 00:03:32.847] -> Wildcard blocked DNS queries: 0
[2018-04-07 00:03:32.847] -> Unknown DNS queries: 0
[2018-04-07 00:03:32.847] -> Unique domains: 18
[2018-04-07 00:03:32.847] -> Unique clients: 1

*** [ DIAGNOSING ]: Pi-hole log
-rw-r–r-- 1 dnsmasq root 2193929 Apr 7 11:30 /var/log/pihole.log
-----head of pihole.log------
Apr 7 00:00:02 dnsmasq[8440]: 124 127.0.0.1/46827 query[PTR] 220.220.67.208.in-addr.arpa from 127.0.0.1
Apr 7 00:00:02 dnsmasq[8440]: 124 127.0.0.1/46827 forwarded 220.220.67.208.in-addr.arpa to 208.67.220.220
Apr 7 00:00:02 dnsmasq[8440]: 124 127.0.0.1/46827 forwarded 220.220.67.208.in-addr.arpa to 208.67.222.222
Apr 7 00:00:02 dnsmasq[8440]: 124 127.0.0.1/46827 reply 208.67.220.220 is resolver2.opendns.com
Apr 7 00:00:09 dnsmasq[8440]: 125 127.0.0.1/53629 query[A] duckduckgo.com from 127.0.0.1
Apr 7 00:00:09 dnsmasq[8440]: 125 127.0.0.1/53629 forwarded duckduckgo.com to 208.67.220.220
Apr 7 00:00:09 dnsmasq[8440]: 125 127.0.0.1/53629 reply duckduckgo.com is 34.243.144.154
Apr 7 00:00:09 dnsmasq[8440]: 125 127.0.0.1/53629 reply duckduckgo.com is 34.241.201.179
Apr 7 00:00:09 dnsmasq[8440]: 125 127.0.0.1/53629 reply duckduckgo.com is 34.243.160.29
Apr 7 00:00:10 dnsmasq[8440]: 126 127.0.0.1/50151 query[A] translate.googleapis.com from 127.0.0.1
Apr 7 00:00:10 dnsmasq[8440]: 126 127.0.0.1/50151 forwarded translate.googleapis.com to 208.67.220.220
Apr 7 00:00:10 dnsmasq[8440]: 126 127.0.0.1/50151 reply translate.googleapis.com is 216.58.209.138
Apr 7 00:00:16 dnsmasq[8440]: 127 127.0.0.1/39859 query[A] uyxympttvadk.sokrates.bosj.local from 127.0.0.1
Apr 7 00:00:16 dnsmasq[8440]: 127 127.0.0.1/39859 forwarded uyxympttvadk.sokrates.bosj.local to 208.67.220.220
Apr 7 00:00:16 dnsmasq[8440]: 128 127.0.0.1/41913 query[A] brvvldpukugivfl.sokrates.bosj.local from 127.0.0.1
Apr 7 00:00:16 dnsmasq[8440]: 128 127.0.0.1/41913 forwarded brvvldpukugivfl.sokrates.bosj.local to 208.67.220.220
Apr 7 00:00:16 dnsmasq[8440]: 129 127.0.0.1/38037 query[A] spzyygndb.sokrates.bosj.local from 127.0.0.1
Apr 7 00:00:16 dnsmasq[8440]: 129 127.0.0.1/38037 forwarded spzyygndb.sokrates.bosj.local to 208.67.220.220
Apr 7 00:00:16 dnsmasq[8440]: 127 127.0.0.1/39859 reply uyxympttvadk.sokrates.bosj.local is NXDOMAIN
Apr 7 00:00:16 dnsmasq[8440]: 130 127.0.0.1/55146 query[A] uyxympttvadk from 127.0.0.1

0 Likes

#5

Try

ip route

to see what your default gateway is.

From there, see if you can ping it:

ping SOME IP ADDRESS

You can also try mtr or traceroute to a certain Website to see where the failure is.

0 Likes

#6

ip route:

default via 192.168.0.1 dev eth0 src 192.168.0.102 metric 202 
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.102 metric 202 

also I can’t run ping:

ping 172.217.21.174
PING 172.217.21.174 (172.217.21.174) 56(84) bytes of data.

it just stays like that

0 Likes

#7

Okay I found out I had pihole’s dhcp server and my router dhcp both enabled, ping now works:
PING 172.217.21.174 (172.217.21.174) 56(84) bytes of data.
64 bytes from 172.217.21.174: icmp_seq=1 ttl=54 time=17.8 ms
64 bytes from 172.217.21.174: icmp_seq=2 ttl=54 time=18.2 ms
64 bytes from 172.217.21.174: icmp_seq=3 ttl=54 time=17.8 ms
64 bytes from 172.217.21.174: icmp_seq=4 ttl=54 time=17.7 ms
64 bytes from 172.217.21.174: icmp_seq=5 ttl=54 time=17.6 ms
64 bytes from 172.217.21.174: icmp_seq=6 ttl=54 time=17.7 ms
^C
— 172.217.21.174 ping statistics —
6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 17.615/17.847/18.206/0.184 ms

0 Likes

#8

OK, restart your devices to get the correct settings from your router and see if that works.

0 Likes

closed #9

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

0 Likes