gunavelu
asked on
Name Resolution Order
The name resolution order on Win2K as per Microsoft' documentation says try DNS first and then WINS.
But when i run a capture tool i made the following observations -
- If a net command is used, ex: net use \\NetBIOSname, WINS is tried first and then DNS
- If a ping command is used, ex: ping hostname.domain.com, DNS is tried first and then WINS.
Can anyone tell me what exactly is the resolution order on Win2K?
But when i run a capture tool i made the following observations -
- If a net command is used, ex: net use \\NetBIOSname, WINS is tried first and then DNS
- If a ping command is used, ex: ping hostname.domain.com, DNS is tried first and then WINS.
Can anyone tell me what exactly is the resolution order on Win2K?
ASKER
So i would assume the order specified in Microsoft documentation is valid only for FQDN / shortnames used by typical TCP/IP applications like ping, telnet.
For all "Windows Networking" commands, the order would be WINS first and then DNS. Is this correct?
For all "Windows Networking" commands, the order would be WINS first and then DNS. Is this correct?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The first is "NetBIOS name resolution" and the second is "hostname resolution".
Also, for NetBIOS name resolution, the 'NetBIOS node type' will modify behaviour. It's not always WINS first, sometimes it will use a broadcast first. There's also a checkbox to enable or diable LMHOSTS file usage.
For typical sitautions (using a Hybrid node type) it's like this:
NetBIOS name resolution:
1)NetBIOS name cache
2)WINS
3)broadcast
4)LMHOSTS file
5)DNS
6)HOSTS file
Hostname resolution:
1)checks localhost name (ie. am I trying to find myself)
2)DNS
3)Hosts file
4)WINS
5)broadcast
6)LMHOSTS
There are a bunch of twists to this - Here's a great article with flowcharts for you:
http://www.microsoft.com/windows2000/techinfo/reskit/en-us/default.asp?url=/windows2000/techinfo/reskit/en-us/ProRK/prcc_tcp_gclb.asp
Checkout the entire section called "Configure TCP/IP name resolution.
JP