Internal DNS Propragaton DHCP Scope

Posted on 2014-12-05
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
Dc2.existingdomain.local (AD) (IP
Exch.existingdomain.local (Exchange 2003 SP3 CU14) (IP

NewDc1.newdomain.local (AD, DNS, WINS, DHCP) (IP
NewDc2.newdomain.local (AD, DNS) (IP
NewExch.newdomain.local (Exchange 2013 CU6) (IP has reverse DNS setup at has reverse DNS setup at

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 created and added.
a.      Alt Name:
b.      Alt Name:
c.      Alt Name:
d.      Alt Name:
e.      Alt Name:

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 autopopulate, I click next, and the wizard establishes a network connection, and it searches for the settings for 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.
Question by:abustraan
  • 2
  • 2
LVL 40

Accepted Solution

footech earned 500 total points
ID: 40483810
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.

Author Comment

ID: 40483869
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)

Author Comment

ID: 40483907
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.
LVL 40

Expert Comment

ID: 40485234
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.

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
Find out what you should include to make the best professional email signature for your organization.
In this video we show how to create a Contact 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 Recipients >> Contact ta…
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…

830 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