compinfo
asked on
Network Interface Card (NIC) teaming on DNS, DHCP, AD, and Hyper-V Server
Hi,
I have a small network and run DNS on the same box as hyper-v. I have 2 available NIC cards. I'd like to use one specifically for hyper-v's. Before I do it, should I make the DNS entry in NIC #2 (the one to be used for Hyper-v) the IP address of NIC#1, which will be the DNS server NIC? Should I use "teaming" of NICs?
Thanks, Compinfo
I have a small network and run DNS on the same box as hyper-v. I have 2 available NIC cards. I'd like to use one specifically for hyper-v's. Before I do it, should I make the DNS entry in NIC #2 (the one to be used for Hyper-v) the IP address of NIC#1, which will be the DNS server NIC? Should I use "teaming" of NICs?
Thanks, Compinfo
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I did not do teaming. NIC #1 is configured as the main NIC with it's own IP address as the DNS too. I tried setting up NIC #2 with a different static IP with NO DNS entry, and it gave me this warning:
"The DNS server list is empty. The local IP address will be configured as the primary DNS server address b/c MS DNS server is installed on this machine".
Also, I try to ping NIC #2 both from this server and from a different client and there is no reply..... ideas?
"The DNS server list is empty. The local IP address will be configured as the primary DNS server address b/c MS DNS server is installed on this machine".
Also, I try to ping NIC #2 both from this server and from a different client and there is no reply..... ideas?
ASKER
BUT, I was allowed to choose the NIC #2 for the hyper-v server, next, I will see if it will work...
firewall on hyper v server?
you also need default gateway,dns server entry and obvieusly static IP and subnet mask (coressponding with rest of your network) if you are using static ips
you also need default gateway,dns server entry and obvieusly static IP and subnet mask (coressponding with rest of your network) if you are using static ips
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
All very good suggestions. In the end, I decided against teaming the NICs *AND* not running AD and HYPER-V on the same server (as it is not a best practice).
Thanks all!
Thanks all!
Do not setup DNS entry on NIC 2 at all just give it an IP. This will eliminate configurations with multiple DNS servers and Gateways. You will set the proper configuration in the Guest of the Hyper-V once you attach the interface. Do not use NIC teaming if all you have is 2 NIC cards in this case the traffic from Hyper-V guests will go through NIC 2 and DNS through NIC1.