This works, but the problem is that all the nodes will end up in the same default datasource, so their Cluster information is lost, which is not so nice for multi-cluster environments.
I haven't tried yet, but a possible workaround for this would be to create a UDP channel for each cluster, which is not so nice if you have many of them.
My current setup is using unicast at the cluster level due to networking limitations, and all the data is getting sent to a node from each cluster. Then I contact each of those using metad to get all the data regarding that cluster.
This way the clusters will be assigned to their own data sources, and their full information will be there.
The config would look like this:
# on each node in the cluster
host = 220.127.116.11 # this is a member of the cluster, not a metad server
port = 8650
Then on the metad:
data_source "My Cluster" 18.104.22.168
For redundancy you can have multiple udp_send_channel entries and multiple IPs listed in the data_source. I personally use two for each cluster.
For federation I use something like this:
data_source "My Grid" 22.214.171.124:8651
This is valid only if you have a metad listening on port 8651 there.