Add FreeBSD support using mDNSResponder/Bonjour backend

[sandronoel]

Hello! Thank you for maintaining this excellent library. I've been using zeroconf on Linux and macOS with great success, and it's been significantly more reliable than alternatives.

I'm currently trying to deploy a server application on FreeBSD 15, and I've run into compilation errors because FreeBSD isn't recognized as a supported platform. However, FreeBSD does support mDNS through the mDNSResponder package (the same Bonjour implementation used on macOS).

The fix appears to be relatively straightforward - adding target_os = "freebsd" to the conditional compilation checks that currently only check for target_vendor = "apple" or target_vendor = "pc". Specifically, in src/lib.rs:

Since FreeBSD uses the same Bonjour/mDNSResponder API as macOS, the existing BonjourEventLoop and BonjourTxtRecord implementations should work without any additional changes.

Would you be open to adding FreeBSD support? I'd be happy to test a PR. FreeBSD is commonly used for servers and networking applications, so I believe this would benefit other users as well.

Thanks again for your work on this project!

Sandro.

[windy1]

Thank you for your support, Sandro!

Yes, I would gladly accept a PR to support FreeBSD. Could you please include GitHub Actions jobs in your PR as well?

[sandronoel]

I can probably hack it. But I don’t know about GitHub actions. :/ never play around with them.

…

On Dec 22, 2025, at 8:59 PM, Walker Crouse ***@***.***> wrote: windy1 left a comment (windy1/zeroconf-rs#87) <#87 (comment)> Thank you for your support, Sandro! Yes, I would gladly accept a PR to support FreeBSD. Could you please include GitHub Actions jobs in your PR as well? — Reply to this email directly, view it on GitHub <#87 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG5SWHU2636UW5BPCMTHVWT4DC4ZFAVCNFSM6AAAAACPZFAFH6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOBVGAYDANJRGQ>. You are receiving this because you authored the thread.

[windy1]

It is fairly straightforward, you should most likely be able to get most of the way there by basing them off the existing jobs for other platforms. If you are having too much trouble with it, don't worry about it and just submit the PR without it and I can figure it out.

[sandronoel]

Awesome, I’ll do that tomorrow! regards.

…

On Dec 22, 2025, at 9:05 PM, Walker Crouse ***@***.***> wrote: windy1 left a comment (windy1/zeroconf-rs#87) <#87 (comment)> It is fairly straightforward, you should most likely be able to get most of the way there by basing them off the existing jobs for other platforms. If you are having too much trouble with it, don't worry about it and just submit the PR without it and I can figure it out. — Reply to this email directly, view it on GitHub <#87 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG5SWHU5HRHIQAOPIN3LDLL4DC5PBAVCNFSM6AAAAACPZFAFH6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOBVGAYTAMBRGI>. You are receiving this because you authored the thread.

[sandronoel]

Good morning you should receive 2 pull requests. One for zeroconf-rs and one for the bonjour-sys Both needed little modifications for the compiler to be happy. I tried it on my FreeBSD 15 and the service advertised properly.  Feel free to adjust it as you wish. You know more about your code base than I do. :) Regards. Sandro.

…

On Dec 22, 2025, at 9:05 PM, Walker Crouse ***@***.***> wrote: windy1 left a comment (windy1/zeroconf-rs#87) <#87 (comment)> It is fairly straightforward, you should most likely be able to get most of the way there by basing them off the existing jobs for other platforms. If you are having too much trouble with it, don't worry about it and just submit the PR without it and I can figure it out. — Reply to this email directly, view it on GitHub <#87 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG5SWHU5HRHIQAOPIN3LDLL4DC5PBAVCNFSM6AAAAACPZFAFH6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOBVGAYTAMBRGI>. You are receiving this because you authored the thread.