Windows Server 2012 Hyper-V Virtual Switch DNS Problem on DC

Hi!
Okay i have a really annoying problem.

Basically we have the following:

A HP Proliant ML350e with 2 physical nics.
The server is running Windows Server 2012. Its roles are DC, DNS, DHCP, FILE SERVER, HYPER-V.

Within Hyper-V we have a virtual machine acting as a RDS Server. We're using one nic from the host for the DC and one for the RDS vm. So within Hyper-v the vm has lets say 172.16.10.11 and if i look in the DC the virtual switch has 172.16.10.49. The Physical NIC of the DC has 172.16.10.10

The problem arises that the DC registers the Hyper-V switch in DNS so when i nslookup DC.CONTOSO.COM i get back 172.16.10.49, instead of what i should get 172.16.10.10. I can go into DNS and delete the entries made for DC pointing to 172.16.10.49 and after a ipconfig /flushdns on RDS i can nslookup DC and get the correct respons. The problem is that the .49 adress returns to dns. What is the fix for this and why am i such an idiot that can't figure this out? It would seem to be a problem with Hyper-V no?

Any pointers would greatly help me out as im going nuts here.
LVL 2
Wouter MakkinjeIT ManagerAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Wouter MakkinjeConnect With a Mentor IT ManagerAuthor Commented:
Here i solved it, I will attach an image and in this image i have highlighted a check box which needs to be unchecked in order for the adapter or hyperv switch to not show up in the hyperv host. Anyways thanks for the help.
Sk-rmklipp.PNG
0
 
Wouter MakkinjeIT ManagerAuthor Commented:
I've disabled the Hyper-V vethernet adapter in the DC host and it doesn't seem to affect the RDS server. Leaving it disabled solves the issue but what is it and why is it even there?
0
 
Cliff GaliherCommented:
Virtual switches do not get IP addresses. So something is definitely screwed up, or you described your environment wrong. You usually can't even force an IP address onto a vswitch. The system will throw an error first.

As an aside, running hyper-V on a DC (or any role really, but ESPECIALLY a DC) is very bad. hyper-V should run alone. Any other roles should be virtualized. Running a DC as a VM is perfectly acceptable. And costs nothing since you get 1+2 licensing rights with 2012. There is no reason to colocate roles like that.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Wouter MakkinjeIT ManagerAuthor Commented:
Ive attached an image of the connections.
Sk-rmklipp.PNG
0
 
Cliff GaliherCommented:
Why are you attaching this image? Without context, explanation, or a follow-up quesrion, I am not sure how to help you.
0
 
Wouter MakkinjeIT ManagerAuthor Commented:
Since the expert helping me didnt solve it but i did eventually.
0
All Courses

From novice to tech pro — start learning today.