[Last Call] Learn how to a build a cloud-first strategyRegister Now


2003 server, multiple NICs, prevent DNS entries for specific NICs?

Posted on 2007-07-27
Medium Priority
Last Modified: 2013-11-09

I have 2 2003 std servers with multiple HP NICs installed.  The configuration established sent the onboard NIC to the user's network while the other two NICs went to completely separate subnets for the sole purpose of iSCSI.   Using the MSoft iSCSI initiator I have configured failover between the two iSCSI NICS that resolve on said separate subnets and it works beautifully - hops across with no service interruptions.

user's subnet is 192.168.0.x
iSCSI 1 subnet is
iSCSI 2 subnet is
All the subnets are electrically isolated save for the 2003 servers in the middle.

So far so good.  However, I am experiencing a problem on the user's subnet as follows:
The only items on the iSCSI subnets are iSCSI devices, so users have no need to access them for any purpose.  Recently we noticed some users experiencing what seemed to be random slowdowns for network activities.  A trace shows that the NIC IP addresses for the iSCSI interfaces are being pushed to clients via AD DNS.  

I subsequently removed the "update dns" option from each iSCSI NIC and manually removed the 3.x and 4.x entries in the DNS servers but 20 minutes later they are back and messing with client PCs.

Apparently I have overlooked some aspect of this - how can I prevent those two iSCSI interface NICs from being handed out in DNS requests, short of manually entering the correct subnet server IP address ( in lmhosts?

Seems like I should be able to at least prevent DNS entries on an as-needed basis.  I think that is all it would take really.

Thank you,
Question by:miroka
  • 2

Accepted Solution

chris_watson earned 750 total points
ID: 19592899
A simple solution woule be not to specify a DNS server for the Iscsi nic's. if the NIC doesnt have a dns server listed it cant register itself.
One more thing in your network connections folder, click advanced, advanced settings and make sure that the iscsi nics arent on the top of the list and make sure your actual LAN connection is on the top. hope this helps.

Author Comment

ID: 19676700
Hi guys - sorry for the delay.  Got knocked out sick and this is 1st day functional again.

Re-arranging the NIC list to ensure the actual LAN connections were on top seems to have finally resolved the issue.  Between the original post of my question and now I did find and remove the option for the NIC to include itself in the DNS lists overall.  However, the issue was not resolved until I changed the list order and rebooted one final time.

Thank you,

Expert Comment

ID: 19680483
cool im glad it worked!!!

Featured Post

New Tabletop Appliances Blow Competitors Away!

WatchGuard’s new T15, T35 and T55 tabletop UTMs provide the highest-performing security inspection in their class, allowing users at small offices, home offices and distributed enterprises to experience blazing-fast Internet speeds without sacrificing enterprise-grade security.

Question has a verified solution.

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

BIND is the most widely used Name Server. A Name Server is the one that translates a site name to it's IP address. There is a new bug in BIND (https://kb.isc.org/article/AA-01272), affecting all versions of BIND 9 from BIND 9.1.0 (inclusive) thro…
#Citrix #Netscaler #MSSQL #Load Balance
Loops Section Overview
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…
Suggested Courses
Course of the Month17 days, 21 hours left to enroll

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