cc/td/doc/product/rtrmgmt/ciscoasu/nr/nr_2_5
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring a Loopback Zone

Configuring a Loopback Zone

A loopback zone is a reverse zone that enables a host to resolve the loopback address (127.0.0.1) to the name localhost. The loopback address is used by the host to enable it to direct network traffic to itself. You can configure a loopback zone manually or you can import it from an existing BIND zone file.

Normally you do not have to configure a loopback zone, because Network Registrar automatically creates one for you. If, however you accidently delete the loopback zone, you can use the following instructions to create a new one.

Manually Configuring a Loopback Zone

Step 1 From the Server Manager (Figure 4-10), select the DNS server, for example DNS@localhost.

Step 2 Click the Add toolbar button.


Figure G-1:
Add Zone Dialog Box

Step 3 In the Name field in the Add Zone dialog box (Figure G-1), enter the loopback zone name, 127.in-addr.arpa.

Step 4 Click Primary.

Step 5 Click OK.


Figure G-2:
SOA Tab (Add Primary DNS Zone Dialog Box)

Step 6 From the Add Primary DNS Zone dialog box, click the SOA (Start of Authority) tab (Figure G-2).

Step 7 In the Contact email address field, enter loopback.

Step 8 In the Name of primary server field, enter localhost.

Step 9 In the remaining fields, enter the appropriate values or accept the defaults.


Figure G-3:
Name Servers Tab (Add Primary DNS Zone Dialog Box)

Step 10 Click the Name Servers tab (Figure G-3).

Step 11 Enter the names of the servers authoritative for the zone, which is localhost.

Network Registrar appends the FQDN to the server.

Step 12 Enter the TTL value or accept the default.

The dash character (-) in the TTL field means use the default value.


Figure G-4: Resource Records Tab (Add Primary DNS Zone Dialog Box)

Step 13 Click the Resource Records tab (Figure G-4).

Step 14 Click Add.


Figure G-5: PTR Tab (Add Resource Record Dialog Box)

Step 15 Click the PTR tab in the Add Resource Record dialog box (Figure G-5).

Step 16 In the Name field, enter 1.0.0.

Step 17 In the Data field, enter localhost.

Step 18 Click OK.


Figure G-6: A Tab (Add Resource Record Dialog Box)

Step 19 Click the A tab (Figure G-6).

Step 20 In the Name field, enter localhost.

Step 21 In the Address field, enter 127.0.0.1.

Step 22 Click OK.

Step 23 Click Close.


Figure G-7: Configured Resource Record

The Resource Record should look like the example shown in Figure G-7.

Importing a Loopback Zone From BIND

Step 1 From the Server Manager, select the DNS server, for example DNS@localhost (Figure 4-10).

Step 2 Click the Add toolbar button.

Step 3 In the Name field in the Add Zone dialog box (Figure G-8), enter the loopback zone name 127.in-addr.arpa.

Step 4 Click the Primary button.


Figure G-8: Add Zone Dialog Box

Step 5 Do one of the following:

Enter the name of the BIND zone file and click OK.

or


Figure G-9: Open Dialog Box

Step 6 Click OK.

Network Registrar imports the contents of your BIND zone file, except for any comments.

Reloading the DNS Server

After you have configured the DNS server, you need to reload it to write the configuration information to Network Registrar's database.


Note A
red star will appear on the server in the tree control if the server has never been successfully started. After the server has been started, the red star will appear only if you make a change to the server.

Step 1 From the Server Manager (Figure 4-10), select the server you want to reload.

Step 2 Click the Control toolbar button.


Figure G-10: Control Dialog Box

Step 3 In the Control dialog box (Figure G-10), Click Reload.

Step 4 Click OK.


Figure G-11: Server Control Results Dialog Box

The Server Control Results dialog box (Figure G-11) displays a message informing you whether the server has successfully reloaded. To view log messages, click View Recent Log.


Note Only the configuration messages are displayed when you click
View Recent Log. To see the entire log, view the \Registrar\Logs\ name_dns_1_log file.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Jul 13 11:57:09 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.