Solved

Internal DNS Propragaton DHCP Scope

Posted on 2014-12-05
4
157 Views
Last Modified: 2014-12-06
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)

Server Naming:
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 102.1.1.1
Mail.newdomain.com has reverse DNS setup at 102.1.1.2

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.local 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.local 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.
0
Comment
Question by:abustraan
  • 2
  • 2
4 Comments
 
LVL 39

Accepted Solution

by:
footech earned 500 total points
Comment Utility
If both DHCP servers are reachable when the client computer sends a DHCP request, whichever one responds first (faster) will be the one the client gets its info from.

When you try to lookup just a NetBIOS name, it's all about which DNS suffixes you have configured.  Those suffixes will be appended to the name to create the DNS queries.
0
 

Author Comment

by:abustraan
Comment Utility
Thanks for the prompt response.

Hummm. Is there any way to set a preference as to which DHCP server is available to which domain? I have an IP helper for DHCP configured in my routing switch for DC1.existingdomain.local.

After hours, should I try and remove the IP Helper and see if that helps?

As far as the DNS suffixes I've added both newdomain.local (first) and existingdomain.local (second)
0
 

Author Comment

by:abustraan
Comment Utility
Okay. New wrinkle...

went into the TCP IP Settings and manually specified NewDC1 IP address as DNS Server. When I do nslookup it shows NEWDC1.newdomain.local as DNS server. However, when I use nslookup to resolve NEWExch it shows results from root forwarders and none of the results are the right IP.
0
 
LVL 39

Expert Comment

by:footech
Comment Utility
I have no experience with IP helpers.

In nslookup, run the following so you can see exactly what queries are being made.
set debug
If results are coming from root hints or forwarders, then the record must not be present in the local DNS.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

6 Experts available now in Live!

Get 1:1 Help Now