25.06.2013 Views

Lotus Domino Administrator 7 Help - Lotus documentation

Lotus Domino Administrator 7 Help - Lotus documentation

Lotus Domino Administrator 7 Help - Lotus documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Tip: Use policies to automate the setup of Connection documents for Notes users. Even if you use<br />

DNS, you should set up Connection documents for Notes users in locations from which they have<br />

difficulty accessing the DNS server.<br />

For more information on policies, see the chapter ″Using Policies.″<br />

Alternative IP name services<br />

Microsoft networking services offers four additional methods of IP address resolution. These methods are<br />

not as reliable as traditional DNS and hosts files and can cause name and address confusion. For best<br />

results, do not use these methods when also using the Notes network port for TCP/IP.<br />

v Direct NetBIOS broadcast -- The system sends out a name broadcast message so that all of the systems<br />

on the local network segment can register the name and IP address in their name cache. If you must<br />

use NetBIOS over IP and use <strong>Domino</strong> with both the NetBIOS and TCP/IP port drivers, avoid<br />

name-resolution problems by giving the <strong>Domino</strong> server and the system different names.<br />

Master Browser cache (for NT domains or SAMBA servers) -- Collects broadcasted names and IP<br />

addresses and publishes them across the NT domain to other Master Browser systems for Windows<br />

systems to access in their name lookups.<br />

v Windows Internet Name Service (WINS) -- Uses NetBIOS broadcasts. Unlike DNS, which is static in<br />

nature, WINS is dynamic. Note that the TCP/IP stacks of Macintosh and UNIX client systems may not<br />

be able to access the WINS server.<br />

v LAN Manager Hosts (LMHosts) -- A static hosts file method.<br />

CAUTION:<br />

On a Windows system, the combination of the system’s native NetBIOS over IP name-resolver service<br />

and DNS can cause name resolution failure for the <strong>Domino</strong> server name.<br />

For information on avoiding this problem, see the topic ″Server name-to-address resolution over<br />

NetBIOS″ later in this chapter.<br />

Ensuring DNS resolves in TCP protocols<br />

When you register a new <strong>Domino</strong> server, you specify a common name for it. Within a <strong>Domino</strong><br />

hierarchical name, the common name is the portion before the leftmost slash. For example, in the name<br />

App01/East/Acme, the common name is App01. The common name, not the hierarchical name, is the<br />

name that the <strong>Domino</strong> server is known by in DNS.<br />

Note: When you choose a common name for a <strong>Domino</strong> server that uses DNS, use only the characters 0<br />

through 9, A through Z, and the dash (-). Do not use spaces or underscores.<br />

Note: The DNS names held in <strong>Lotus</strong> Notes and <strong>Lotus</strong> <strong>Domino</strong> are not case sensitive; Notes workstations<br />

and <strong>Domino</strong> servers always pass DNS names to DNS in lowercase.<br />

You can avoid problems and extra work if you consider the DNS configuration, as well as the effect of<br />

other protocol name-resolver services, when you choose the format for the common name of the <strong>Domino</strong><br />

server.<br />

To avoid name-resolution problems that affect all TCP services on Windows systems, see the topic<br />

″Ensuring DNS resolves on Windows systems -- All TCP protocols.″<br />

For procedures to help you avoid DNS problems in NRPC, see these topics:<br />

v Ensuring DNS resolves in NRPC -- Best Practices<br />

v Ensuring DNS resolves in NRPC -- Alternative practices<br />

v Ensuring DNS resolves in NRPC -- A practice to use with caution<br />

Chapter 2. Setting Up the <strong>Domino</strong> Network 19<br />

®

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!