I’ve created new Forest, Domain, DNS, AD, to facilitate a change in Company name, to migrate from 2003 to 2012 and exchange 2007 to 2013.
For clarity here’s my naming convention:
existingdomain.local (2003 Server)
newdomain.local (2012 Server)
Dc1.existingdomain.local (AD, DNS, WINS, DHCP) (IP 192.168.1.100)
Dc2.existingdomain.local (AD) (IP 192.168.1.101)
Exch.existingdomain.local (Exchange 2003 SP3 CU14) (IP 192.168.1.102)
NewDc1.newdomain.local (AD, DNS, WINS, DHCP) (IP 192.168.1.200)
NewDc2.newdomain.local (AD, DNS) (IP 192.168.1.201)
NewExch.newdomain.local (Exchange 2013 CU6) (IP 192.168.1.202)
Mail.existingdomain.com has reverse DNS setup at 220.127.116.11
Mail.newdomain.com has reverse DNS setup at 18.104.22.168
1. I’ve created the two-way trust between the domains.
2. I’ve added secondary zones for each domains DNS on each server.
3. I’ve exported the DHCP from 2003 to 2012
a. Updated DHCP.newdomain.local to reflect the new servers.
4. I've also used the ADMT V3.2 tool to migrate the users/passwords/groups between existingdomain.local to newdomain.local
5. Mailboxes.newdomain.local created.
6. SSL Cert for newdomain.com created and added.
a. Alt Name: mail.newdomain.com
b. Alt Name: www.mail.newdomain.com
c. Alt Name: autodiscover.newdomain.com
d. Alt Name: newdomain.com
e. Alt Name: lkexch.newdomain.com
Now my issue is this:
I took a new computer, added it to the newdomain.local added myuser.newdomain.local to the local admin group and logged into the computer. Successfully joined the domain, and added to AD.
1. Opened Outlook, and while the "Your name" and email address myuser.newdomain.com autopopulate, I click next, and the wizard establishes a network connection, and it searches for the settings for myuser.newdomain.com for a considerable amount of time, and says the server can not be contacted.
From the newcomputer.newdomain.loca
l if I do an nslookup, it's using the DNS.existingdomain.local server to resolve.
It is also using DHCP.exisitingdomain.local
to obtain its DHCP scope which defines its DNS Server.
How can I force newcomputer.newdomain.loca
l to use DHCP.newdomain.local to get DNS from newdomain.local
Additionally at the client computer, if I do an nslookup for NewExch it will not resolve, but NewExch.newdomain.local. However, at the server DC1.existingdomain.local it will resolve.