DFS Namespace - The namespace cannot be queried

Question

Cloud_Geek_82 901

Hi guys,

There is a Windows Server 2012 domain controller DC1.

It has DFS namespace \domain.local\TEST

Another domain controller DC2 (Windows Server 2019) was added to the existing forest and DFS Namespace server.

After that FSMO roles were moved from DC1 to DC2.

Now on both domain controllers I get.

(There were no errors before FSMO roles migration)

DFS error

I don't see any errors in the Event Viewer on both servers.

There are also no visible signs of replication error.

Is it an indication of some problems with DNS or AD replication?

1 answer

Answer 1

Cloud_Geek_82 901

Self-resolved.

ChadB-1095 0 Reputation points

2024-04-15T18:21:24.3333333+00:00

I have the same issue. It happened when moving FSMO roles as well. Did you ever find out how it "self-resolved"?
Cloud_Geek_82 901 Reputation points

2024-04-15T19:36:10.19+00:00

Unfortunately not.
ChadB-1095 0 Reputation points

2024-04-15T19:39:59.7366667+00:00

Thanks for the follow-up. I'm looking into this right now. I see running dfsutil /pktinfo that I have a server listed as a "TargetSet" even though it's an old server that's currently not online. https://community.spiceworks.com/t/cannot-access-dfs-namespace/517393/3
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
ChadB-1095 0 Reputation points

2024-04-16T00:39:50.94+00:00

Good news, we fixed it! It turns out that the DC with the FSMO roles also needs to be a Namespace Server. If it's not, you will get "namespace cannot be queried the specified domain either does not exist or cannot be contacted" error. To fix this, we moved the FSMO roles back to the DC which was also a Namespace Server. Waited about 20 min. and then the error was gone and the namespace was accessible. We then added the new DC as a Namespace server. We are going to give it a couple of days before moving the FSMO roles to the new server.