All my devices, Mac, iPhone, Tablet, Alexa should connect to the internet
Alexa & Google Home connecting to the internet (even Firefox on my Echo Show) BUT my devices, iMac, iPhone, Shield Tablet etc NOT connecting to the internet after the most recent update to 4.2.2
From your debug log - the setup for Pi-Hole does not match the network address. Are you running Pi-Hole with a VPN for external access? If so, then you may need to re-set your Pi-Hole settings for the VPN.
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the tun0 interface:
10.8.0.1/24 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
[i] Default IPv4 gateway: 192.168.1.1
* Pinging 192.168.1.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] aeon.crypto-webminer.com is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve aeon.crypto-webminer.com via Pi-hole (192.168.1.18)
[✓] doubleclick.com is 172.217.1.46 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Setup variables
DHCP_START=192.168.1.201
DHCP_END=192.168.1.251
DHCP_ROUTER=192.168.1.1
DHCP_LEASETIME=24
PIHOLE_DOMAIN=lan
DHCP_IPv6=false
DHCP_ACTIVE=false
BLOCKING_ENABLED=true
PIHOLE_INTERFACE=tun0
IPV4_ADDRESS=192.168.1.18/24
Hi @jfb
Yip, I've just this week installed pivpn and everything was working until the update earlier. So as per your advice I ran pinhole -r and reset the settings, everything now seems to be working again, even openvpn on my iPhone with Ad blocking. I don't understand what went wrong, thats the frustrating thing, I know just enough but far too little 
Many thanks for your reply, much appreciated!
what I really don't understand though is why I couldn't access the internet via my browsers but Echo & Google home could 
just a parting thought!
I have seen some IOT devices use their own DNS for lookups when the primary fails. I used to run a DNS "capture" rule on my router that would re-write any request to port 53 to my private DNS. I do remember that either Ooma or Vonage would do this so I wouldn't doubt that Amazon and Google may have built this into their devices.
Makes sense and kind of obvious, thanks!
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.