Can't get virtual server to connect to domain run off same computer

Christopher Gay
Christopher Gay used Ask the Experts™
on
I have a Windows 2012 server that I plan on taking over for our old Server 2003 R2 server. I have installed the DCHP and DNS roles on the new machine, but currently have the DCHP disabled since the old server is currently working as both a DCHP and DNS server for the machines out on our collection floor. I have successfully promoted the new machine to DNS controller of a new domain instead of using the previous .local we were running.

Using Hyper-V, I installed a new version of Server 2012 which I plan on running our SQL Server 2008. I can get the virtual server to see the .local network when I leave everything dynamic on the setup. Once I change the DNS server to point at the new machine instead of the old one I am able to ping the IP address, but when I try to attach the virtual machine to the new DNS server I get the error: "An Active Directory Domain Controller (AD DC) for the domain ***.com could not be contacted.

Please see the attached screen shot of the error.
Error.png
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2016

Commented:
guessing that you changed the domain name in the new server setup so you will have to change the network adapter dns setting to point to the NEW server.
Christopher GayIT Operations Manager

Author

Commented:
The virtual adapter on the physical server shows the right domain, but when I log into the virtual server it only show WORKGROUP. I have all adapters pointing to the new domain server, but the same error keeps appearing.
Senior Solutions Architect
Commented:
If nbocollections.com is your new domain then you need to point your workgroup/hyper-v machine to that DNS server too.

Basically, you're not able to add this machine to the domain because you cannot resolve the DNS records.

Test it manually by running: nslookup nbocollections.com

Just curious though, are you planning a full domain migration or is this for test only?
Using a .local address in private DNS is the preferred option over a .com address.
If your internal DNS zone and external zones are the same name then you will probably run into a few hickups and might need to setup a split DNS configuration to ensure that internal and external name resolution works correctly.

Have a read through the following RFC about non-routable top level domain names(TLD)
http://www.faqs.org/rfcs/rfc2606.html
Christopher GayIT Operations Manager

Author

Commented:
It appears that since our .com website is hosted remotely using a .com for our internal DNS zone causes an issue with name resolution.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial