https://tools.ietf.org/html/rfc6762#section-10.2
Queriers receiving a Multicast DNS response with a TTL of zero SHOULD
NOT immediately delete the record from the cache, but instead record
a TTL of 1 and then delete the record one second later. In the case
of multiple Multicast DNS responders on the network described in
Section 6.6 above, if one of the responders shuts down and
incorrectly sends goodbye packets for its records, it gives the other
cooperating responders one second to send out their own response to
"rescue" the records before they expire and are deleted.
The RFC says it should be scheduled 1s in the future. Currently it happens right after we finish processing the answers in handle_response
We should instead set the ttl to 1s like we do with maybe_entry.reset_ttl(record)
https://tools.ietf.org/html/rfc6762#section-10.2
The RFC says it should be scheduled 1s in the future. Currently it happens right after we finish processing the answers in
handle_responseWe should instead set the ttl to 1s like we do with
maybe_entry.reset_ttl(record)