cc/td/doc/product/iaabu/cddm/cddm111
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Migrating Existing DNS Configuration and Zone Data

Migrating Existing DNS Configuration and Zone Data

This chapter demonstrates how to use existing DNS configuration and zone data to configure the CDDM. In this exercise, you will configure the DNS and DNM servers using a set of zone files provided with CDDM. On Solaris, HP-UX, and AIX systems, the files are in the directory install_dir/CSCOcddm/test, where install_dir is the directory in which you installed CDDM. On Windows NT systems, the files are in the directory install_dir\test. This chapter refers to both directories as the "test" directory.

The example zone files come from a name server, ns1.test.yoyodyne.com, which is configured as a primary name server for the domain, test.yoyodyne.com, and two subdomains, admin.test.yoyodyne.com and sales.test.yoyodyne.com. ns1 is also configured as a secondary name server for the domain eng.test.yoyodyne.com, for which ns2.eng.test.yoyodyne.com is primary. The grey area in Figure 6-1 represents the zones for which ns1 is authoritative.


Figure 6-1: Example

Domain

ns2.eng.test.yoyodyne.com is a Solaris system running the native DNS server. All hosts in test.yoyodyne.com are on the same network segment, 10.1.1, and ns1.test.yoyodyne.com is primary for the domain 1.1.10.in-addr.arpa.

Several steps also ask you to test your work by looking up specific names with nslookup.

To test your work in this exercise:

You can also follow the procedures in this exercise by entering values exactly as they appear in each step, and verify your work by comparing the DNM Browser and CSM screens with the figures in this chapter. If you have not met the above requirements, you will not be able to resolve names with nslookup.

The IP addresses used in this example comply with RFC 1918 so that you can create the test.yoyodyne.com domain exactly as shown in the procedures. You can, however, substitute your own IP addresses, and domain names.

Note yoyodyne.com is registered as a domain name with the NIC.

To migrate from existing DNS configuration and zone data:

Step 1 Make sure all servers are working (see Chapter 4, "Verifying the Installation").

Step 2 Import the existing zone files to the DNM Server using the DNM Browser (see "Importing the Existing Zone Files").

Step 3 Configure the Cisco DNS server to be secondary for the test domains (see "Making the DNS Server Secondary for the Test Zones").

Importing the Existing Zone Files

This procedure loads existing zone file data into the DNM server via a DNM Browser. Once the DNM server contains the zone data, you can configure DNS servers to obtain zone transfers for the imported zones.

Your native DNS server stores data for the test.yoyodyne.com domain in the file named.boot. This exercise assumes the named.boot file for the test domain's current DNS server contains the following lines:

primary test.yoyodyne.com db.test primary admin.test.yoyodyne.com db.admin primary sales.test.yoyodyne.com db.sales primary 1.1.10.in-addr.arpa db.1_1_10 secondary eng.test.yoyodyne.com 10.1.1.8 eng_yoyodyne.bak

Step 1 Start the DNM Browser and connect to the DNM server, "localhost," using the admin DNM user account and password set up in the "Verifying the Installation" chapter.

Step 2 If yoyodyne.com already appears in the DNM Browser window (remaining from the exercises in previous chapters), delete the DNM server's database by selecting the top-level domain ("."), and choosing Delete from the Edit menu.

Step 3 Load test.yoyodyne.com into the DNM server.

The first "primary" line in named.boot indicates that this host obtains zone data for the zone test.yoyodyne.com from the file, db.test. The CDDM includes a copy of this zone file in the test directory.


For example, if you installed CDDM in c:\multinet on a Windows NT system, choose c:\multinet\test\db.test as

follows:


Note Because the zone files in the test directory include $ORIGIN statements to specify fully qualified domain names, the DNM Browser ignores the Default Domain parameter. The Default Origin field must not be empty, or the DNM Browser will not allow you to import the zone files. For details on the Default Domain parameter, see the Cisco DNS/DHCP Manager Administrator's Guide.

The DNM server automatically creates the reverse mappings for ns1 and ns2 in the in-addr.arpa domain because the DNM Browser's "Automatically Maintain Record Pairs" parameter (under Settings in the Options menu) is enabled.


Note The presence of ns2.eng.test.yoyodyne.com in the DNM server is not sufficient to delegate eng.test.yoyodyne.com to ns2; you must also configure the DNS server to obtain zone transfers for eng.test.yoyodyne.com from ns2.

Step 4 Load admin.test.yoyodyne.com into the DNM server.

The second "primary" line in named.boot indicates that the DNS server obtains zone data for the zone admin.test.yoyodyne.com from the file, db.admin. The CDDM includes a copy of this zone file in the test directory.


For example, if you installed CDDM in c:\multinet on a Windows NT system, choose c:\multinet\test\db.admin as

follows:


Note Because the zone files in the test directory include $ORIGIN statements to specify fully qualified domain names, the DNM Browser ignores the Default Domain parameter. For details on the Default Domain parameter, see the Cisco DNS/DHCP Manager Administrator's Guide.

Step 5 Load sales.test.yoyodyne.com into the DNM server.

The third "primary" line in named.boot indicates that the DNS server obtains zone data for the zone sales.test.yoyodyne.com from the file, db.sales. The CDDM includes a copy of this zone file in the test directory.


For example, if you installed CDDM in c:\multinet on a Windows NT system, choose c:\multinet\test\db.sales as

follows:


Note Because the zone files in the test directory include $ORIGIN statements to specify fully qualified domain names, the DNM Browser ignores the Default Domain parameter. For details on the Default Domain parameter, see the Cisco DNS/DHCP Manager Administrator's Guide.

Step 6 Because the DNM server does not automatically create Start of Authority (SOA) records when it creates reverse domains, you must add an SOA record for 1.1.10.in-addr.arpa:

Step 7 Choose Exit from the File menu and click OK in the confirmation dialog box.

Importing Zone Files with dnm_import

dnm_import is a utility included with the CDDM that imports zone data directly into the DNM server. Unlike the import function of the DNM Browser, there is no user interface. You simply issue the command, and the data is automatically imported. In addition, since you can import from a named.boot file as well as individual zone files, you can import all of your zone files listed in the named.boot file at once.

This procedure uses the dnm_import program to import existing zone data stored in multiple zone files that are listed in the named.boot file. Once the DNM server contains the zone data, you can use the DNM Browser to modify the data, and you can configure DNS servers to obtain zone transfers for the imported zones.

Step 1 If you have already loaded yoyodyne.com in previous exercises, delete the DNM Server database by starting the DNM Browser, selecting the top-level domain ("."), and choosing Delete from the Edit menu.

Step 2 Change to the /test subdirectory of the CDDM directory. If you installed the CDDM in a directory called /cddm as shown in Chapter 2, then the full pathname to change to is:

For Solaris, HP-UX, and AIX: /cddm/CSCOcddm/test


For Windows NT: /cddm/test


Step 3 On the system on which the DNM server is running, from a command prompt issue one of the commands below, depending on which operating system you are running:

For Solaris, HP-UX, and AIX systems enter the command:


../bin/dnm_import -u admin -p admin -b named.boot


For Windows NT systems, enter the command:


../dnmimp32 -u admin -p admin -b named.boot


If you are using a user name or password different than the admin account set up in Chapter 4 of this guide, replace the admin following the -u parameter with your user name, and the admin following the -p with your password.


The dnm_import utility will load all of the zone files listed in the named.boot file. Note that our example named.boot file does not store the absolute pathname of the example zone files. That is why, for this test, you must run dnm_import from within the install_dir/test subdirectory, where install_dir is the CDDM installation directory.


Step 4 Verify that the zone data has been loaded by starting the DNM Browser. Double-click the .com domain and you should see that yoyodyne.com has been loaded. You can browse the rest of the domains to verify that all of the zone files have been loaded.

If you already had the DNM Browser running, from the Edit menu choose the Reload option to see the new domains.


Note For descriptions of dnm_import command line options, see the Cisco DNS/DHCP Manager Administrator's Guide.

Making the DNS Server Secondary for the Test Zones

Now that the DNM server contains the zone data for test.yoyodyne.com, admin.yoyodyne.com, sales.yoyodyne.com, and 1.1.10.in-addr.arpa, you can configure the DNS server on ns1 to be authoritative for those domains.

Step 1 Start the CSM.

Step 2 Choose the DNS server configuration editor by clicking the DNS icon in the Available Services list. Notice that the DNS server is already configured to resolve the reverse domain for "localhost" and "0.0.127.in-addr.arpa" in the Primary area.

Step 3 If a secondary entry already exists for yoyodyne.com (remaining from the previous exercise), delete it by selecting a field in that row, and clicking Delete in the secondary group.

Step 4 Make the DNS server secondary for test.yoyodyne.com:

where install_dir is the directory in which you installed CDDM.

Step 5 Make the DNS server secondary for admin.test.yoyodyne.com:

where install_dir is the directory in which you installed CDDM.

Step 6 Make the DNS server secondary for sales.test.yoyodyne.com:

where install_dir is the directory in which you installed CDDM.

Step 7 Make the DNS server secondary for 1.1.10.in-addr.arpa:

where install_dir is the directory in which you installed CDDM.

Step 8 Make the DNS server secondary for eng.test.yoyodyne.com:

Note Unlike standard BIND configuration files, the Cisco DNS configuration editor lets you specify secondaries by host name or by IP address if the corresponding Address record exists.
where install_dir is the directory in which you installed CDDM.

The DNS server configuration should appear as

follows:


Note that although ns1 was originally primary for test.yoyodyne.com, 1.1.10.in-addr.arpa, and the admin and sales subdomains, it is now secondary for these domains.


Step 9 Save the DNS server configuration.

Step 10 Restart the DNS server by clicking Restart.

Because the DNS server does not yet have backup zone files for the new zones, it requests zone transfers for test.yoyodyne.com, 1.1.10.in-addr.arpa, admin.test.yoyodyne.com, and sales.test.yoyodyne.com from the local DNM server, and it requests a zone transfer for eng.test.yoyodyne.com from ns2.eng.test.yoyodyne.com's DNS server.


Step 11 If you have used your own real domain name instead of yoyodyne.com in this exercise, test your system by resolving names with nslookup:

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1997 © Cisco Systems Inc.