First off let me apologize for asking this question again, but I have read through all the similar questions/answers and none seem to meet my needs.
I have an issue where the DFS root namespace shares are not showing up when connecting to the UNC path (i.e.\\FQDN\share). We are trying to use domain based DFS in server 2008 mode. We have multiple sites within our organization throughout the world and would like the users to be able to type in the UNC path\\FQDN and then be able to see the root name space there.
From what I can tell, this works just fine from a site that has the namespace server for the root name. Once you are not in a location that has a namespace server, you only get the standard "netlogon" and "sysvol" folders, no other folders. I am attributing this to the fact that at each site we have at a minimum of one domain controller and the domain controller is responding the the request when typing in the UNC path\\FQDN to a run command. If I type this same command into a run command at a site that has the namespace server, it returns the standard "netlogon" and "sysvol" folders along with all the name space root folders.
So onto my question. What is the best way to resolve this issue for my users? Should I install namspace servers at each site? Is there a better standard practice that will alleviate this issue?
I have read and re-read all the documentation that Microsoft has put out and there isn't anything about this that I have found.
I appreciate any responses as this is driving me crazy and I'm not sure that I want to put namespace servers all over the world and then have the other issue of deciding on the optimization choices of consistency or scalability.
Thanks in advance.