Skip to main content


DNS and WINS are really for doing two different (but similar) things. Second, each has been co-opted to assist the other in some cases -- and as a last resort.
Literally Domain Naming System (DNS) servers, resolve Domain Naming System names to IP addresses. Sounds redundant, but technically it is almost literally true (not quite for you advanced people) that an IP host has NO NAME; it has a DNS name only by virtue of the DNS servers or by convention.
Windows Internet Naming Services (WINS) servers resolve NetBIOS names to IP addresses. NetBIOS names ARE a feature of the network node (or host machine). The NetBIOS protocols require that NetBIOS nodes 'defend' their name from other machines attempting to use the same name.
Likewise, a 'host' file resolves DNS names to IP addresses while an 'LMHOST' file resolves NetBIOS names to IP addresses.
So you can see a 1-1 mapping of DNS server to host file, and WINS server to LMHOSTS file.
The order of use of these name resolutions is dependent on various host options, check boxes, and the assigned node types. But in general, if a DNS name cannot be resolved to an IP address, then the WINS method will be used as a back-up resolution method.
Conversely, the DNS method can be selected -- or on some OS versions defaults -- for backing up the WINS/LMHOSTS resolution for NetBIOS names.
The exact order of each separate method is dependent on these options, as well. For instance there are 4 (now 5 but don't ask) main NetBIOS node types:
  • b-node
  • p-node
  • m-node
  • h-node.
B-nodes broadcasts only, p-nodes talk only to a WINS server or WINS proxy and do not broadcast, m-nodes (mixed) broadcast first, followed by using the p-node method, while h-node (hybrid) reverses the m-node order.
Now this whole idea of one method backing up the other method works only if the TWO host/NetBIOS names are the same -- or if they can be converted trivially.
This fact argues strongly for choosing names valid for both, e.g., 15 characters or less with no dashes, underscores, or other characters that are valid only on one resolution system. In this case, the TCP/IP software will construct the DNS name from the NetBIOS name automatically, e.g.,
My machine HAMACHI becomes
...where '' is the name I registered with the InterNIC.
The most important advantage of WINS name resolutions is that DHCP can instruct the station to register itself with the WINS server. DHCP 'leases' IP addresses to stations as they initialize their TCP/IP software. This leasing means that stations do not have to know or configure their own IP addresses locally; these addresses can be centrally administered on the DHCP server, and the software will correctly configure the address and other parameters at boot time.
There are some rudimentary methods of reverse DNS to approximate this, or to substitute for this by using BOOTP to distribute addresses, but these are much less capable at present and don't in general allow for dynamic assignment.
Additionally, dynamic assignment of IP addresses by DHCP allows an administrator to configure a small pool of IP addresses to effectively service a larger group of client machines. (More machines than addresses, even though each machine requires a unique address.)
Example, consider a hypothetical company owning a Class C address (limited to 254 nodes) with 100 office machines, and 300 sales people who work largely in the field.
If it can be determined that fewer than about 150 of those sales people will ever be in the office at one time, DHCP can lease and reclaim that pool of addresses to service all 400 machines from a pool of only 250 addresses.
DHCP DHCP can instruct the station to register these dynamic assignments with the WINS server, thus making these dynamically assigned addresses resolvable from the host name. DNS is largely a fixed, static database.
With Windows NT 4.0, Microsoft began the integrations of DNS with WINS. Under 4.0 DNS can resolve addresses by querying the WINS server, thus enabling a form of 'dynamic' DNS.) With the integration of WINS and DNS, even the DNS clients can participate in this scheme.
DHCP clients will register addresses with the WINS that is supporting the DNS server, which means that addresses can be dynamically allocated and resolved with both methods.
BTW, DHCP is an extension/elaboration of BOOTP, a standard protocol -- not just a Microsoft extension (RFC 1541, 1542 etc). WINS is Microsoft only (Windows Internet Naming ...). But it appears that Microsoft and other vendors are working on RFCs and standards to extend DNS or enhance a future replacement for DNS to offer all of the advantages of both schemes (Dynamic DNS).

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N