DNS_PROBE_FINISHED_BAD_CONFIG - Google Clodu

Help
1

Expected Behaviour:

PiHole should be resolving DNS queries

Actual Behaviour:

getting DNS_PROBE_FINISHED_BAD_CONFIG

Debug Token:

redacted by staff
3

Jun 17 00:21:22 dnsmasq[13601]: reply github.map.fastly.net is 151.101.0.133

from your log file show pi-hole is resolving as expected

there is a chance the local DNS cache is seen as poisoned and can be cleared using ipconfig /all from windows command prompt

4

Hi @technicalpyro! Thanks for replying.

I have configured my router to use the Pi Hole DNS server and flushed the DNS Cache on my PC (dont know how that will affect other devices dns configs). But it's still not resolving names on other devices.

I found this from the log:

[✓] IPv4 address(es) bound to the ens4 interface:
   10.*.*.*/* 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)
   35.*.*.*/* 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)

[✓] IPv6 address(es) bound to the ens4 interface:
   *::*::*:: 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)

   ^ Please note that you may have more than one IP address listed.
   As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.

   The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.

[i] Default IPv4 gateway: 10.*.*.*
   * Pinging 10.*.*.*...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
5

to fix those errors recommended course of action is to run pihole -r and select reconfigure

6

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.