DNS resolution is currently unavailable

Help
1

Expected Behaviour:

I'm expecting the blocklists to update when I either pihole -g or via the console.

Actual Behaviour:

I get the following message:
[✗] DNS resolution is currently unavailable
[✗] DNS resolution is not available

Debug Token:

formd70tov

Background information:

I'm running pihole v3.2 on a Synology DS216j as both DHCP and DNS server. I get good connectivity and the console shows that I'm blocking queries, but I just cannot update my blacklists. I'm not using any VPN service whatsoever.
Running pihole -r also gets stuck at trying to run gravity.sh

2

See GitHub:

1 Like
3

Same here on a pi, is there a workaround? read elsewhere to check resolv.conf, it should only contain:

nameserver 127.0.0.1

Check and I have exactly that. removed pihole from network to restore internet.

4

Thank you for the reply. Once I got home, I wanted to see if I could get it to work.
Unfortunately, now my network is completely off. Devices are not assigned an IP anymore so I can't get onto my own network to debug or anything.
I have already rebooted both my NAS (which runs pihole) and router just in case. Phone (wireless; android) and PC (wired; Manjaro) both can't get an IP.

Kind of stuck here and Internet doesn't seem to have an answer.

5

configure network to not use pihole for DNS now. In my case DNS is assigned by router, so I changed router to no longer use pihole.

6

The problem with that is that I cannot get access to my network, thus I am unable to gain access to the router. Direct connection also does not help.

7

Are you not able to connect via IP address? That sounds like a larger network issue. Try resetting your router?

8

Did that, now it seems that I'm able to get things working again. Edited /etc/resolv.conf and now I'm able to get update.

NAS (with pihole) is now both DNS and DHCP server. Got internet, but the admin page seems to be gone when connecting to the correct port. Even edited /etc/lighttpd/lighttpd.conf and made a copy to /etc/lighttpd/external.conf which I edited the correct port to be 2905. Still no admin console.

Debug token is 7v0oeo0flj

Update:
root@Alexandria:/# sudo service lighttpd restart
Duplicate config variable in conditional 0 global: server.modules 2017-12-08 22:38:07: (configfile.c.957) source: cat external.conf 2>/dev/null line: 29 pos: 21 parser failed somehow near here: (EOL)
2017-12-08 22:38:07: (configfile.c.957) source: /etc/lighttpd/lighttpd.conf line: 76 pos: 1 parser failed somehow near here: (EOL)

9

Since you copied it to external.conf it is probably recursively loading the same config over and over. Try renaming the backup.

10

But external.conf says to save it as external.conf or it will be overwritten:

FILE AUTOMATICALLY OVERWRITTEN BY PI-HOLE INSTALL/UPDATE PROCEDURE.
ANY CHANGES MADE TO THIS FILE AFTER INSTALL WILL BE LOST ON THE NEXT UPDATE
#
CHANGES SHOULD BE MADE IN A SEPARATE CONFIG FILE:
/etc/lighttpd/external.conf

11

Hm, perhaps the wording is bad, but what happens is lighttpd.conf includes external.conf at the end, and it's supposed to only contain some small config changes, not a copy of the default config.

12

All right, so I basically only have to add server.port = 2905 to external.conf instead of copying the whole file?

13

And we're back... Devices aren't assigned IP's again so I'm doing something wrong somewhere. I guess that the DHCP server is bugged or anything, but for now I'll have to reset my router and not use pihole until I know what I'm doing wrong.

14

I don't think adding the server port config to the external config works. In any case, we don't really support changing the port because it causes issues with the block page. You can manually modify lighttpd.conf if you really want to change the port.

15

Run pihole -d for a debug token. The lighttpd config shouldn't have changed anything relating the DHCP or DNS.

16

When I'm trying to edit lighttpd.conf to port = 80, it gives me an error upon restarting, saying that port 80 is already in use. Therefore, I've set it to port 2905 (same as pihole, not sure if that can cause problems) but when running pihole -d, I see that lighttpd still uses port 80.

It seems to be working for now, I've reset the router, made the router the DHCP server again (I think that's the solution since the problems only arose when my NAS (pihole) was assigned as DHCP server) and made sure pihole handles the DNS queries.

Anyhow, I wanted to be sure if I missed something somewhere, so here's my latest debug token:
pqd0e542ib

17

Hello, I have the same Problem. Is there an solution?

18

Which problem are you referring to?

19

Problem is solved. I edit the /etc/resolvconf/resolv.conf.d/head file. I added the nameserver 8.8.8.8 and now it works.

20

Sorry, I was unable to get to your debug log in time (they expire after 48 hours). Can you make a new debug token? Thanks.