<div>
DFS doesn't work like you think<br />
<br />
If you want to put DFS name space on single DC, it will not get replicated to other domain controllers<br />
<br />
DFS configuration do get stored in AD, however it not mean that DFS name space is automatically created on other domain controllers<br />
You will not be able to access DFS name space if DC holding it goes down<br />
For that you need to add all DCs as DFS name space servers in DFS, after that DFS name space shared folders will get created on those DC servers<br />
<br />
Now it make sense that one DC gets down, other DC will take over to DFS name space (redundancy)<br />
<br />
Major considerations if you want to add DFS name space on DC server:<br />
If you want to add DFS name space on DC, its OK as long as you add all DC servers in same AD site as DFS name space servers<br />
Other wise you will get DFS access issues if dfs name space is installed on few DC servers and there are other DC servers without DFS name space component installed<br />
Because DFS name space will be accessed as \\domain.com\dfsroot<br />
In this case, domain.com if resolved to non DFS DC server, you won't access DFS name space, this happens because of DNS random behavior<br />
<br />
OR<br />
U could install DFS name space on multiple domain member servers instaed of DC server
</div>


<div>
Mahesh, <br />
<br />
I have not been able to find any articles describing the issue that DFS-N and the DC's. Do you have a KB available? <br />
<br />
Additionally what's the best way to build the DFS name space in a fault tolerant way with member servers? Any article that's explains the steps? <br />
<br />
Thanks.
</div>


<div>
I have not said there are any issues, if you read my comment carefully, I said that are considerations<br />
<br />
If you aware how DNS name resolution and round robin works, you would come to know the issue<br />
<br />
Ex:<br />
contoso.com is my AD domain name with 4 DCs in same active directory site<br />
Now if you run nslookup for contoso.com multiple times, each time it will resolve IP addresses of all 4 DCs by varying there order due to DNS round robin<br />
Guess what will happen if you have dfs-n role installed on only two servers?<br />
you will access dfs name space by entering \\contoso.com\dfsnamespace<wbr /> or \\contoso\dfsnamespace<br />
if contoso resolves to DC which do not have dfs-n installed, you won't be able to access dfs-n<br />
now client will not go to dns immediately until failed record TTL get expired, next time if client try to access contoso and if it resolves to DC server which have dfs-n role installed, it will get access<br />
<br />
I have experienced this behavior and hence you need to install dfs-n on all domain controllers<br />
I don't have KB for this, infact this is straight forward behavior and don't see any need for KB<br />
<br />
For your 2nd question:<br />
You should deploy dfs-n on at least two member servers to get fault tolerance and redundancy<br />
if one server gone down<br />
if one server fails, still users will be able to access data due to referrals<br />
you will gets lots of documents / bring online
</div>


<div>
For what it is worth, I have always been a believe is let's DC be DC's and that's it and install File and Print services on other servers... I assume you will be using DFS to support your company file shares?
</div>


<div>
<div class="content wysiwyg-content">
Hi, <br />
<br />
We are planning to deploy DFS-N and we are looking for suggestion in the deployment. Basically I would like to deploy Domain Based DFS-N &nbsp;and I was considering using one of the domain controllers (DC01)( to the deploy and configure the DFS Name Space. My understanding is that the others DC02, DC03 will provide the fault tolerance for the DFS-N, so if DC01 is shutdown DC02 and DC03 will be able to provide the DFS-N to the users. <br />
<br />
If DC01 (which is the DC that I've used to install DFS-N and create the NameSpace) is shutdown I will not be able to make new changes on the namespace but the current namespace itself will be available to the users, correct? The DCs are a mixed between 2012/R2 and 2008/R2. The DFL and FFL is windows 2008 <br />
<br />
Are there any specific reasons not to use the DCs to deploy DFS-N? <br />
<br />
Anything else we should be aware of when facing the deployment and configuration?
</div>
</div>


Hi, 

We are planning to deploy DFS-N and we are looking for suggestion in the deployment. Basically I would like to deploy Domain Based DFS-N  and I was considering using one of the domain controllers (DC01)( to the deploy and configure the DFS Name Space. My understanding is that the others DC02, DC03 will provide the fault tolerance for the DFS-N, so if DC01 is shutdown DC02 and DC03 will be able to provide the DFS-N to the users. 

If DC01 (which is the DC that I've used to install DFS-N and create the NameSpace) is shutdown I will not be able to make new changes on the namespace but the current namespace itself will be available to the users, correct? The DCs are a mixed between 2012/R2 and 2008/R2. The DFL and FFL is windows 2008 

Are there any specific reasons not to use the DCs to deploy DFS-N? 

Anything else we should be aware of when facing the deployment and configuration?

Domain Based DFS-N - Fault tolerance

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.