Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Moving from a .local to .com - Domains and Trust ad.company.com is setup but uncertain of next step

$
0
0

The domain in question is currently a .Local Active Directory Domain (company.local).  In order to get external certificates to function properly, we need to roll it over to a AD.company.us.  I realize that completely hosing the Domain is one way of going about this, but from what I've read I can also create a new UPN Suffix (Domains and Trusts) domain to accomplish this.

Scenario I have:

Current Domain: company.local

New UPN Suffix in AD Domains and Trust: ad.company.us

Username: tuser

I then go look at a user account properties, I can see my new @ad.company.us UPN listed in the drop down.  I select that and jump over to the machine.  My thought process says I need to add this account to the machine, which would prompt me to do the following:

Hit the client machine, go through System Properties > Network ID > Add the User & Machine to the Domain.  Upon doing so, I receive the following error message: 

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "AD.COMPANY.US":

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.AD.COMPANY.US

Common causes of this error include the following:

- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

192.168.0.251
192.168.0.250

- One or more of the following zones do not include delegation to its child zone:

AD.COMPANY.US
COMPANY.US
US
. (the root zone)

Reading through the message tells me a couple of things.  It could be a lack of an SRV record for AD.COMPANY.US, but it states in the response that they're automatically added.  I've created an Internal Lookup Zone with AD.COMPANY.US (I'm not sure if this plays into any success/failure). 

Am I heading down the right path for making servers work with .AD.COMPANY.US?


Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>