You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed a TODO item in the code for DNS service discovery, and I've made some progress on it. It's still a work in progress. However, I'm also wondering if it's necessary to return the port based on the protocol dns.rs
The text was updated successfully, but these errors were encountered:
There are many ways to do DNS based discovery. Beside using the A/AAAA record directly, which doesn't carry any information about ports, others use SRV and TXT DNS record which can carry port information.
Another thing is that our service discovery traits are public. You can use and share your implementation of DNS service discovery (as a "plugin") with 3rd party without contributing to our code base.
I noticed a TODO item in the code for DNS service discovery, and I've made some progress on it. It's still a work in progress. However, I'm also wondering if it's necessary to return the port based on the protocol
dns.rs
The text was updated successfully, but these errors were encountered: