I've got a bunch of physical sites: East-1, East-2, Central, West-1 and West-2, they all have domain controllers and have servers that provide DFS services.
Other sites Near-East-1, Near-East2, Near-West-1, Near-West2 have domain controllers but no servers that provide DFS services.
Central is our main data center.
Each site is defined in AD Sites & Services, and a Site Link from each site to Central exists and has a cost of 100 so it winds up being a kind of hub & spoke configuration with Central being the hub.
Users in the sites that have DFS servers are connecting to those on-site servers, that's not an issue. But users in nearby sites are connecting to the DFS server in Central instead of the one nearby. A user in Near-East-1 should connect to East-1 but are instead connecting to Central. I could create a Site Link from Near-East-1 to East-1 with a lower cost than the Near-East-1 to Central link and that should fix that problem but lets say there is a different DFS folder in East-2 that needs to be accessed. I'd need to create another Site Link from Near-East-1 to East-2 with... what cost? The same as the one to East-1?
And what if I add more sites in one of the areas? Would I need to create Site Links from each of those new sites to the sites that have the DFS servers? This can get real messy real fast.
What would be the best way to configure this to ensure that users connect to the actual closest DFS server?