Download NetBIOS name resolution

IP V6 Link Local Zone ID:
When using site-local addresses, it is possible to be connected to multiple sites. In this case, each site is assigned a site identifier.
To define the area of the network for which the destination is intended, the zone ID is used to indicate the site identifier. In the IPv6
protocol, the zone ID is the Zone ID for Site from the display of the netsh interface ipv6 show interface level=verbose command. If
you are connected only to a single site, the default site identifier is 1 and the zone ID does not have to be specified. The site
identifier is defined locally on each IPv6 host. Because of this, the site identifier used by Host A to reach Host B might not be the
same as the site identifier used by Host B to reach Host A. You can determine your Zone ID number by opening a command prompt
window and entering the command ipconfig. This command returns information specific to your local system’s addresses.
For example, in the command ping fe80::4d3d:3426:46e6:1457%2, the address is of the computer you want to ping while the zone
ID (%2) corresponds to the network interface of your computer.
The ZoneID option specifies the scope or zone of the destination for the ICMPv6 Echo Request
messages. For link-local addresses, the zone identifier (ID) is typically equal to the interface index, as
displayed in the output of the netsh interface ipv6 show interface command. For site-local addresses,
the zone ID is equal to the site number, as displayed in the output of the netsh interface ipv6 show
interface level=verbose command. If multiple sites are not being used, a zone ID for site-local
addresses is not required. You can also obtain the zone ID from the display of the Ipconfig command.
The number after the "%" character in the display of an address indicates the zone ID. The zone ID is
not needed when the destination is a global address.
For example, to send Echo Request messages to the link-local address FE80::260:97FF:FE02:6EA5
using zone ID 4 (the interface index of an installed Ethernet adapter), use the following command:
ping fe80::260:97ff:fe02:6ea5%4
Ip6.arpa is live ipv4 reverse DNS record
Reverse DNS lookups for IPv6 addresses use the special domain ip6.arpa. An IPv6 address appears
as a name in this domain as a sequence of nibbles in reverse order, represented as hexadecimal digits
as subdomains. For example, the pointer domain name corresponding to the IPv6
address 2001:db8::567:89ab isb.a.9.8.7.6.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b
.d.0.1.0.0.2.ip6.arpa.
ISATAP
ISATAP is the Intra-site Automatic Tunnel Addressing Protocol. ISATAP is an IPv6 transition technology
that allows you to use IPv6 applications on a IPv4 network. For example, support you have a new
application called AppA. This application is designed to take advantage of the IPv6 networking protocol,
but your network isn't designed to support IPv6. Your routers only work with IPv4, your DNS infrastructure
is based on IPv4, your DHCP servers are designed to work only with IPv4, and you just don't want to deal
with IPv6. However, you are interested in AppA - so you want to get this IPv6 application working on your
IPv4 network.
ISATAP can help you get AppA to work. ISATAP will encapsulate the IPv6 packets with an IPv4 header
before sending them out to the network. While on the network, the IPv6 packets travel inside the IPv4
header, so that they can be routed throughout your IPv4 network using your IPv4 routing infrastructure.
Once the packet reaches the destination, the IPv4 header is removed from the packet, and the IPv6
packet is revealed to AppA.
Teredo:
Same encapsulation technology but can perform over ipv4 NAtted devices.
DHCP Suprscope:
Create two different scopes (Subnets on same wire) and combined them in one super scope.
LMHOSTS
The LMHOSTS file is a local text file that maps IP addresses to NetBIOS names of remote servers with
which you want to communicate over the TCP/IP protocol. Windows recognizes names instead of IP
addresses for network requests and a name discovery process is used to correctly route network requests
with TCP/IP. Because the name discovery process is generally not routed by an IP router, the LMHOSTS
file allows Windows machines to communicate using TCP/IP across a subnet.
NetBIOS name resolution
NetBIOS name resolution means successfully mapping a NetBIOS name to an IP address. A NetBIOS name
is a 16-byte address that is used to identify a NetBIOS resource on the network. A NetBIOS name is either
a unique (exclusive) or group (nonexclusive) name. When a NetBIOS process is communicating with a
specific process on a specific computer, a unique name is used. When a NetBIOS process is
communicating with multiple processes on multiple computers, a group name is used.
An example of a process that uses a NetBIOS name is the File and Printer Sharing for Microsoft Networks
service on a computer running Windows XP Professional. When your computer starts up, this service
registers a unique NetBIOS name based on the name of your computer. The exact name used by the
service is the 15-character computer name plus a 16th character of 0x20. If the computer name is not
15 characters long, it is padded with spaces up to 15 characters.
When you attempt to make a file-sharing connection to a computer by using its computer name, the File
and Printer Sharing for Microsoft Networks service on the file server you specify corresponds to a specific
NetBIOS name. For example, when you attempt to connect to a computer called CORPSERVER, the
NetBIOS name corresponding to the File and Printer Sharing for Microsoft Networks service on that
computer is:
CORPSERVER
[20]
Which name are we talking about?
The first issue is determining the kind of name. In the Windows client world, there are two basic
types of names. The first kind is a name for IP addresses. Host name resolution uses a host’s file
and DNS for resolution. The second kind of name is the NetBIOS name, which is used for Windows
(SMB) type sharing and messaging. These are the names that are used when you are mapping a
drive or connecting to a printer. These names are resolved either by using an LMHosts file on the
local machine or WINS server, or by broadcasting a request.
how NetBIOS names work
NetBIOS names are located through a series of steps that begins with checking the local cache. You
then check an LMHosts file and, lastly, progress into a broadcast message that looks for the name
(that is, unless the default actions have been changed). Before you begin, you need to understand
the four kinds of resolution that NetBIOS does natively.
Caching only DNS
A caching only name server is a Domain Name System (DNS) Server that is not authoritative for any
particular domain. Its only function is to look up names for clients and cache them.
After a period of time, as names are resolved, the cache will be populated with the most frequently
requested names, and these names/addresses are available quickly for subsequent queries.
A caching-only DNS server may be valuable at a site where DNS functionality is needed locally but there is
not a requirement for a separate domain for that location. This will reduce the amount of DNS traffic on a
Wide Area Network (WAN), as the DNS cache may be able to satisfy many of the queries locally.
dnscmd [<ServerName>] /config /enableglobalqueryblocklist 0|1
DNS Security Extension
http://technet.microsoft.com/en-us/library/ee683904(v=ws.10).aspx
DNS Cache Locking
http://technet.microsoft.com/en-us/library/ee683892(v=ws.10).aspx
DNS Socket Pool
http://technet.microsoft.com/en-us/library/ee683907(v=ws.10).aspx
To enable global name zones
dnscmd <ServerName> /config /enableglobalnamessupport 1