AD DNS issue, need GPO to correct

  • Thread starter Thread starter Mike Huff
  • Start date Start date
M

Mike Huff

I am in the process of migrating workstations from an NT domain to a 2003
Active Directory. User accounts and groups were already in the AD.

My AD is called "abc.net"

When I migrate my workstations into the AD, they are assuming the FQDN name
of machinename.abc.net.

However the DNS folks have it set up to where only the AD Domain Controllers
get the DNS suffix of abc.net. All other machines are set by DHCP scope/IP
Address to have a DNS suffix that is site specific. Example, machine at
Richmond site would be machinename.ri.na.cba.com and machine in London would
be machinename.lo.eu.cba.com.

So DNS is doing its job, and keeping the right DNS suffix for the
workstations, but AD is assuming that any machine in it, is
machinename.abc.net. This is keeping me from right clicking a machine in
ADUC and managing it, and causing issues in a few other utilities as well.

I need a GPO that will resolve this issue so the AD and ADUC know the
correct FQDN of a machine. I tried setting the Computer
Configuration\Administrative Templates\Netowrk\DNS Client Primary DNS Suffix
GPO, but it did not seem to work.

Any suggestions?
 
Is the not a way to tell ADUC for domain abc.net, to on a certain OU assume
that machines have the FQDN of machinename.cba.ri.com?

That is my real issue, because that is the way DNS is set up, but I cannot
right click a machone in ADUC and say manage, because it is looking for
machinename.abc.net.
_________________________________________________________
 
Back
Top