Temporary failure in name resolution, but only for certain devices

Help
1

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

I'm using pi-hole as my DHCP and DNS server for my network.
I'm running pi-hole on a Raspberry Pi 3 with raspbian buster.
I also have a number of servers that I am monitoring via Uptime Kuma.
Most of the devices behave as expected.

The TuringPi devices have static IPs assigned to them via DHCP.

Expected Behaviour:

The TuringPi devices to consistently respond to pings to the FQDN.

Actual Behaviour:

Randomly (apparently) Uptime Kuma reports that
ping: turingpi-rk1.lan: Name does not resolve
along with the other devices attached to the Turing Pi (but only those devices).

The failures are sporadic; I've had everything working fine for days, only to get failures separated by an hour or so.

Debug Token:

https://tricorder.pi-hole.net/XfKdOTuu/

2

Assuming that those pings where issued from a separate machine running Uptime Kuma, please share the results of the following commands as run from that very machine:

nslookup pi.hole

nslookup flurry.com 192.168.0.253

Also, note that ping is using other means to resolve domains than just DNS (making it inadequate to analyse DNS issues).
If possible, you probably should configure your Uptime Kuma to ping by IP rather than name, to avoid a system that actually is up and running to be reported as down only because its name is unresolvable.

3

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