Trnsfer FSMO, No Group Policy?

  • Thread starter Thread starter Chad Bechstein
  • Start date Start date
C

Chad Bechstein

I have a question about using a CNAME for a domain
controller in its BIND resource records. I successfully
transferred the fsmo roles from the main dc to our
secondary dc to find that group policy stopped working.
Once the fsmo's were moved back to the original dc,
everything was fine again. The secondary dc's resource
records use its CNAME entry instead of its fully
qualified domain name and I am wondering if that could be
what's causing the problem.

Thanks for any ideas.
 
In
Chad Bechstein said:
I have a question about using a CNAME for a domain
controller in its BIND resource records. I successfully
transferred the fsmo roles from the main dc to our
secondary dc to find that group policy stopped working.
Once the fsmo's were moved back to the original dc,
everything was fine again. The secondary dc's resource
records use its CNAME entry instead of its fully
qualified domain name and I am wondering if that could be
what's causing the problem.

Thanks for any ideas.
Click to expand...

That would be it. I've found CNAMEs cause problems, especially for domain
locator records (SRVs), except the Forest CNAME GUID (which is by default).

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top