Pi: DNS Resolution is not available after update to 3.2

##Setup
Raspberry Pi2, Rasbian jessie (updated that before updating to pihole 3.2)

Expected Behaviour:

Working internet

Actual Behaviour: (running pihole -r)

Laptop and ios devices won't open any site anymore

pihole -r has this part
[i] Preparing to run gravity.sh to refresh hosts...
[i] Cleaning up previous install (preserving whitelist/blacklist)
[i] Running gravity.sh
[✗] DNS resolution is currently unavailable
[i] Waiting up to 116 seconds before continuing...

Debug Token:

Your debug token is: cqy37gjy5l

This is fixed in the next release

1 Like

Thanks. Any workaround I can try? checked the resolv.conf but it only has 127.0.0.1

And will updating work normally, via pihole -up?

Will you please run:

pihole checkout dev

gravity will run as part of this process; if you run pihole -g again, you can verify if the fix in place will work for you. Please let me know either way.

You may want to switch back to the master branch after testing as development is not always stable.

1 Like

ofcourse, running it now. Seems to switch to development branch (how do I switch back in a week or so when all works? "pihole checkout master"?)

It is running and gives this, had that yesterday when running repair. not sure if/what it means or implies
[✓] Creating directory for blocking page, and copying files
[✗] Backing up index.lighttpd.html
No default index.lighttpd.html file found... not backing up

then further down I get
[i] Preparing to run gravity.sh to refresh hosts...
[i] Cleaning up previous install (preserving whitelist/blacklist)
[i] Running gravity.sh
[✗] DNS resolution is currently unavailable
[i] Waiting up to 113 seconds before continuing...

now waiting for the timer to reach 0, it just has:
[i] Running gravity.sh
[✗] DNS resolution is currently unavailable
[✓] DNS resolution is now available

FYI - saw the other tickets but some were on a synology or were fixed with "nameserver 127.0.0.1" - mine wasnt hence the post.

Then ran pihole -g
pi@raspberrypi-pi-hole:~ $ pihole -g
[✗] DNS resolution is currently unavailable
[i] Waiting up to 117 seconds before continuing...

after timeout runs it does seem to continue:
pi@raspberrypi-pi-hole:~ $ pihole -g
[✗] DNS resolution is currently unavailable
[✓] DNS resolution is now available

[i] Neutrino emissions detected...
[✓] Pulling blocklist source list into range

[i] Target: raw.githubusercontent.com (hosts)
[✓] Status: Retrieval successful

Yup!

OK, so when you ran the checkout command, it didn't work, but then running a subsequent pihole -g did solve it, correct?

If that's the case, the new code in development should fix the problem you are seeing.

Can you run a pihole -g once more to verify.

Thanks. As I had no internet I switched of my router to use the pihole. Swithing back requires reconfig and reboot, a 10 minute job. Not sure how to tell if I am ready to use the DNS again but you seem positive so will try. Honostly quite the noob so from all the logs not sure if they are good or not.

Just tried pihole -g again and it starts running right away
pi@raspberrypi-pi-hole:~ $ pihole -g
[i] Neutrino emissions detected...
[✓] Pulling blocklist source list into range

Also reran pihole -r repair. it is still doing the timout thing
[i] Preparing to run gravity.sh to refresh hosts...
[i] Cleaning up previous install (preserving whitelist/blacklist)
[i] Running gravity.sh
[✗] DNS resolution is currently unavailable
[i] Waiting up to 117 seconds before continuing...

and it shows the lighttpd error, is that normal?
[✗] Backing up index.lighttpd.html
No default index.lighttpd.html file found... not backing up

Again - clueless - if you think I can try using dns again let me know, also happy to test other stuff

Update: reconfigured network to use pi-hole again and internet is working. Thx!
Will switch back to master once I see a new official update

Update: tried to update lists in webinterface:

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

and trying to open a normal site like tweakers.net no longer works:
This site can’t be reached

tweakers.net’s server DNS address could not be found.
Try:
Checking the connection
Checking the proxy, firewall, and DNS configuration
Running Windows Network Diagnostics
ERR_NAME_NOT_RESOLVED

Run pihole -d for a debug token.

here it is:
Your debug token is: pv230sa2f9

Check that your Windows device is using only the Pi-hole as DNS. The debug log shows that it is resolving names correctly.

Thanks, appreciated. Now back to work and need to make sure internet at home works 100% while I am at the office, will need to test other evenings.

Any significance in the timeouts I seem to be getting in the web interface and after a command prompt repair?

just did abother pihole -r and I get them when gravity is executed (still on pihole checkout dev)
[i] Preparing to run gravity.sh to refresh hosts...
[i] Cleaning up previous install (preserving whitelist/blacklist)
[i] Running gravity.sh
[✗] DNS resolution is currently unavailable
[i] Waiting up to 116 seconds before continuing...

Your debug token is: lfqdghbarn

saw some red flashing by on ipv6 - clueless if it means anything but thought I'd highlight.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a k nown ad-serving domain
[✓] anticrizisnaya-akciya.ru is 192.168.1.44 via localhost (127.0.0.1)
[✓] anticrizisnaya-akciya.ru is 192.168.1.44 via Pi-hole (192.168.1.44)
[✓] doubleclick.com is 172.217.17.142 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a k nown ad-serving domain
[✓] www.engenhariaforma.com.br is 2001:984:207c:1:b40c:deab:4f46:972a via localh ost (::1)
[✗] Failed to resolve www.engenhariaforma.com.br via Pi-hole (2001:984:207c:1:b4 0c:deab:4f46:972a)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860 :4860::8888)

As long as gravity gets past the DNS resolution timeout, it is fine (it needs to wait until dnsmasq is ready before it can download lists).

The IPv6 error may or may not be a problem. Either your network doesn't fully support IPv6, your IPv6 address changed since you configured Pi-hole, or dnsmasq is somehow not listening on that interface (and there's probably other possible reasons). Since it couldn't resolve via Google's public IPv6 server, it's likely your network just doesn't fully support IPv6.

Thanks appreciated. Have switched back to master and repaired. Seems to work now. When I update lists I will get the 120 second timeout, at some point it starts working again. Seems like a short delay and that is fine.

Will look into the ipv6

This issue is resolved in v3.2.1, which was released today.