DNS resolution is currently unavailable

Hi!

I made a fresh install of pihole on my raspberry-pi with docker. And pi-hole is not blocking any ads.
When I try to update gravity, following 2 errors appear:

  • [✗] DNS resolution is currently unavailable*
  • [✗] DNS resolution is not available*

Home

system details

  `.::///+:/-.        --///+//-:``    pi@raspberrypi
 `+oooooooooooo:   `+oooooooooooo:    --------------
  /oooo++//ooooo:  ooooo+//+ooooo.    OS: Raspbian GNU/Linux 10 (buster) armv7l
  `+ooooooo:-:oo-  +o+::/ooooooo:     Host: Raspberry Pi 4 Model B Rev 1.2
   `:oooooooo+``    `.oooooooo+-      Kernel: 5.10.103-v7l+
     `:++ooo/.        :+ooo+/.`       Uptime: 5 days, 8 hours, 29 mins
        ...`  `.----.` ``..           Packages: 1521 (dpkg)
     .::::-``:::::::::.`-:::-`        Shell: bash 5.0.3
    -:::-`   .:::::::-`  `-:::-       Terminal: /dev/pts/0
   `::.  `.--.`  `` `.---.``.::`      CPU: BCM2711 (4) @ 1.500GHz
       .::::::::`  -::::::::` `       Memory: 703MiB / 3838MiB
 .::` .:::::::::- `::::::::::``::.
-:::` ::::::::::.  ::::::::::.`:::-
::::  -::::::::.   `-::::::::  ::::
-::-   .-:::-.``....``.-::-.   -::-
 .. ``       .::::::::.     `..`..
   -:::-`   -::::::::::`  .:::::`
   :::::::` -::::::::::` :::::::.
   .:::::::  -::::::::. ::::::::
    `-:::::`   ..--.`   ::::::.
      `...`  `...--..`  `...`
            .::::::::::
             `.-::::-`

Here's my 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] 2022-08-29:18:48:31 debug log has been initialized.
[i] System has been running for 5 days, 8 hours, 19 minutes

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

*** [ DIAGNOSING ]: Core version
[i] Core: v5.9 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Remotes: origin	https://github.com/pi-hole/pi-hole.git (fetch)
             origin	https://github.com/pi-hole/pi-hole.git (push)
[i] Branch: master
[i] Commit: v5.9-0-g6ffa2ba

*** [ DIAGNOSING ]: Web version
[i] Web: v5.11 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Remotes: origin	https://github.com/pi-hole/AdminLTE.git (fetch)
             origin	https://github.com/pi-hole/AdminLTE.git (push)
[i] Branch: master
[i] Commit: v5.11-0-g64bbce9

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

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

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

*** [ DIAGNOSING ]: Operating system
[i] dig return code:  0
[i] dig response:  "Raspbian=10,11 Ubuntu=18,20,21,22 Debian=10,11 Fedora=34 CentOS=7,8 Rocky=8"
[✓] Distro:  Debian
[✓] Version: 10

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

*** [ DIAGNOSING ]: FirewallD
[✓] Firewalld service not detected

*** [ DIAGNOSING ]: Processor
[✓] armv7l

*** [ DIAGNOSING ]: Disk usage
   Filesystem      Size  Used Avail Use% Mounted on
   overlay          59G   26G   30G  47% /
   tmpfs            64M     0   64M   0% /dev
   tmpfs           1.9G     0  1.9G   0% /sys/fs/cgroup
   shm              64M  1.3M   63M   2% /dev/shm
   /dev/root        59G   26G   30G  47% /etc/pihole
   tmpfs           1.9G     0  1.9G   0% /proc/asound
   tmpfs           1.9G     0  1.9G   0% /sys/firmware

*** [ DIAGNOSING ]: Network interfaces and addresses
   1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
       link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
       inet 127.0.0.1/8 scope host lo
          valid_lft forever preferred_lft forever
   4412: eth0@if4413: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
       link/ether 02:42:ac:17:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
       inet 172.23.0.2/16 brd 172.23.255.255 scope global eth0
          valid_lft forever preferred_lft forever

*** [ DIAGNOSING ]: Network routing table
   default via 172.23.0.1 dev eth0 
   172.23.0.0/16 dev eth0 proto kernel scope link src 172.23.0.2 

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
    172.23.0.2/16

[✗] No IPv6 address(es) found on the eth0 interface.

[i] Default IPv4 gateway: 172.23.0.1
   * Pinging 172.23.0.1...
[✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
    udp:127.0.0.11:33087 is in use by <unknown>
[✗] udp:0.0.0.0:53 is in use by  (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] udp:*:53 is in use by  (https://docs.pi-hole.net/main/prerequisites/#ports)
    tcp:127.0.0.11:35749 is in use by <unknown>
[✗] tcp:127.0.0.1:4711 is in use by  (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:0.0.0.0:80 is in use by  (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:0.0.0.0:53 is in use by  (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:[::]:80 is in use by  (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:[::]:53 is in use by  (https://docs.pi-hole.net/main/prerequisites/#ports)

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve  on lo (127.0.0.1)
[✓] No IPv4 address available on eth0@if4413
[✓] doubleclick.com is 216.58.203.14 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] No IPv6 address available on lo
[✓] No IPv6 address available on eth0@if4413
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   DHCP packets received on interface eth0: 0
   DHCP packets received on interface lo: 0

*** [ DIAGNOSING ]: Pi-hole processes
[✗] lighttpd daemon is inactive
[✗] pihole-FTL daemon is inactive

*** [ DIAGNOSING ]: Pi-hole-FTL full status
[i] systemctl:  command not found

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_DNS_1=8.8.8.8
    PIHOLE_DNS_2=8.8.4.4
    BLOCKING_ENABLED=true
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    WEBTHEME=default-dark
    ADMIN_EMAIL=surjitsahoo0@gmail.com
    PIHOLE_INTERFACE=eth0
    QUERY_LOGGING=true

*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Expires: Mon, 29 Aug 2022 13:18:49 GMT
Cache-Control: max-age=0
Date: Mon, 29 Aug 2022 13:18:49 GMT
Server: lighttpd/1.4.53

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

*** [ DIAGNOSING ]: Gravity Database
-rw-rw-r-- 1 pihole pihole 92K Aug 29 09:51 /etc/pihole/gravity.db

*** [ DIAGNOSING ]: Info table
   property              value                                   
   --------------------  ----------------------------------------
   version               15                                      
   Last gravity run finished at: 

   ----- First 10 Gravity Domains -----


*** [ DIAGNOSING ]: Groups
   id    enabled  name                                                date_added           date_modified        description                                       
   ----  -------  --------------------------------------------------  -------------------  -------------------  --------------------------------------------------
   0           1  Default                                             2022-08-29 09:51:14  2022-08-29 09:51:14  The default group                                 

*** [ DIAGNOSING ]: Domainlist (0/1 = exact white-/blacklist, 2/3 = regex white-/blacklist)

*** [ DIAGNOSING ]: Clients

*** [ DIAGNOSING ]: Adlists
   id     enabled  group_ids     address                                                                                               date_added           date_modified        comment                                           
   -----  -------  ------------  ----------------------------------------------------------------------------------------------------  -------------------  -------------------  --------------------------------------------------
   1            1  0             https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts                                      2022-08-29 09:51:15  2022-08-29 09:51:15  Migrated from /etc/pihole/adlists.list            

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

-rw-r--r-- 1 root root 122 Aug 29 11:34 /etc/pihole/custom.list
   192.168.0.1 router
   192.168.0.1 router.lan
   192.168.0.100 pi.lan
   192.168.0.100 pi
   192.168.0.100 plex
   192.168.0.100 plex.lan

-rw-r--r-- 1 root root 241 Aug 28 09:32 /etc/pihole/logrotate
   /var/log/pihole/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-rw-r-- 1 pihole root 157 Aug 29 18:43 /etc/pihole/pihole-FTL.conf
   REPLY_ADDR4=0.0.0.0
   LOCAL_IPV4=192.168.0.100

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

-rw-r--r-- 1 root root 1.4K Aug 29 18:43 /etc/dnsmasq.d/01-pihole.conf
   addn-hosts=/etc/pihole/local.list
   addn-hosts=/etc/pihole/custom.list
   localise-queries
   no-resolv
   cache-size=10000
   log-queries
   log-facility=/var/log/pihole.log
   log-async
   server=8.8.8.8
   server=8.8.4.4
   interface=eth0

-rw-r--r-- 1 root root 2.2K Aug 29 18:43 /etc/dnsmasq.d/06-rfc6761.conf
   server=/test/
   server=/localhost/
   server=/invalid/
   server=/bind/
   server=/onion/

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

-rw-r--r-- 1 root root 0 Aug 29 18:43 /etc/lighttpd/external.conf

-rw-r--r-- 1 root root 3.7K Aug 29 18:43 /etc/lighttpd/lighttpd.conf
   server.modules = (
       "mod_access",
       "mod_accesslog",
       "mod_auth",
       "mod_expire",
       "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             = "/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" )
   mimetype.assign = (
       ".ico"   => "image/x-icon",
       ".jpeg"  => "image/jpeg",
       ".jpg"   => "image/jpeg",
       ".png"   => "image/png",
       ".svg"   => "image/svg+xml",
       ".css"   => "text/css; charset=utf-8",
       ".html"  => "text/html; charset=utf-8",
       ".js"    => "text/javascript; charset=utf-8",
       ".json"  => "application/json; charset=utf-8",
       ".map"   => "application/json; charset=utf-8",
       ".txt"   => "text/plain; charset=utf-8",
       ".eot"   => "application/vnd.ms-fontobject",
       ".otf"   => "font/otf",
       ".ttc"   => "font/collection",
       ".ttf"   => "font/ttf",
       ".woff"  => "font/woff",
       ".woff2" => "font/woff2"
   )
   include_shell "cat external.conf 2>/dev/null"
   include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
   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"] =~ "^/admin/\.(.*)" {
       url.access-deny = ("")
   }
   $HTTP["url"] =~ "/(teleporter|api_token)\.php$" {
       $HTTP["referer"] =~ "/admin/settings\.php" {
           setenv.add-response-header = ( "X-Frame-Options" => "SAMEORIGIN" )
       }
   }
   expire.url = ( "" => "access plus 0 seconds" )

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

-rw-r--r-- 1 root root 1.8K Feb 13  2022 /etc/cron.d/pihole
   6 3   * * 7   root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log
   00 00   * * *   root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole flush once quiet
   @reboot root /usr/sbin/logrotate --state /var/lib/logrotate/pihole /etc/pihole/logrotate
   */10 *  * * *   root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker local
   50 14  * * *   root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker remote
   @reboot root    PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker remote reboot

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

-rw-r--r-- 1 www-data www-data 262 Aug 29 18:43 /var/log/lighttpd/error.log
   -----head of error.log------
   2022-08-29 10:19:33: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-08-29 18:43:32: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-08-29 18:43:32: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 

   -----tail of error.log------
   2022-08-29 10:19:33: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-08-29 18:43:32: (server.c.1464) server started (lighttpd/1.4.53) 
   2022-08-29 18:43:32: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused 

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

-rw-r--r-- 1 pihole pihole 29K Aug 29 18:43 /var/log/pihole-FTL.log
   -----head of pihole-FTL.log------
   [2022-08-29 10:19:33.349 484M] Using log file /var/log/pihole-FTL.log
   [2022-08-29 10:19:33.349 484M] ########## FTL started on rpicontainer! ##########
   [2022-08-29 10:19:33.349 484M] FTL branch: master
   [2022-08-29 10:19:33.350 484M] FTL version: v5.14
   [2022-08-29 10:19:33.350 484M] FTL commit: 52e6b95
   [2022-08-29 10:19:33.350 484M] FTL date: 2022-02-12 19:58:34 +0000
   [2022-08-29 10:19:33.350 484M] FTL user: pihole
   [2022-08-29 10:19:33.350 484M] Compiled for armv7hf (compiled on CI) using arm-linux-gnueabihf-gcc (Debian 6.3.0-18) 6.3.0 20170516
   [2022-08-29 10:19:33.350 484M] Creating mutex
   [2022-08-29 10:19:33.350 484M] Creating mutex
   [2022-08-29 10:19:33.352 484M] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
   [2022-08-29 10:19:33.352 484M]    SOCKET_LISTENING: only local
   [2022-08-29 10:19:33.352 484M]    AAAA_QUERY_ANALYSIS: Show AAAA queries
   [2022-08-29 10:19:33.352 484M]    MAXDBDAYS: max age for stored queries is 365 days
   [2022-08-29 10:19:33.352 484M]    RESOLVE_IPV6: Resolve IPv6 addresses
   [2022-08-29 10:19:33.353 484M]    RESOLVE_IPV4: Resolve IPv4 addresses
   [2022-08-29 10:19:33.353 484M]    DBINTERVAL: saving to DB file every minute
   [2022-08-29 10:19:33.353 484M]    DBFILE: Using /etc/pihole/pihole-FTL.db
   [2022-08-29 10:19:33.353 484M]    MAXLOGAGE: Importing up to 24.0 hours of log data
   [2022-08-29 10:19:33.353 484M]    PRIVACYLEVEL: Set to 0
   [2022-08-29 10:19:33.353 484M]    IGNORE_LOCALHOST: Show queries from localhost
   [2022-08-29 10:19:33.353 484M]    BLOCKINGMODE: Null IPs for blocked domains
   [2022-08-29 10:19:33.353 484M]    ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
   [2022-08-29 10:19:33.353 484M]    DBIMPORT: Importing history from database
   [2022-08-29 10:19:33.353 484M]    PIDFILE: Using /run/pihole-FTL.pid
   [2022-08-29 10:19:33.354 484M]    PORTFILE: Using /run/pihole-FTL.port
   [2022-08-29 10:19:33.354 484M]    SOCKETFILE: Using /run/pihole/FTL.sock
   [2022-08-29 10:19:33.354 484M]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2022-08-29 10:19:33.354 484M]    MACVENDORDB: Using /etc/pihole/macvendor.db
   [2022-08-29 10:19:33.354 484M]    GRAVITYDB: Using /etc/pihole/gravity.db
   [2022-08-29 10:19:33.354 484M]    PARSE_ARP_CACHE: Active
   [2022-08-29 10:19:33.355 484M]    CNAME_DEEP_INSPECT: Active
   [2022-08-29 10:19:33.355 484M]    DELAY_STARTUP: No delay requested.
   [2022-08-29 10:19:33.355 484M]    BLOCK_ESNI: Enabled, blocking _esni.{blocked domain}
   [2022-08-29 10:19:33.355 484M]    NICE: Cannot change niceness to -10 (permission denied)

   -----tail of pihole-FTL.log------
   [2022-08-29 18:43:32.208 483M]    REPLY_WHEN_BUSY: Permit queries when the database is busy
   [2022-08-29 18:43:32.208 483M]    BLOCK_TTL: 2 seconds
   [2022-08-29 18:43:32.208 483M]    BLOCK_ICLOUD_PR: Enabled
   [2022-08-29 18:43:32.208 483M]    CHECK_LOAD: Enabled
   [2022-08-29 18:43:32.208 483M]    CHECK_SHMEM: Warning if shared-memory usage exceeds 90%
   [2022-08-29 18:43:32.208 483M]    CHECK_DISK: Warning if certain disk usage exceeds 90%
   [2022-08-29 18:43:32.209 483M] Finished config file parsing
   [2022-08-29 18:43:32.210 483M] Database version is 12
   [2022-08-29 18:43:32.210 483M] Resizing "FTL-strings" from 40960 to (81920 * 1) == 81920 (/dev/shm: 1.1MB used, 67.1MB total, FTL uses 1.1MB)
   [2022-08-29 18:43:32.211 483M] Imported 0 alias-clients
   [2022-08-29 18:43:32.211 483M] Database successfully initialized
   [2022-08-29 18:43:32.245 483M] New upstream server: 8.8.4.4:53 (0/256)
   [2022-08-29 18:43:32.258 483M] New upstream server: 8.8.8.8:53 (1/256)
   [2022-08-29 18:43:32.302 483M] Resizing "FTL-queries" from 180224 to (8192 * 44) == 360448 (/dev/shm: 1.2MB used, 67.1MB total, FTL uses 1.1MB)
   [2022-08-29 18:43:32.339 483M] Imported 7026 queries from the long-term database
   [2022-08-29 18:43:32.339 483M]  -> Total DNS queries: 7026
   [2022-08-29 18:43:32.339 483M]  -> Cached DNS queries: 1878
   [2022-08-29 18:43:32.339 483M]  -> Forwarded DNS queries: 5061
   [2022-08-29 18:43:32.339 483M]  -> Blocked DNS queries: 0
   [2022-08-29 18:43:32.339 483M]  -> Unknown DNS queries: 0
   [2022-08-29 18:43:32.339 483M]  -> Unique domains: 652
   [2022-08-29 18:43:32.339 483M]  -> Unique clients: 11
   [2022-08-29 18:43:32.339 483M]  -> Known forward destinations: 2
   [2022-08-29 18:43:32.339 483M] Successfully accessed setupVars.conf
   [2022-08-29 18:43:32.340 483M] listening on 0.0.0.0 port 53
   [2022-08-29 18:43:32.341 483M] listening on :: port 53
   [2022-08-29 18:43:32.344 483M] PID of FTL process: 483
   [2022-08-29 18:43:32.345 483/T491] Listening on port 4711 for incoming IPv4 telnet connections
   [2022-08-29 18:43:32.345 483/T493] Listening on Unix socket
   [2022-08-29 18:43:32.345 483M] INFO: FTL is running as user pihole (UID 999)
   [2022-08-29 18:43:32.345 483M] Reloading DNS cache
   [2022-08-29 18:43:33.350 483/T494] gravityDB_count(SELECT value FROM info WHERE property = 'gravity_count';) - SQL error step no more rows available
   [2022-08-29 18:43:33.351 483/T494] Count of gravity domains not available. Please run pihole -g
   [2022-08-29 18:43:33.355 483/T494] Compiled 0 whitelist and 0 blacklist regex filters for 11 clients in 3.5 msec
   [2022-08-29 18:43:34.349 483M] Blocking status is enabled

*** [ DIAGNOSING ]: contents of /dev/shm
-rw------- 1 pihole pihole 668K Aug 29 18:43 /dev/shm/FTL-clients
-rw------- 1 pihole pihole 240 Aug 29 18:43 /dev/shm/FTL-counters
-rw------- 1 pihole pihole 4.0K Aug 29 18:43 /dev/shm/FTL-dns-cache
-rw------- 1 pihole pihole 20K Aug 29 18:43 /dev/shm/FTL-domains
-rw------- 1 pihole pihole 56 Aug 29 18:43 /dev/shm/FTL-lock
-rw------- 1 pihole pihole 12K Aug 29 18:43 /dev/shm/FTL-overTime
-rw------- 1 pihole pihole 4.0K Aug 29 18:43 /dev/shm/FTL-per-client-regex
-rw------- 1 pihole pihole 352K Aug 29 18:48 /dev/shm/FTL-queries
-rw------- 1 pihole pihole 12 Aug 29 18:43 /dev/shm/FTL-settings
-rw------- 1 pihole pihole 80K Aug 29 18:43 /dev/shm/FTL-strings
-rw------- 1 pihole pihole 156K Aug 29 18:43 /dev/shm/FTL-upstreams

*** [ DIAGNOSING ]: contents of /etc

-rw-r--r-- 1 root root 37 Aug 29 18:43 /etc/dnsmasq.conf
   conf-dir=/etc/dnsmasq.d
   user=pihole

-rw-rw-r-- 1 root 1000 38 Aug 29 18:43 /etc/resolv.conf
   nameserver 127.0.0.11
   options ndots:0

*** [ DIAGNOSING ]: Pi-hole diagnosis messages

*** [ DIAGNOSING ]: Locale
    LANG=

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 2.7M Aug 29 18:48 /var/log/pihole.log
   -----head of pihole.log------
   Aug 29 10:19:33 dnsmasq[484]: started, version pi-hole-2.87test8 cachesize 10000
   Aug 29 10:19:33 dnsmasq[484]: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n IDN DHCP DHCPv6 Lua TFTP no-conntrack ipset no-nftset auth cryptohash DNSSEC loop-detect inotify dumpfile
   Aug 29 10:19:33 dnsmasq[484]: using nameserver 8.8.8.8#53
   Aug 29 10:19:33 dnsmasq[484]: using nameserver 8.8.4.4#53
   Aug 29 10:19:33 dnsmasq[484]: using only locally-known addresses for onion
   Aug 29 10:19:33 dnsmasq[484]: using only locally-known addresses for bind
   Aug 29 10:19:33 dnsmasq[484]: using only locally-known addresses for invalid
   Aug 29 10:19:33 dnsmasq[484]: using only locally-known addresses for localhost
   Aug 29 10:19:33 dnsmasq[484]: using only locally-known addresses for test
   Aug 29 10:19:33 dnsmasq[484]: read /etc/hosts - 7 addresses
   Aug 29 10:19:33 dnsmasq[484]: read /etc/pihole/custom.list - 4 addresses
   Aug 29 10:19:33 dnsmasq[484]: failed to load names from /etc/pihole/local.list: No such file or directory
   Aug 29 10:19:34 dnsmasq[484]: query[A] 172-17-0-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct from 192.168.0.100
   Aug 29 10:19:34 dnsmasq[484]: forwarded 172-17-0-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct to 8.8.8.8
   Aug 29 10:19:34 dnsmasq[484]: forwarded 172-17-0-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct to 8.8.4.4
   Aug 29 10:19:34 dnsmasq[484]: query[AAAA] 172-17-0-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct from 192.168.0.100
   Aug 29 10:19:34 dnsmasq[484]: forwarded 172-17-0-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct to 8.8.8.8
   Aug 29 10:19:34 dnsmasq[484]: forwarded 172-17-0-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct to 8.8.4.4
   Aug 29 10:19:34 dnsmasq[484]: reply 172-17-0-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct is NODATA-IPv6
   Aug 29 10:19:34 dnsmasq[484]: reply 172-17-0-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct is 172.17.0.1

   -----tail of pihole.log------
   Aug 29 18:48:52 dnsmasq[483]: reply 172-26-0-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct is NODATA-IPv6
   Aug 29 18:48:52 dnsmasq[483]: reply 192-168-0-100.abcdefghijklmnopqrstuvwxyz012345.plex.direct is NODATA-IPv6
   Aug 29 18:48:52 dnsmasq[483]: query[A] plex.tv from 192.168.0.100
   Aug 29 18:48:52 dnsmasq[483]: forwarded plex.tv to 8.8.4.4
   Aug 29 18:48:52 dnsmasq[483]: query[AAAA] plex.tv from 192.168.0.100
   Aug 29 18:48:52 dnsmasq[483]: forwarded plex.tv to 8.8.4.4
   Aug 29 18:48:52 dnsmasq[483]: reply plex.tv is NODATA-IPv6
   Aug 29 18:48:52 dnsmasq[483]: reply plex.tv is 34.252.41.177
   Aug 29 18:48:52 dnsmasq[483]: reply plex.tv is 52.212.166.170
   Aug 29 18:48:52 dnsmasq[483]: reply plex.tv is 34.250.46.62
   Aug 29 18:48:52 dnsmasq[483]: reply plex.tv is 54.154.55.122
   Aug 29 18:48:52 dnsmasq[483]: reply plex.tv is 176.34.175.0
   Aug 29 18:48:52 dnsmasq[483]: query[A] plex.tv from 192.168.0.100
   Aug 29 18:48:52 dnsmasq[483]: cached plex.tv is 176.34.175.0
   Aug 29 18:48:52 dnsmasq[483]: cached plex.tv is 54.154.55.122
   Aug 29 18:48:52 dnsmasq[483]: cached plex.tv is 34.250.46.62
   Aug 29 18:48:52 dnsmasq[483]: cached plex.tv is 52.212.166.170
   Aug 29 18:48:52 dnsmasq[483]: cached plex.tv is 34.252.41.177
   Aug 29 18:48:52 dnsmasq[483]: query[AAAA] plex.tv from 192.168.0.100
   Aug 29 18:48:52 dnsmasq[483]: cached plex.tv is NODATA-IPv6


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

   * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
[i] Debug script running in automated mode
    * Using curl for transmission.

Please help.

Thanks in advance.

You are running an older version of Pi-hole.

*** [ DIAGNOSING ]: Core version
[i] Core: v5.9 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Remotes: origin	https://github.com/pi-hole/pi-hole.git (fetch)
             origin	https://github.com/pi-hole/pi-hole.git (push)
[i] Branch: master
[i] Commit: v5.9-0-g6ffa2ba

*** [ DIAGNOSING ]: Web version
[i] Web: v5.11 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Remotes: origin	https://github.com/pi-hole/AdminLTE.git (fetch)
             origin	https://github.com/pi-hole/AdminLTE.git (push)
[i] Branch: master
[i] Commit: v5.11-0-g64bbce9

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

The current versions are:

  Pi-hole version is v5.11.4 (Latest: v5.11.4)
  AdminLTE version is v5.13 (Latest: v5.13)
  FTL version is v5.16.3 (Latest: v5.16.3)

I recommend you update your container image.

The latest version is not even starting, some timeout issue.. In github I found the recommendation to switch to older version of pihole.. I switched to exact version mentioned in github issue..
Now pi-hole is starting, but getting the above issue

4412: eth0@if4413: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ac:17:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 172.23.0.2/16

This is the address setup for pi-hole on whatever is hosting it.

If you look through the logs, you have a class C (192.168.) address in the logs as well.

Generally this can work if going through a router (jumping subnets--I still do not fully understand subnets) but it may be simpler to just set pi-hole to a 192.168 or 172 network, just make it all the same.

Alternatively, I believe you can have 172 on your pi-hole, but set your gateway to an upstream router for your internet service to a suitable 192 address on the modem or wireless router that is also set with a functional setup in the 192 range

I believe 172 network is configured by docker and 182.168 is the pi-hole's ethernet IP. Internet is working inside the container, I am able to ping internet websites, I am able to dig and get IP responses as well.

O.K. so I don't have a great workaround, but this hopefully, should be an effective measure to get you by.

If you can go download the adlist files you would like to use, and add them manually.

In the web interface go to group management and type in the files like so:

In the file path bar:

file:/// (yes three slashes, the third is to indicate the root filesystem)

file:///home/your-user-name/andwhatever-folder

Ex:

file:///home/username/adlist/exactfilename.txt

In the docker container, cat /etc/resolv.conf. It may look something like this:

nameserver 127.0.0.11
options ndots:0

where the nameserver is something other than 127.0.0.1. So the Gravity 'DNS resolution is unavailable' error means exactly what it says.

To fix this (temporarily) do this:

echo nameserver 127.0.0.1 > /etc/resolv.conf

This sets the nameserver (for the container) to localhost, and the 'DNS Resolution is unavailable' error should go away (so long as your PiHole is otherwise working in the first place).

I'm not sure why the /etc/resolv.conf is screwed up in the first place, but it is re-generated on container start, so this 'fix' needs to be applied after every reboot/restart.

1 Like

It appears that docker does this deliberately (127.0.0.11) and does some iptables black magic that usually works. Apparently the 'DNS resolution is unavailable problem' isn't specific to PiHole or Gravity.

Something that can be tried (but I haven't tested yet) is adding the flag --dns 127.0.0.1 to docker run or for docker compose up -d add

dns: 
  - 127.0.0.1

to the service in compose.yaml