Understand Windows Internet Naming Service WINS

1
Goals

• Understand Windows Internet Naming Service (WINS)
• Understand the Domain Name System (DNS)
• Understand DNS name resolution
• Install and configure the DNS service
• Understand Routing and Remote Access Service
  (RRAS)
• Understand types of remote access connections

2
Goals (2)

• Configure remote access services
• Create a remote access policy
• Create a VPN server
• Examine Internet Connection Sharing (ICS)
• Examine Network Address Translation (NAT)

3
(Skill 1)
Understanding Windows Internet Naming Service
(WINS)

• A NetBIOS Name Server (NBNS) is an application
  responsible for mapping NetBIOS names to IP
  addresses
• Microsofts implementation of an NBNS is Windows
  Internet Naming Service (WINS)
• The computer running WINS is referred to as the
  WINS server
• WINS allows clients on a network configured to
  use WINS (called WINS clients) to dynamically
  register their NetBIOS name-to-IP address
  mappings in a database called the WINS database

4
(Skill 1)
Understanding Windows Internet Naming Service
(WINS) (2)

• Microsoft WINS clients use four methods in the
  following order to resolve NetBIOS names
• NetBIOS name cache Stores information about the
  most recently resolved NetBIOS names in client
  memory
• Windows Internet Naming Service (WINS) This
  method is the most likely to be used on a network
  and the most likely to succeed
• Broadcast The basic method of NetBIOS name
  resolution, which sends requests simultaneously
  to all network hosts on the attached subnet
• LMHOSTS file A text file, stored on the local
  computer, which contains the static mappings of
  NetBIOS names to IP addresses for computers on
  remote networks only

5
(Skill 1)
Figure 11-1 NetBIOS name resolution process using
WINS
6
(Skill 1)
Figure 11-2 Resolving a NetBIOS name using a
NetBIOS broadcast
7
(Skill 1)
Figure 11-3 Resolving a NetBIOS name using the
LMHOSTS file
8
(Skill 1)
Understanding Windows Internet Naming Service
(WINS) (4)

• Requirements on a TCP/IP network
• WINS can only be installed on a Windows NT
  Server, Windows 2000 Server, or Windows Server
  2003 computer
• The server must be configured with a static IP
  address, a subnet mask, a default gateway, and
  other TCP/IP parameters
• After a WINS server has been configured, you must
  make sure that the clients on the network are
  configured

9
(Skill 1)
Click to open the TCP/IP WINS Server dialog box
where you will enter the static IP address for a
WINS server
Figure 11-6 The WINS tab in the Advanced TCP/IP
Settings dialog box
10
(Skill 1)
Figure 11-7 The Networking Services dialog box
11
(Skill 1)
To view the content of the WINS database,
right-click Active Registrations and select
Display Records. Then, click the Find Now button
to view all active registrations in the details
pane. You can also create filters to search for
records based on a name pattern, IP address,
record owner, or record type.
Figure 11-8 The WINS console
12
(Skill 1)
Understanding Windows Internet Naming Service
(WINS) (5)

• It is a recommended practice to back up the WINS
  database every time the server shuts down (by
  selecting Backup database during server shutdown
  on the General tab)
• Burst handling is a method for handling a high or
  burst period of WINS registration and renewal
  traffic

13
(Skill 1)
Understanding Windows Internet Naming Service
(WINS) (6)

• WINS replication process
• Process by which WINS servers on a network swap
  information with one another
• It is done through partnering with other WINS
  servers so that all WINS servers are
  interconnected and replication occurs between
  them

14
(Skill 1)
Select to use IP multicasts to identify the other
WINS servers on the network and automatically
configure them as Push/Pull replication partners
Figure 11-13 The Advanced tab in the Replication
Partners Properties dialog box
15
(Skill 1)
Figure 11-14 The New Replication Partner dialog
box
16
(Skill 1)
Figure 11-15 The Replication Partners Properties
dialog box
17
(Skill 1)
Understanding Windows Internet Naming Service
(WINS) (7)

• WINS Push Replication
• Occurs when the service starts or when an address
  in the database changes
• The server pushes replication by notifying its
  partners that changes have occurred
• When the partners receive the notification, they
  can pull the replication data from the WINS
  server
• WINS Pull Replication
• Is controlled by setting a schedule for the
  partners
• By default, this is set to occur every 30 minutes

18
(Skill 1)
Figure 11-16 WINS replication
19
(Skill 1)
Figure 11-17 The Push Replication tab
Figure 11-18 The Pull Replication tab
20
(Skill 1)
Figure 11-19 The Intervals tab on the Properties
dialog box for a WINS server
21
(Skill 2)
Understanding the Domain Name System (DNS)

• Domain Name System (DNS) is the main name
  resolution service for Windows Server 2003
• DNS servers, also referred to as DNS name
  servers, perform the task of name resolution to
  convert host names to IP addresses
• The DNS namespace
• Has a hierarchical structure
• The nodes in this hierarchical structure are
  called domains
• As you add more domains to the DNS hierarchy, the
  name of the parent domain is added to the child
  domain or sub-domain

22
Understanding the Domain Name System (DNS) (2)
(Skill 2)

• DNS hierarchy
• The domain at the top is called a root domain and
  is represented by a trailing period
• The child domain of the root domain is called a
  top-level domain
• The child domain of a top-level domain is called
  a second-level domain
• A host name is at the bottom of the DNS hierarchy
  and designates a particular computer
• A fully qualified domain name (FQDN) includes a
  domain name in addition to a host name

23
(Skill 2)
Figure 11-20 The DNS hierarchy
24
(Skill 2)
Figure 11-21 A FQDN
25
(Skill 2)
Understanding the Domain Name System (DNS) (3)

• On a small network, a DNS server may contain just
  one database file that stores all of the
  name-to-IP-address resolution data
• In larger networks, it may be necessary to create
  zones
• Zone are distinct, contiguous segments of the DNS
  namespace
• Servers in each zone store records about the
  resources in that zone in a file called a zone
  database file
• A zone database file contains various types of
  resource records

26
(Skill 2)
Understanding the Domain Name System (DNS) (4)

• When multiple DNS servers are created in a
  standard DNS zone, there are two kinds of DNS
  database files primary and secondary
• Primary database file
• Modifications can be made only to the primary
  database file
• Zone transfers occur to replicate any changes to
  the primary zone database file to the secondary
  zone database file
• Secondary database file servers
• Reduce the traffic and query load on the primary
  database zone server
• Provide redundancy so that if the authoritative
  server is down, the secondary database file
  servers can service requests

27
(Skill 2)
Understanding the Domain Name System (DNS) (5)

• Caching-only name servers
• Use caching to store information collected
  during name resolution
• They are not authoritative for any zone
• Cache query results to reduce network traffic
• A query result can be cached for a specific
  amount of time called the Time to Live (TTL),
  after which it is deleted

28
(Skill 2)
Figure 11-22 The DNS namespace subdivided into
zones
29
(Skill 3)
Understanding DNS Name Resolution

• Client computers can make two standard types of
  queries to a DNS server a forward lookup query
  and a reverse lookup query
• A forward lookup query occurs when a client asks
  the DNS server to resolve a host name to an IP
  address
• A reverse lookup query
• Involves resolving a known IP address to a host
  name
• Uses the in-addr.arpa domain, a special
  second-level domain created expressly for this
  task

30
(Skill 3)
Understanding DNS Name Resolution (2)

• Recursive query
• A type of forward lookup query used to request
  that a DNS name server provides the full and
  complete answer to the query
• It is a request for the answer, not for a
  referral to another DNS server that may be able
  to answer the query
• Iterative query
• If the designated DNS name server is unable to
  resolve the destination host name on its own, it
  sends an iterative query on behalf of the client
  to assist in answering the recursive query
• Iterative queries allow DNS servers to send back
  pointer or referrals
• Resolver
• A host that performs a recursive search and
  issues iterative queries
• Queries other DNS name servers, including root
  servers, to look up DNS records on behalf of the
  client

31
(Skill 3)
Figure 11-23 Forward lookup queries
32
(Skill 3)
Figure 11-24 in-addr.arpa
33
(Skill 3)
Figure 11-25 Resolving a host name to an IP
address
34
(Skill 4)
Installing and Configuring the DNS Service

• Considerations
• The size of your network is important because key
  implementation issues will vary for small,
  mid-sized, and large networks
• DNS resilience
• Refers to the hardiness of the DNS
  infrastructure, specifically its ability to
  continue operating when individual components
  have been damaged
• To ensure DNS resiliency, you should have at
  least one primary and one secondary DNS server
  for a domain

35
(Skill 4)
Installing and Configuring the DNS Service (2)

• Using DNS on an intranet, the Internet, or both
• If you plan to use DNS on both, you must decide
  whether you want to use a single domain name for
  both, or different domain names for internal and
  external resources
• If you plan to have an Internet presence, you
  must register your domain name with an Internet
  naming authority such as Network Solutions
• Registering your domain name is not required if
  you plan to implement DNS only on an intranet,
  but it is recommended
• Types of DNS zones
• Root zone is a zone authoritative for the root
  domain
• Forward lookup zones are used to resolve host
  names to IP addresses
• Reverse lookup zones are used to resolve IP
  addresses to host names

36
(Skill 4)
Figure 11-26 Same internal and external DNS
namespace
37
(Skill 4)
Figure 11-27 The DNS Cache file opened in
Microsoft Word
38
(Skill 4)
Installing and Configuring the DNS Service (3)

• Main types of zones
• The standard primary zone is the first zone to be
  created and it is authoritative for one or more
  domains
• Secondary zones
• Read-only copies of another zone on the network
• Created after the primary zone to provide
  redundancy for the primary name server
• Stub zones are an enhancement to delegated
  sub-domains that were added as a new feature in
  Windows Server 2003s DNS Server service
• Active Directory-integrated zone uses Active
  Directory to store and replicate zone database
  files

39
(Skill 4)
Installing and Configuring the DNS Service (4)

• Locations where DNS zones can be stored in Active
  Directory
• Domain directory partition
• Where data pertaining to a particular Active
  Directory domain is stored
• This includes data about objects such as users
  and computers
• Application directory partitions
• Implemented to improve replication efficiency in
  situations where only a subset of the domain
  controllers needs a copy of the application data
• Use them to store data that will only be
  replicated to a specific group of domain
  controllers

40
(Skill 4)
DNS zone data will be replicated to all domain
controller/DNS servers in the Active Directory
forest
Figure 11-28 Creating an application directory
partition for a forest
41
(Skill 4)
DNS zone data will be replicated to all domain
controller/DNS servers in the Active Directory
domain
Figure 11-29 Creating an application directory
partition for a domain
42
(Skill 4)
Figure 11-30 Installing the DNS service
43
(Skill 4)
Figure 11-31 The dnsmgmt console
44
(Skill 4)
Figure 11-32 The Select Configuration Action
screen
45
(Skill 4)
Figure 11-33 The Forward Lookup Zone screen
46
(Skill 4)
Figure 11-34 The Zone Type screen
47
(Skill 4)
Figure 11-35 The Dynamic Update screen
48
(Skill 4)
Figure 11-36 The Reverse Lookup Zone screen
49
(Skill 4)
Installing and Configuring the DNS Service (5)

• Reverse lookup zone
• Can be created in the console tree
• The first reverse lookup zone is a primary zone
• If your DNS server is a domain controller and you
  are creating an Active Directory-integrated zone,
  you must configure how you want zone data to be
  replicated
• The default configuration is for zone data to be
  replicated to all domain controllers in the
  Active Directory domain (domain directory
  partition)

50
(Skill 4)
Installing and Configuring the DNS Service (6)

• Resource records
• A zone must contain the resource records for all
  resources in the domain for which it is
  responsible
• When a zone is created, DNS automatically adds an
  SOA (Start of Authority) resource record and a NS
  (Name Server) resource record

51
(Skill 4)
Figure 11-37 Adding a resource record