Hello,
I'm trying to figure out how to configure an AD integrated DFS Namespace on a RODC
(2008R2) so that if a wan link is down the users in a branch site can access
that namespace server for referrals after a client reboot. At the moment I
can't get this to work. I've used this configuration successfully with regular
DCs for years, so I'm sure it's something to do with the fact I'm trying to get
this to work on an RODC.
Should this work? Or is it not possible to configure an accessible DFS Namespace on an
RODC? It strikes me that despite configuring the namespace server to run on the
RODC in the branch site that clients may not even be using it regardless of the
wan connectivity.
If the link is down clients are unable to resolve the dns name for the domain and namespace
(e.g. domain.local), I think because RODCs don't register themselves in DNS
like regular DCs. What I don't seem to understand is how exactly the client
obtains the list of namespace servers. Surely if the client has access to an
RODC it should be able to obtain the list from AD, find and then connect to the
available namespace server (that's also installed on the RODC)? I looked at
this article (here) and the client referral process involves connecting
to a domain controller to obtain a list of namespace servers, but in my case
the client gives up when it can't find \\domain.local\dfs\folder target\ despite
there being a namespace server ready to reply in the local site.
Any assistance much appreciated!
Neil