Device_tracker throws exceptions when ping platform can't resolve a dns name

Configuration
1

Seems like that should be a foreseeable and common situation that the integration should handle more gracefully.
The integration is throwing an exception (and filling logs with them - the problem).

This doesn’t seem to be the best way for the device_tracker/ping integration to react when a device has simply departed the LAN.
Perhaps I should instead submit this as a bug/feature issue?

Background detail: I’m using the Ping platform for a device_tracker to determine when our phones are home or not.
The home router assigns them an IP via DHCP, and resolves their names reliably.
When the phone is away, the LAN ping fails of course, and the name-resolve also fails after the lease has expired.
And HA logs an exception - lots and lots of them. To the degree that I have to disable the ping integration when we go on vacations.

2

Update: I employed the obvious workaround of statically defining the hostnames in the DHCP server by issuing them reserved addresses.
It just seems wrong to have to solve a problem by modifying an external system.
So I reiterate my suggestion that the name-resolution failure be a soft-fail, tolerated and configurable, rather than an exception-worthy event.