Description
Is there a mechanism to indicate to Zeroconf/AsyncZeroconf or ServiceBrowser/AsyncServiceBrowser that a cache entry might be stale, based on application level failures on connecting to advertised services?
https://datatracker.ietf.org/doc/html/rfc6762#section-10.4
The software implementing the Multicast DNS resource record cache
should provide a mechanism so that clients detecting stale rdata can
inform the cache.
When the cache receives this hint that it should reconfirm some
record, it MUST issue two or more queries for the resource record in
dispute. If no response is received within ten seconds, then, even
though its TTL may indicate that it is not yet due to expire, that
record SHOULD be promptly flushed from the cache.
So it looks like an optional feature according to the RFC, but would be nice to have (if it's not there already, I'm new to this library).