DFS Namespace targets not showing up on clients

Hello,

I decommed a namespace server tonight, having added another.

I only have two sites, a main site and a DR site, one namespace server per-site.  I am testing on clients that are on the main site.  I believe both should be listed, even though the other namespace server is out of the site.  Although clients can use the DFS UNC path, the only target that's listed is the actual UNC path to the resource... no way to make alternate site's namespace server the target.

I see in adsiedit.msc that it is listed under dfs-configuration remoteServerName attribute lists the UNC path to both namespace servers.

Note that I ran through all five checks listed on this page without issue (other than my SANs not support RPC). For future reference, those tests would be:

DFSDIAG /TestDCs

DFSDiag /TestSites /DFSPath:\\Contoso.com\Namespace2 /Recurse /Full

DFSDiag /TestDFSConfig /DFSRoot:\\Contoso.com\MyNamespace

DFSDiag /TestDFSIntegrity /DFSRoot:\\Contoso.com\MyNamespace /Recurse /Full

DFSDiag /TestReferral /DFSPath:\\Contoso.com\MyNamespace

I'm not sure how to further troubleshoot the issue, and, in fact, am not sure if it's even an issue.

Please let me know any other ideas.

Thanks,

Matt