Can not install PiHole, keep getting "DNS resolution is currently unavailable"

[alexrose]

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

Expected Behaviour:

I tried to install PiHole on 2 different pc's behind same DD-WRT router; first pc, was an intel atom, running an old ubuntu 16.04; second one, was running a fresh install of ubuntu 18.04 then i switched to debian 9.

Actual Behaviour:

I keep getting this error at install on both devices

Blockquote
[i] Restarting services...
[✓] Enabling pihole-FTL service to start on reboot...
[✓] Restarting pihole-FTL service...
[✓] Deleting existing list cache
[i] Pi-hole blocking is enabled
[✗] DNS resolution is currently unavailable
[✗] DNS resolution is not available
Blockquote

When I try to access the web interface it says:

Blockquote
[ERROR] There are no domain lists generated lists within /etc/pihole/ ! Please update gravity by running pihole -g , or repair Pi-hole using pihole -r .
Blockquote
Reinstalled the OS several times and tried the PiHole installation with no success every time;
Trying to repair returns:

Blockquote
[i] FTL Checks...
[✓] Detected x86_64 architecture
[i] Checking for existing FTL binary...
[✗] Downloading and Installing FTL
Error: Unable to get latest release location from GitHub
[✗] FTL Engine not installed
Blockquote

But somehow, pihole seems to be enabled

Blockquote
pihole status
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled
Blockquote

Debug Token:

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

[jfb]

Try the following steps to get your log uploaded:

sudo nano /etc/resolv.conf

edit nameserver 127.0.0.1 to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit

Run pihole -d and upload the log.

[alexrose]

If only it could be that easy. Keep getting same error at upload:
"[✗] There was an error uploading your debug log."

Blockquote
root@beast:~# nslookup google.com
;; connection timed out; no servers could be reached

root@beast:~# dig google.com

; <<>> DiG 9.10.3-P4-Debian <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached

Blockquote

[jfb]

From the Pi, can you ping Google DNS: ping -c5 8.8.8.8

[alexrose]

Blockquote
root@beast:/home/beast# ping -c5 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=121 time=19.2 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=121 time=19.2 ms
Blockquote

Then I edit the resolv.conf and add 8.8.8.8 instead of 127.0.0.1

Blockquote
root@beast:/home/beast# ping -c5 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=121 time=19.6 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=121 time=26.1 ms
Blockquote

But if I try to "/etc/init.d/networking restart" I get "Network is unreachable"

[jfb]

Edit the namserver again and then rerun the dig/nslookup commands for google.com. They should resolve properly using a commercial DNS server.

[jfb]

@alexrose

Then I edit the resolv.conf and add 8.8.8.8 instead of 127.0.0.1

This will make no difference. Since you are not looking for a domain name that requires translation to an IP, there is no DNS traffic involved in a direct ping to an IP address.

[alexrose]

root@beast:/home/beast# tail /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 1.1.1.1

root@beast:/home/beast# nslookup google.com
;; connection timed out; no servers could be reached

root@beast:/home/beast# dig google.com

; <<>> DiG 9.10.3-P4-Debian <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached
root@beast:/home/beast#

[alexrose]

Finally managed to upload it
[✓] Your debug token is: https://tricorder.pi-hole.net/ewl2nw7eg7!

by editing /etc/resolvconf/run/interface/lo.piholeFTL and replacing 127.0.0.1 with 8.8.8.8
then "service resolvconf restart"

If i try to "pihole -r" i still get the annoying error

[i] Pi-hole blocking is enabled
[✗] DNS resolution is currently unavailable
[i] Time until retry: 115

[alexrose]

Somehow, after several "pihole -g" and "pihole -r" the admin interface became accessible.
Still, a ping from the server to google - doesn't work and the block list is empty.

[jfb]

Please generate a new debug log, upload it and post the token.

[alexrose]

New debug token is: w1vdakuh3k

[alexrose]

Ok, it seems that the problem was from my dd-wrt router; enabled "Forced DNS Redirection" and now it;s working fine.