Support for mDNS in GDS

[RakshanPremsagar]

Type of Issue
[ ] Bug [ ] Enhancement [ ] Compliance [x ] Question [ ] Help wanted

Hi, I have 2 hosts. Host A and Host B.
Host A has the .net core GDS running (as it is on Linux). Also it has an LDS(mDNS enabled) .
Next, I have the HostB(Windows), which has its local discovery service running in the background, and also a prosys simulation server registered to it. I run the global discovery client here.
Using the select GDS, I connect to the GDS running on host A.

Now, the observation is that in the discovery section -> on the local machine-> I observe the prosys simulation server
on the local network-> I observe the LDS of hostA, and Prosys server(HostB)
on the global discovery-> empty

But on the global discovery, I expect it to show the above mentioned servers in the list. But it shows an empty list. Should it not show the cumulative list of all the servers?

Could you please guide me as to what am I doing wrong here?

Also, one more question is: In the tutorial video, a sample config file of a server was registered to the GDS client(server pull). And it was shown in the global discovery section. Now, is it a step to be taken when there is no LDS in the system like in Intro

Or was that step, the 2nd step in the GDS Overview

Extremely confused.. Look forward for some guidance here

[mregen]

Hi @RakshanPremsagar, the .NET GDS does not support the mDNS, although there is already a configuration flag.
So the registration in the GDS of other devices, like ProSys which may support the mDNS , is a manual step.
Hope this helps...