|
|
Cisco Network Registrar (CNR) is a full-featured, scalable DNS and DHCP system for large IP networks. It provides the key benefits of stabilizing the IP infrastructure, automating networking services including client configuration and provisioning cable modems, and providing the foundation of user-based policies for CiscoAssure Policy Networking.
With unique features that enable integration with other network infrastructure software and business applications, Cisco Network Registrar enables enterprise and service provider users to better manage their networks.
Cisco Network Registrar is designed for managers of large business enterprises and for Internet Service Providers.
Cisco Network Registrar includes a wide range of unique and standard features that provide users with numerous benefits over competing products and public domain software. The most critical benefits are stabilizing the IP infrastructure, automating network services, and preparing for policy networking.
Table 1-1 describes Cisco Network Registrar features and benefits. The table is divided into DNS server, DHCP server, and architecture and user interface sections.
| Feature | Description | Benefit |
|---|---|---|
| DNS Server | ||
Supports use of the best practices described in RFC 2317. (Note: Network Registrar does not automatically generate the large number of alias records suggested in the RFC) | Helps support a wide variety of network topologies and DNS zone structures. | |
The DNS server can hide the subzone hierarchy for all zones delegated from a server. When enabled, the DNS server will not transfer NS and SOA records for a subzone during a zone transfer. Standard DNS queries continue to work. | Hides sensitive information about the topology of the network and devices on the network. | |
Allows DNS clients and DHCP servers to dynamically update DNS with new IP addresses and DNS name mappings. (RFC 2136) Network Registrar is the only DNS/DHCP product that implements dynamic DNS updates using this standard protocol. | Automatically registers clients in DNS and eliminates DNS management overhead. | |
Allows import of DNS information in the BIND zone file format; either individual files or all files specified in a named.boot file. | Speeds migration from BIND to Network Registrar. | |
Transfers only the incremental changes in a DNS zone during a zone transfer. Network Registrar is the only DNS server to support Incremental Zone Transfers. (RFC 1995) | Dramatically reduces time and bandwidth required to propagate DNS updates throughout a network. Particularly valuable if updates must traverse expensive WAN links | |
Allows configuration of a DNS server as an internal root server. | Supports IP networks that are not connected to the Internet. | |
Interoperable with BIND | Interoperates with BIND and other RFC-compliant DNS servers. Network Registrar can be primary to a BIND secondary and vice-versa. | Supports mixed environments and a phased migration from BIND. |
Primary DNS server notifies secondary DNS servers of changes to zone information. (RFC 1996) | Speeds up the propagation of dynamic DNS information. | |
DNS cache data is stored in indexed disk files. Controls the amount of physical memory used by the DNS server. Preserves DNS cache data across system or server restarts. | Improves performance and reduces amount of memory used by the DNS server. Prevents thrashing which is caused when the DNS server consumes all physical memory. | |
Preconfigured with the names and addresses of the Internet root name servers. Can be updated or overridden if needed. | Speeds and simplifies installation and configuration. | |
Selectively forwards DNS queries for specified domains to internal DNS servers rather than recursively querying the root name servers on the Internet and external DNS servers. | Allows DNS to work among subsidiaries (intranets) or trading partners (extranets) without using the Internet, and thus improving network privacy. | |
If one name owns multiple A records (address records), the order of the records is rotated in successive queries for that name. | Provides a rudimentary form of load balancing. (Note: Cisco Local Directors and Distributed Director are superior solutions for load balancing) | |
Supports SRV records, including dynamic DNS update of SRV records. ("Experimental" RFC 2052) | Windows 2000 compatibility. Microsoft has identified this feature as required for DNS servers in a Windows 2000/Active Directory environment. | |
When the DNS resolver (client), DNS server, and target are all on the same subnet, and the target has multiple addresses (A records), the server will list, in the reply, the address on the common subnet first. | ||
| DHCP Server | ||
BOOTP and Dynamic BOOTP | Supports older BOOTP clients, including many network printers | |
Supports customization of IP address, DHCP options, and fully-qualified domain name based on client's MAC address. Similar clients can be grouped into classes, and customization applied to the class. Can deny addresses to clients or classes |
| |
Allows configuration of new DHCP options | Flexibility in supporting options required by custom DHCP clients, or options standardized between revisions of Cisco Network Registrar | |
Compliance with RFC 2132. | Ensures standard option definition. | |
Supports the DHCP relay agent option, as specified in draft-ietf-dhc-agent-options. | Supports DOCSIS modems | |
Includes features needed by DOCSIS modems. These include: | Supports data-over-cable service providers | |
DHCP server updates the DNS server with two records each in the forward and reverse zones. The forward zone receives an A record (Name and IP address) and a TXT record with the client ID (client ID = MAC address for Microsoft clients). The reverse zone receives a PTR record (IP address and name) and a TXT record with the client ID. Uses RFC 2136 Dynamic DNS Update Protocol | Automatically registers DHCP clients in DNS and eliminates DNS management overhead. | |
Allows custom handling of individual DHCP packets as the DHCP server processes them. Extensions can be written in TCL scripting language or C, C++ compiled languages. | Supports additional levels of customization of individual DHCP clients. | |
Allows redundant DHCP servers to provide leases in the event of server failure | Provides a high-availability DHCP service. Clients requesting leases need not know or care which server is responding to their requests for leases. | |
Supports a variety of techniques for selecting DNS names:
| Flexibility | |
Can read client information from an LDAP directory; can update the directory with lease data. |
| |
Multiple network interfaces | Supports DHCP server systems with multiple network interfaces. | Reduces network traffic on multiple network segments. |
Supports the NetWare options in RFCs 2241 and 2242. | Supports customers with NetWare | |
Before the DHCP server offers an IP address to a DHCP client, the DHCP server pings the network. | Prevents duplicate IP address assignments. | |
Allows administrators to create DHCP address pools (scopes) that have addresses from multiple logical subnets that are on the same physical network. | Supports numerous network configurations and allows networks to be easily renumbered. | |
Supports all DHCP allocation methods | Supports all three allocation methods specified in RFC 2131:
| Flexibility and standards support |
Generates e-mail notices if the percentage or number of available addresses on one or more subnets falls below a configurable threshold | Alerts administrators of impending problems, allowing timely corrective action | |
Variable-length subnet masks | Address pools for different IP subnets can have different subnet masks. | Allows for flexible addressing schemes including OSPF configurations. |
| Registrar Architecture and User Interfaces | ||
All aspects of Network Registrar can be configured with the CLI. | Repetitive tasks can be automated with scripts. Configuration can be integrated with other network infrastructure applications. | |
Exports all active IP addresses into a specified database or CSV text file | Integration with a SQL database for customer network management applications, enhanced reporting capabilities on address usage, and the security of a SQL database with referential integrity | |
Graphical and command line interfaces | Both the GUI and CLI can be used to configure and monitor Network Registrar. | Flexibility. Ability to use the interface best suited to the task or user. |
Multithreaded | The DNS and DHCP servers can perform multiple tasks at the same time. | Improved performance and prevents DNS brownouts, takes advantage of multi-CPU systems. |
Both GUI and CLI can be run remotely. | Saves time and allows for central configuration and management. | |
Can import and export data in a variety of formats and reports. Both detailed and summary address data can be exported in comma-delimited format, which can be easily imported into databases and spreadsheets. | Supports integration with existing databases. Supports tracking of address space utilization. | |
Warns administrators of error conditions and possible problems with the DNS and DHCP servers. | Early alerts to problems conditions and a way to set thresholds in the event of increased demands. | |
Web browser reporting | Runs server status, address usage, lease status, and connection status between main and backup DHCP servers. | An easy way to monitor the status of Network Registrar. |
The Cisco Network Registrar documentation set consists of the following books:
If you are using the GUI to administer Network Registrar, you should consult the Network Registrar Concepts Guide to learn about the concepts, and the Network Registrar GUI User's Guide to learn how to configure specific features for your site.
If you are using the CLI to administer Network Registrar, you should consult the Network Registrar Concepts Guide to learn about the concepts, and the Network Registrar CLI User's Guide, and the Network Registrar CLI Reference Guide to learn how to configure specific features for your site.
Table 1-2 lists the DNS features and the documentation that contain information about them.
| Feature | GUI UG | CLI UG | CLI Ref | Concepts |
|---|---|---|---|---|
DNS subzone hiding | Chapter 2 |
| dns hide-subzones |
|
Dynamic updates | Chapter 1 | Chapter 3 | zone dynamic/scope dns-zone-name |
|
Import Zone files | Chapter 2 | Chapter 3 | import | Chapter 4 |
Internal Root | Chapter 2 | Chapter 3 | dns add RootHint |
|
IXFR | Chapter 2 | Chapter 3 | dns ixfr-enable |
|
NOTIFY | Chapter 2 | Chapter 3 | dns notify |
|
Preconfigured root server | Chapter 2 | Chapter 3 |
|
|
Removal of dynamic resource records |
|
| zone removeDynRR |
|
Resolution Exception | Chapter 2 | Chapter 3 | dns addException |
|
Round-robin | Chapter 2 | Chapter 3 | dns round-robin |
|
Specification of forward and reverse zones | Chapter 2 | Chapter 3 | dns addForwarder zone |
|
SRV records | Appendix A | Appendix A | zone add Host |
|
Subnet sorting | Chapter 2 | Chapter 3 | dns subnet-sorting |
|
Table 1-3 lists the DHCP features and the books that contain information about them.
| Feature | GUI UG | CLI UG | CLI Ref | Concepts |
|---|---|---|---|---|
All DHCP lease allocation methods | Chapter 3 | Chapter 4 | lease |
|
BOOTP and Dynamic BOOTP | Chapter 3 | Chapter 4 | scope bootp |
|
Class of Service | Chapter 3 | Chapter 4 | client-class | Chapter 2 |
DHCP custom options | Chapter 3 | Chapter 4 | custom-option |
|
DHCP option validity | Appendix C | Appendix C |
|
|
DHCP relay agent option |
| Chapter 4 | policy |
|
DOCSIS modem support |
| Chapter 4 | policy |
|
Dynamic DNS Updates | Chapter 3 | Chapter 4 | dhcp |
|
Extension points |
|
| Chapter 4 | Chapter 8 |
Failover |
| Chapter 4 | dhcp, scope, server | Chapter 3 |
Flexible name options | Chapter 3 |
| client host-name | Chapter 2 |
LDAP directory support |
| Chapter 4 | ldap | Chapter 7 |
Multiple Network Interfaces | Chapter 3 | Chapter 4 | dhcp-interface |
|
NetWare options | Appendix B | Appendix B | policy setOption |
|
PING before offering lease | Chapter 3 | Chapter 4 | scope ping-clients |
|
Secondary subnets | Chapter 3 | Chapter 4 | scope |
|
Utilization alerts |
|
| lease- | Chapter 4 |
Variable-length subnet masks | Chapter 3 | Chapter 4 | scope |
|
Table 1-4 lists the Registrar architecture features and the books that contain information about them.
DHCP
| Feature | GUI UG | CLI UG | CLI Ref | Concepts |
|---|---|---|---|---|
Remote configuration and monitoring | Chapter 4 | Chapter 5 |
|
|
Reports and data exports |
| Chapter 4 | export, report, and lease-notification | Chapter 4 |
SNMP notification |
| Chapter 4 | trap | Chapter 5 |
Web browser reporting | Chapter 4 | Chapter 5 |
|
|
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Thu Jul 13 11:04:19 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.