Multiple Network Cards showing up in DNS

I have a server with 8 NIC's and the server is also the DNS server.  Two of the NIC's are connected to a SAN storage and installed on a x.x.6.x network and the rest of the network cards are setup on a x.x.7.x network.  One of the NIC's is set as x.x.7.30 and that is the DNS server Primary IP, and the other NIC's are setup for Hyper-V dedicated connections.

My problem is that in DNS the server (server01) is showing up in DNS with all the IP address even the x.x.6.x network so if you ping server01 sometimes you get back x.x.6.x.  On all the network cards except the x.x.7.30 i turned off Register this connection addresses in DNS.  So the only connection that should be registered in DNS in the one NIC but they all still appear.  I've deleted them from DNS and Reload the Zone and the come back.

How do I limit only the priomary NIC to showup in DNS
itsadmin1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Darius GhassemCommented:
Here is a hotfix for the issue.

http://support.microsoft.com/kb/975808/EN-US

For best practices you shouldn't run DNS on the Hyper-v Host computer.
0
itsadmin1Author Commented:
Reading this article looks like it is for a NIC with multiple IP's on a single NIC and doesn't say anything about multiple NIC's with a single IP on each.  Should it work for the Multiple NIC's also it says a reboot is needed any idea how to prevent the reboot and still have the fix applied and running?

The DNS server is on the standalone OS that machine also has two VM's on it.

Thank you very much,

Ryan
0
itsadmin1Author Commented:
Sorry after reading your post again are you saying that DNS shouldn't even be on the HOST OS?  It is not part of the Hyper-V OS's.  The machine is a beast with nothing else running on the HOST OS but AD/DNS/DHCP/Hyper-V.  Mem usage and CPU usage are so low.  The Hyper-V machines are very small as well with very little I/O.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Darius GhassemCommented:
The Host Server Hyper-v shouldn't have any service installed on it except Hyper-v. AD, DNS, DHCP, and etc is a no no on a Hyper-V server Host. Now in the VM (Guests) you can have these services without any issues.

http://technet.microsoft.com/en-us/library/cc759481(WS.10).aspx

http://technet.microsoft.com/en-us/library/cc759481(WS.10).aspx
0
itsadmin1Author Commented:
Thank you for the update - I did that becasue of Dell's recommendation for the the Hyper-V Images in combination with the SAN storage where the Hyper-V images reside.
0
itsadmin1Author Commented:
Also how would the HOST OS boot if no AD was found?
0
Darius GhassemCommented:
The Host OS should be in a workgroup unless you have a physical box installed with AD.
0
itsadmin1Author Commented:
OK - Good point didn't think about the workgroup side - So still having the issue with all the network cards reporting back to DNS even though they are not selected to report back to DNS.
0
Darius GhassemCommented:
You should remove the DNS servers out of the DNS settings in the TCP\IP properties.
0
itsadmin1Author Commented:
Thanks for the suggestion - Removed the DNS server IP's and they still show up in DNS.

Does it have to do with the fact that the extra NIC's are on the same hardware as the DNS server?  Can I tell the DNS server to not configure those NIC's?
0
itsadmin1Author Commented:
I've found the Listen for DNS requests properties but I'm afraid if I limit the listen on the following IP address to just the one NIC that a computer might not connect becasue it is pulling a different IP via DNS

SO:

Server name svr01

DNS IP x.x.7.30
NIC 2 x.x.6.10
NIC 3 x.x.6.11
NIC 4 x.x.7.35
NIC 5 x.x.7.37
NIC 6 x.x.7.39

in NDS svr01 records so up for everything if the x.x.6.x network which is going to a SAN.  I've removed the DNS settings from the NIC properties but a message is displayed stating that DNS will use the local IP becasue the DNS service is installed.

If I limit DNS request listening to just x.x.7.30 and DNS tells another comuter to use x.x.7.35 then the DNS service wont respond because it's not coming from x.x.7.30
0
Darius GhassemCommented:
On your host you shouldn't have DNS first off. Second you should only have 1 interface listening on DNS since you can only have one name per machine.
0
Darius GhassemCommented:
What computer? You should be able to connect to the VMs fine because they are defined within the VM on the Host. You are only going to be able to connect to the host by name which is the way it should be.
0
itsadmin1Author Commented:
OK i agree with you on the host thing and after you mentioned put the base OS in a workgroup and the others part of the domain I can see that but put all that aside and just look at three of the NIC's

svr01 with just three NIC's no Hyper-V

NIC 1 Primary NIC with an IP of x.x.7.30
NIC 2 Primary SAN with an IP of x.x.6.10
NIC 3 Backup SAN with an IP of x.x.6.11

If the company network is a x.x.7.x network but DNS shows three entries for svr01 (x.x.7.30, x.x.6.10, and x.x.6.11) then if a computer trys to access svr01 which IP will it use?

I've attached a screen shot that shows the issue that I think I have.  When I ping from svr01 to an IP address that is unreachable it trys different network cards and I can't help to think that behind the screens problems aren't going on.
JGMSDNS.JPG
0
Darius GhassemCommented:
You need to make sure that the DNS service only listens to the primary NIC card. If DNS has all IPs then it could choose any of the 3.

Make sure in your Binding order under Advance Menu in your Network Connections that your Primary NIC is listed first.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.