If you want the MS resource that is taken from, it's here: http://technet.microsoft.com/en-us/library/bb457118.aspx
Christopher Bodnar Enterprise Architect I, Corporate Office of Technology:Enterprise Architecture and Engineering Services Tel 610-807-6459 3900 Burgess Place, Bethlehem, PA 18017 christopher_bod...@glic.com The Guardian Life Insurance Company of America www.guardianlife.com From: Christopher Bodnar <christopher_bod...@glic.com> To: "NT System Admin Issues" <ntsysadmin@lyris.sunbelt-software.com> Date: 11/07/2012 11:02 AM Subject: Re: Confused about DNS resolution on a server with 2 NICs on a DMZ Have you taken a look at this yet? http://www.scribd.com/doc/63870216/108/Multihomed-Name-Resolution Christopher Bodnar Enterprise Architect I, Corporate Office of Technology:Enterprise Architecture and Engineering Services Tel 610-807-6459 3900 Burgess Place, Bethlehem, PA 18017 christopher_bod...@glic.com The Guardian Life Insurance Company of America www.guardianlife.com From: Michael Leone <oozerd...@gmail.com> To: "NT System Admin Issues" <ntsysadmin@lyris.sunbelt-software.com> Date: 11/07/2012 10:14 AM Subject: Confused about DNS resolution on a server with 2 NICs on a DMZ So, today's confusion ... we have a webserver on our DMZ, Win 2008 R2. It has 2 NICs, and external and an internal. The external NIC has DNS settings pointing to our ISp (Verizon, in our case). The internal NIC has DNS settings of our internal LAN. So how come, if I say "ping <other internal server>", the name resolves and I can ping? (I can understand how the ping succeeds; we have a static route to our internal servers). But how is the name resolving to the internal address? Using another of my internal servers as a target (i.e., not on the DMZ): If I do "ping <shortname>", it says could not find host. That's good; we don't have our domain name set in the NIC properties. if I do "ping <FQDN>", it says "Pinging <FQDN> [internal IP]". And how does it know to do that?? It appears that it's succeeding by using the internal NIC, but how does it know to use the internal NIC to resolve a name? If it was an internal IP, I could understand it - it would use the static route. Is it normal behavior to use the DMZ NIC, and - if that fails - silently use the INTERNAL NIC? That makes no sense to me either, but that's all I am coming up with, for why this is working. Can somebody clear up my age-fogged brain about this?? There is no HOSTS file, these are not domain members. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ----------------------------------------- This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
<<image/jpeg>>
<<image/jpeg>>
