74 lines
4.9 KiB
HTML
74 lines
4.9 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Determine domain structure" />
|
||
|
|
<meta name="abstract" content="If you are setting up a domain for the first time, you should plan for demand and maintenance before creating zones." />
|
||
|
|
<meta name="description" content="If you are setting up a domain for the first time, you should plan for demand and maintenance before creating zones." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkplanning.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkscenario3.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakkplanningdomainstructure" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Determine domain structure</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakkplanningdomainstructure"><a name="rzakkplanningdomainstructure"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Determine domain structure</h1>
|
||
|
|
<div><p>If you are setting up a domain for the first time, you should plan
|
||
|
|
for demand and maintenance before creating zones.</p>
|
||
|
|
<p>It is important to determine how you divide your domain or subdomains into
|
||
|
|
zones, how to best serve network demand, access to the Internet, and how to
|
||
|
|
negotiate firewalls. These factors can be complex and must be dealt with case-by-case.
|
||
|
|
Refer to authoritative sources such as the O'Reilly DNS and BIND book for
|
||
|
|
in-depth guidelines.</p>
|
||
|
|
<p>If you configure a Domain Name System (DNS) zone as a dynamic zone, you
|
||
|
|
cannot make manual changes to zone data while the server is running. Doing
|
||
|
|
so might cause interference with incoming dynamic updates. If it is necessary
|
||
|
|
to make manual updates, stop the server, make the changes, and then restart
|
||
|
|
the server. Dynamic updates sent to a stopped DNS server will never be completed.
|
||
|
|
For this reason, you might want to configure a dynamic zone and a static zone
|
||
|
|
separately. You can do this by creating entirely separate zones, or by defining
|
||
|
|
a new subdomain, such as dynamic.mycompany.com, for those clients that will
|
||
|
|
be maintained dynamically.</p>
|
||
|
|
<p>iSeries™ DNS
|
||
|
|
provides a graphical interface for configuring your servers. In some cases,
|
||
|
|
the interface uses terminology or concepts that might be represented differently
|
||
|
|
in other sources. If you refer to other information sources when you are planning
|
||
|
|
for your DNS configuration, it might be helpful to remember the following:</p>
|
||
|
|
<ul><li>All zones and objects defined in a server are organized within the folders <span class="uicontrol">Forward
|
||
|
|
Lookup Zones</span> and <span class="uicontrol">Reverse Lookup Zones</span>.
|
||
|
|
Forward lookup zones are the zones that are used to map domain names to IP
|
||
|
|
addresses, such as A records. The reverse lookup zones are the zones that
|
||
|
|
are used to map IP addresses to domain names, such as PTR records.</li>
|
||
|
|
<li>iSeries DNS
|
||
|
|
refers to <em>primary zones</em> and <em>secondary zones</em>.</li>
|
||
|
|
<li>The interface uses <em>subzones</em>, which some sources refer to as <em>subdomains</em>.
|
||
|
|
A child zone is a subzone for which you have delegated responsibility to one
|
||
|
|
or more name servers.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakkplanning.htm" title="Domain Name System (DNS) offers a variety of solutions. Before you configure DNS, it is important to plan how it works within your network. Subjects, such as network structure, performance, and security, should be assessed before you implement DNS.">Plan for Domain Name System</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzakkscenario3.htm" title="This example depicts Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) on the same server.">Example: Domain Name System and Dynamic Host Configuration Protocol on the same iSeries server</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|