Update list of ad-serving domains // DNS resolution is not available

Help
1

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

Expected Behaviour:

it should work!

Actual Behaviour:

in "Update list of ad-serving domains / blacklist / whitelist" i get
[✗] DNS resolution is currently unavailable
[✗] DNS resolution is not available

Debug Token:

5tqd10kyri

2

I am seeing this after update.
Debug token =uod8m07wst

3

Are either of you using Pi-hole with a VPN?

4

No vpn at the moment but I do occasionally use vpn service.

Everything seems to work as far as I can see except adlist update.

I tried adding Google DNS on gateway and in /etc/network/interfaces, but neither seems to help.

5

I am having the same issue. OpenVPN server runs on the Router but the Pi-hole does not use it. Debug token: pgnpufq3py

6

i'm running OpenVPN on the same box, but Pi-Hole does not use it
Pi-Hole is installed on a box in the cloud and uses OpenDNS
Pi-Hole is used directly by my home router and family and clients connected to the VPN server (on the same box)

7

same issue for me and i am using openvpn with pihole

debug token: ml2lbosv1z

8

Can you post the contents of the /etc/resolv.conf files on your Pi-hole devices? I think this is from getent hosts pi.hole fails if /etc/resolv.conf has resolvers other than localhost. · Issue #1806 · pi-hole/pi-hole · GitHub

9

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 192.168.0.1
nameserver 208.67.222.222
nameserver 208.67.222.220
nameserver 127.0.0.1
search google.com

EDIT: okay, I double checked and commented out all the lines except 127.0.0.1 in /etc/resolvconf/resolv.conf.d/head
and restarted the network service, pihole now updates. but this is not good for me, because i don't want the machine hosting pihole to use pihole, hence why i've specified other nameservers to use

10

cat /etc/resolv.conf
#Generated by NetworkManager
nameserver 192.168.1.1

11

Using debian 9

Generated by dhcpcd from eth0.dhcp

/etc/resolv.conf.head can replace this line

nameserver 192.168.0.1

/etc/resolv.conf.tail can replace this line

I tried changing this to 127.0.0.1 but it was replaced with above, the gateway.

Tried supersede dns in dhclient.conf and that di not work either.

I will try /etc/resolvconf/resolv.conf.d/head next.

Edit: creating /etc/resolv.conf.head file with : nameserver 127.0.0.1 works!

12

OK, it's a known issue we are looking into:

https://github.com/pi-hole/pi-hole/issues/1806

https://github.com/pi-hole/pi-hole/issues/1800

https://github.com/pi-hole/pi-hole/issues/1801

2 Likes