Open evverx opened 1 month ago
I'm not sure what to do though. It makes it possible to test things like https://github.com/avahi/avahi/commit/93b14365c1c1e04efd1a890e8caa01a2a514bfd8 so from that perspective I think it's great that it's possible to send PTR RRs like that. I'm not sure it should be included in the examples though. It could be that they are copied verbatim and end up being advertised by various devices like for example https://github.com/avahi/avahi/issues/251. Those avahi bugs were fixed so it isn't that bad anymore but still.
Looking at https://github.com/troglobit/mdnsd/blob/5346604fcdeccd99f9943ac5ef887c3880480338/man/mdnsd.service.5#L72-L73 it seems that targets should go to SRV resource records.
The first two examples at https://github.com/troglobit/mdnsd?tab=readme-ov-file#service-records come with
and it leads to PTR resource records like
where
_ftp._tcp.local
points toftp.luthien.local
.The problem is that
avahi-browse
(or any other mDNS browser) can't follow those PTR resource records so those services can't be discovered using those tools. It's still possible to resolve the services directly since their SRV and TXT resource records are advertised too but there is no link between_ftp._tcp.local
andTroglobit FTP Server._ftp._tcp.local
anywhere.According to https://datatracker.ietf.org/doc/html/rfc6763#section-4.1
where
<Service>
should follow https://datatracker.ietf.org/doc/html/rfc6763#section-7