keepsimple1

Thanks for your PR with quick response! I'll probably take a couple of days to review, but will do.

Currently `mdns-sd` does not handle reverse DNS lookups mainly because it's not normally needed for "service discovery". And, it seems the RFC only mentioned the link local addresses reverse lookups...

From your steps, looks like mdns-sd should not remove the service after step 4. It's not clear to me why: in both pcap trace files I didn't see a packet...

Sorry about my late response. Thank you for the trace file! It's really helpful. I think I found the bug and submitted a PR #350 for fixing it. Would you...

> I tried with the PR and this patch is fixing the problem. 👍 thanks for verifying! > Could you help me understand what is happening? In our case, what...

> I don't understand this explanation. The repro steps mentions publishing (`P1`), expiring (`E`), wait 5s (sorry I was not more specific about how long to wait in my initial...

This issue have been fixed. If any related problems, please feel free to reopen this issue or open a new issue. Thanks!

> Any ideas on what coudl be the cause for this intermittent problem? Since the source code that prints `Discovered device:` is not included, I cannot be sure. But it...

Thanks for the link. Indeed it seems odd. Could you also print out the `get_hostname()` and `get_fullname()` when a service info is resolved? (as internally we index addresses and TXT...

> Do you think that could be the cause? Yes. If hostname is same, the resolved addresses will be the same (or accumulated) . > some other times I still...