Jump to content

Win-2k / Exchange Server -> Hosts file?


Nomen

Recommended Posts

I've got Exchange running on a win-2k server. it's been running for years and recently have cloned the hard drive (just to be on safe side) and while I had the machine running, decided to check exchange using some sort of performance tool DL'd from Microsoft.

I don't have DNS server running on this box (don't really want to). Exchange is not used for email.

The performance tool says that exchange can't resolve it's own FQDN / host-name, even though I have it in the HOSTS file and ping and tracert can resolve the name to 127.0.0.1 just fine. But nslookup must query the DNS server directly (bypassing the hosts file).

(tangent - I've noticed on NT systems that nslookup never seems to know about HOSTS file entries, I didn't think it had a choice since I thought that the TCP/IP stack was tied into HOSTS file lookup so I don't know how NSlookup can bypass it, but it does. Can anyone explain how?)

So I'm wondering why (or how) Exchange (or the exchange performance analysis tool) doesn't honor or recognize the info in the HOSTS file (or even the LMHOSTS file) when resolving host names. This leads to the bigger question - where exactly in the process of host lookups on an NT-based system does the HOSTS file fit in, and why or how can it be bypassed by certain processes / programs?

Link to comment
Share on other sites


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...