name resolution order

[djc]

I knew this at one time but I think I need a refresher. The order of name
resolution mechanisms used by Windows clients IN ORDER from 1st to last are:

1) hosts or lmhosts files
2) any configured DNS or WINS servers
3) broadcasts

Thats how I remember it.... but its been a while.

1) could someone please correct me if I'm wrong.
2) I am confused about the order with regard to the different types of
'names'. Meaning, in my recollection of the order (which may be wrong) it
combines both DNS and NETBIOS name resolution methods in the same 'tier'...
this would lead one to believe that the machine firsts attempts say, the
hosts file, which is for DNS host names, then it tries the lmhosts file,
which is for NETBIOS names, etc... does it keep flopping back and forth
between name types like that or does it exhaust all DNS methods before
moving to NETBIOS methods or vice versa?

any info is apprecated. thanks!

 

[Jeff Cochran]

I knew this at one time but I think I need a refresher. The order of name
resolution mechanisms used by Windows clients IN ORDER from 1st to last are:

Dependent on whether you're talking TCP/IP name resolution or NetBIOS
name resolution.

TCP/IP:

Hosts
DNS
Cache
WINS
Broadcast
LMHosts

NetBIOS:

Cache
WINS
Broadcast
LMHosts
Hosts
DNS

Now, if you need the seven layers of the OSI model to help bone up on
your NT4 MCSE exams...

Jeff

 

[Doug Sherman [MVP]]

The short answer is .... well, it depends. In h node the default search
order for name resolution is:

1. NetBIOS name cache
2. WINS server
3. B-node broadcast
4. LMHOSTS file
5. HOSTS file
6. DNS server

A Windows computer assumes you are seeking to resolve a NetBIOS name unless
you use a winsock based program such as ping or http. In that case, the
search order becomes, cache, hosts file, DNS server, and yup - lmhosts file.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP