portillosjohn
asked on
DFS namespace and domain name
We are trying to implement DFS and we have run into some issues and unfortunately our domain name is the same as our external website. Is there a way to change the DFS name to something else? Our domain name is abc.com our external website is abc.com and the dfs is abc.com. Can we change the DFS namespace to XYZ.com?
ASKER
Hi Michael,
Can you clarify what you mean? If i use standalone DFS it would work? Does that mean 1 server?
Can you clarify what you mean? If i use standalone DFS it would work? Does that mean 1 server?
Hello,
Here you go, this should help clarify :)
http://msdn.microsoft.com/fr-fr/library/cc780773%28v=ws.10%29.aspx
Regards
Michael
Here you go, this should help clarify :)
http://msdn.microsoft.com/fr-fr/library/cc780773%28v=ws.10%29.aspx
Regards
Michael
ASKER
Thanks a bunch. Is there a way to work around my problem besides changing the domain name if I still want to use DFS?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Is your DNS split-brained (external DNS hosting)?
Internal DNS (and DFS) only needs \\domain.TLD\ to work properly. Internally, your website should not be accessible using http://domain.TLD, otherwise you would have other AD problems since all of your domain controllers should be the only hosts available using domain.TLD. Internally, you should only be accessing the external site as http://www.domain.TLD, so AD and DFS should work just fine.
Things get a little more complicated if you're doing VPN from outside, but one step at at time.
Internal DNS (and DFS) only needs \\domain.TLD\ to work properly. Internally, your website should not be accessible using http://domain.TLD, otherwise you would have other AD problems since all of your domain controllers should be the only hosts available using domain.TLD. Internally, you should only be accessing the external site as http://www.domain.TLD, so AD and DFS should work just fine.
Things get a little more complicated if you're doing VPN from outside, but one step at at time.
ASKER
We have our own dns servers internally. You are correct about the resolution of the domain. I guess the problem is that on certain work stations the dfs resolves to our exchange server/webmail server instead of the DFS.
Do you have more than the IPs of domain controllers in the list of HOST records for your domain? If you do an nslookup on the domain name, are the Exchange (webmail) server IPs listed?
nslookup domain.tld
Domain based DFS makes use of the domain name, this cannot be changed.
You use a standalone DFS, however you will not be able to add any other namespace / folder paths from other servers to the DFS root.
Regards
Michael