Please follow the below template, it will help us to help you!
Expected Behaviour:
_ad be blocked and the query log to be reflect on site visited and in time
Actual Behaviour:
tested many site but the ad still showing up, for the last few hours, only 1 blocked query in dashboard
_the query log still showing the last query is 2019-12-26 00:01:28 eventhough I kept trying differnet site after that time, the time now is 12:31 am., the query log is not updating
Debug Token:
[Replace this text with the debug token provided from running pihole -d (or running the debug script through the web interface]
I am not sure how to do this but I thought the debug log is auto uploaded
Thank you
Okay, have you restarted/reconnected the devices in your network after the change in your router? Otherwise, they will not have been informed about the new networking configuration.
Can you show us a screenshot of the page in your router where you put in the settings? Maybe it didn't accept it or doesn't use it. Is there also a DHCP page somewhere? Can you enter the Pi-hole's IP address here as DNS server as well?
Your debug log shows that the Pi-Hole host does not have an active IP address. You have Pi-Hole configured to listen on 192.168.1.10, but none of the other clients on the network can find the Pi-Hole at that IP. Pi-Hole is working, but it can only receive requests from localhost without an active IP address.
*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.
[✗] No IPv6 address(es) found on the eth0 interface.
[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
[✓] demo.vertexinfo.in is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve demo.vertexinfo.in via Pi-hole (192.168.1.10)
[✓] doubleclick.com is 172.217.164.206 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Setup variables
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.1.10/24
Your IP is on the wireless interface, and you have Pi-Hole configured on the ethernet interface. You also have reserved the .10 IP for the ethernet interface, not the wlan interface.
You will need to choose one interface or the other, put that IP on the chosen interface, then run pihole -r and select reconfigure, then select the correct IP and interface for Pi-Hole.