I added 2 Google nest devices to have reserved DHCP addresses like follows:
d8:8c:79:5f:##:##,192.168.0.79,nest-audio,infinite
d8:8c:79:83:##:##,192.168.0.72,nest-audio2,infinite
One works, second one seems a bit odd... 
I tried deleting one and/or both, restarting Pi-hole and devices few times ending up with same result.
Lease expired 54 years ago seems a bit strange.
At the same time I noticed that some devices are missing Client ID's.
2024 - 54 = 1970 which is the beginning of time so I'm not actually overly confused. I agree this looks like a parsing issue:
Could you show us the content of your leases file in /etc/pihole? You are free to shuffle the hex bits and obfuscate the hostnames but please ensure the overall structure of the file stays intact.
Here's a snip from dhcp.leases
1706323423 ac:67:84:37:##:## 192.168.0.100 Google-Nest-Mini *
0 d8:8c:79:83:##:## 192.168.0.72 nest-audio2 *
1706320219 d8:8c:79:5f:##:## 192.168.0.79 nest-audio *
The nest-audio2 row seems a bit odd...
Edit, few more rows:
1706322027 b0:4a:39:13:##:## 192.168.0.89 [device] 01:b0:4a:39:13:##:##
1706313177 84:b8:b8:a3:##:## 192.168.0.70 [device] 01:84:b8:b8:a3:##:##
1706312903 18:4e:cb:18:##:## 192.168.0.109 [device] 01:18:4e:cb:18:##:##
1706312654 ac:ca:54:01:##:## 192.168.0.88 [device] *
1706312653 78:8b:2a:18:##:## 192.168.0.104 [device] 01:78:8b:2a:18:##:##
1706317232 ac:f1:08:57:##:## 192.168.0.81 [device] 01:ac:f1:08:57:##:##
1706336362 68:07:0a:84:##:## 192.168.0.108 [device] 01:68:07:0a:84:##:##
1706312729 fc:34:97:6e:##:## 192.168.0.103 [device] 01:fc:34:97:6e:##:##
Note:
Device 192.168.0.88 is manually added too, DNS names replaced with [device].
@DL6ER
Can I manually add Epoch timestamp ~20hrs from now to the row and see if that solves the issue?
Stop Pihole and run "sudo systemctl stop pihole-FTL.service" before edit?
Issue solved by manually adding Epoch timestamp where missing.
Changed:
0 d8:8c:79:83:##:## 192.168.0.72 nest-audio2 *
to
1706320219 d8:8c:79:83:##:## 192.168.0.72 nest-audio2 *
And it works now.
I see you have already found a workaround. However, the correct fix is
which simply adds an exception that 0 really means a never expiring lease.
Thanks you again for your report!
