GPO Software Deployment using DFS via FQDN fails?

[pete]

I have a minimal DFS namespace (4 links, one replicated folder).

 

If I assign an application via \\domainshortname\namespace\applications\path\whatever.msi it installs.

 

If I assign an application via \\fqdn\namespace\applications\path\whatever.msi it complains it can't find the application.

 

If I manually browse to the msi using the fqdn I can install the app fine.

 

Profiles and scripts run in the user context (plus redirected start menus) from \\fqdn\namespace\profiles works fine.

 

I've enabled the DFSDnsConfig key on both DFS servers and I've rebuilt the namespace ensuring I use FQDN everywhere. Software still doesn't install via GPOs.

 

DNS works fine and the permissions for the application install point are set on the server hosting the applications, so that hasn't changed for months.

 

This is annoying - any ideas? Does DFS have a means of enabling verbose "computer X requested $foo?" logging?

[pete]

And the answer was a DNS server was holding onto records for a demoted DC that it should have cleared out when the other dns servers cleared it.

 

Cleaned that up manually and it magically starts working.