Re: DNS / WINS

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Cathy Moya [MS] (camoya_at_online.microsoft.com)
Date: 07/20/04


Date: Tue, 20 Jul 2004 13:31:07 -0700

Hi, Homer,
DNS is used for resolving host names to IP addresses and IP addresses to
host names.
WINS is used for resolving NetBIOS names to IP addresses (but does not do
reverse lookups.)

So that would lead to the next question, what is the difference between host
names and NetBIOS names? Well, usually they are the same name unless you try
to use a NetBIOS name that is not a valid host name. You used to get a pop
up message if you did that, like if you put an underscore in the name when
you installed your computer, and it would say something like, "Hey, your
host name will be different than your NetBIOS name - do you care?" Usually
it's just tidier to keep them using the same name for both.

NetBIOS names also have a special 16th character after the name that tells
what the name does, kind of like putting your job title on your business
card. Go to a command prompt and type NBTSTAT -n and you'll see all the
names you have registered in your NetBIOS name cache. The <00> means it's a
client computer. If you have <20> it means your server service is running.
If you have <03> it means your messenger service is running. If you're on a
primary domain controller, you'll see <1B> and if you're just any domain
controller you'll see <1C> after the domain name. NetBIOS names must be
unique, and your computer checks to make sure there isn't, for example,
another Computer X<20> before letting the server service start.

Host names can include the Fully Qualified Domain Name (FQDN) which has the
whole path for the host, like tw1.norcal.nwtraders.com. There should only be
one tw1 in norcal, but the host can still start if it's stealing someone
else's name. Host names can also use aliases, like tw1 could also be called
fred.norcal.nwtraders.com. NetBIOS names can never use aliases.

The main difference comes with the application you're using. The programmer
can write them to use different names. Things like web browsers and ping and
ftp want the host name and they perform name resolution in this order:
local host name (is it me?)
hosts file
DNS
If you're using applications that use a Universal Naming Convention (UNC)
like this \\server\share those applications are usually written to use
NetBIOS. Now at least until NT 4 I know that NetBIOS names usually resolved
in this order:
cache
WINS
broadcast
lmhosts
but in Windows 2000 and later there may be times when it tries to resolve
using DNS before it tries WINS. (It's probably documented somewhere on the
Microsoft.com site.)

So, why do you care about all of this for SMS? Because SMS can still have
ties to NetBIOS. If, for example, you haven't extended your schema for
Active Directory, we have to look at WINS for your management points and
server locator point because they can be registered in WINS with one of
those special 16th characters that says "I'm the server locator point".

Probably much longer answer than you wanted, but this was always my favorite
subject to teach. ;-)

-- 
Cathy Moya, MCSE: Security, MCT
Technical Writer, Enterprise Management Content Group
Check out the SMS Technical FAQ:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
This posting is provided AS IS with no warranties and confers no rights.
"Homer" <anonymous@discussions.microsoft.com> wrote in message
news:09f301c46e6c$a8986720$a301280a@phx.gbl...
> Can somebody tell me what the difference is between DNS
> and WINS.  Everytime I read about them the script tells
> me that they both resolve names back to IP Addresses.
>
> But surely they cannot be the same or you would not need
> to configure your servers for DNS and WINS?
>
> Thanks.


Relevant Pages

  • Re: DNS, WINS-R, Other?
    ... the record does not show up in DNS or in the WINS database. ... > I'm not curious about controlling WINS-R resolution, ... > querying the host at the requested IP address for its NetBIOS host ... kind of a direct NetBIOS query of the host at that IP address to find out ...
    (microsoft.public.windows.server.dns)
  • Re: How do I track down which server is resolving my DNS query?
    ... If I pinged it with just the host name, the IP address came back with an incorrect ip addressI have now removed the node from the network. ... DNS Server ... Broadcasts might resolve NetBIOS names (and even be used by a DNS ... enters into both DNS and NetBIOS name resolution. ...
    (microsoft.public.win2000.dns)
  • Re: DNS, WINS-R, Other?
    ... the record does not show up in DNS or in the WINS database. ... >> querying the host at the requested IP address for its NetBIOS host ... > kind of a direct NetBIOS query of the host at that IP address to find out ... > what its host name is, then caching that lookup in the NetBIOS cache. ...
    (microsoft.public.windows.server.dns)
  • Re: slow web browsing
    ... Once DNS resolved the name, downloading seems to be fast enough. ... host yahoo.com ... I've had some problems with firefox not resolving until I manually ... resovle something from the command line with the "host" command. ...
    (comp.os.linux.networking)
  • Re: netbios and sql replication
    ... lmhosts, hosts, DNS, sometimes DNS (if the host name has a. ... > If i have netbios enabled on the distributor is there any way to make it ... > subscriber in the host file and in the client network utility. ...
    (microsoft.public.sqlserver.replication)