|
|
|
Action of periodically scanning dynamic updates to the DNS server for stale resource records and purging these records.
|
|
Administrative grouping of TCP/IP addresses on a DHCP server. Required for lease assignments.
|
|
DNS name server that gets it zone data from another name server authoritative for the zone. When a secondary master server starts up, it contacts the primary master, from which it receives updates.
|
|
A single LAN might have more than one subnet number applicable to the same LAN or network segment in a router. Typically, one subnet is designated as primary, the others as secondary. A site might support addresses on more than one subnet number associated with a single interface. You must configure the DHCP server with the necessary information about your secondary subnets.
|
|
Mechanisms that help select DHCPv4 scopes and DHCPv6 prefixes for clients and client-classes.
|
|
IP address of the server to use in the next step of the DHCP boot process. Sent in an RFC 2131 packet between the client and server.
|
|
DNS server that behaves like a stub resolver and passes most queries on to another name server for resolution.
See also
stub resolver.
|
|
DNS server that always forwards queries it cannot answer from its cache to a fixed list of forwarding servers instead of querying the root name servers for answers.
|
|
Simple Network Management Protocol messages that warn of server error conditions and problems.
See also
trap.
|
|
DNS Start of Authority resource record (RR). Designates the start of a zone.
|
|
Type of DNS resource record (RR) that allows administrators to use several servers for a single host domain, to move services from host to host with little difficulty, and to designate some hosts as primary servers for a service and others as backups.
|
|
dhcp or dns edit mode in which the data is stored on the CCM server, but not live on the protocol server.
See also
synchronous edit mode.
|
|
DNS server that hands off queries to another server instead of performing the full resolution itself.
|
|
Cisco Network Registrar use of on-demand address pools for entire subnet allocation of IP addresses to provisioning devices.
|
|
Separate IP address, or part of a host IP address, that determines the host address subnet. For example, 192.168.40.0 255.255.255.0 (or 192.168.40.0/24) indicates that the first 24 bits of the IP address are its subnet, 192.168.40. In this way, addresses do not need to be divided strictly along network class lines.
|
|
Set of IP addresses associated with a network number and subnet mask, including secondary subnets.
|
|
Attribute of the Cisco Network Registrar DNS server. By enabling it, the server checks the network address of the client before responding to a query.
|
|
A report that can be generated to determine how many addresses in the subnet were allocated and what the free address space is.
|
|
Action of dividing any network class into multiple subnetworks.
|
|
Limitation to the number of addresses service providers can determine for the DHCP server to give out to devices on customer premises, handled in Cisco Network Registrar by DHCP option 82 definitions.
|
|
Partition of a delegated domain, represented as a child of the parent node. A subzone always ends with the name of its parent. For example, boston.example.com. can be a subzone of example.com.
|
|
Dividing a zone into subzones. You can delegate administrative authority for these subzones, and have them managed by people within those zones or served by separate servers.
|
|
Aggregation of IP network addresses advertised as a single classless network address.
|
|
Synchronization can occur between the regional cluster and local clusters, the CCM and other protocol servers, failover servers, HA DNS servers, and routers.
|
|
dhcp or dns edit mode in which the data is live on the protocol server.
See also
staged edit mode.
|