Cisco Cisco Prime Network Registrar 8.3 Release Notes
4
Cisco Prime Network Registrar 8.3.3 Release Notes
Cisco Prime Network Registrar Bugs
The synchronization between version 8.3 and pre-8.3 local clusters must be done from an 8.3 regional cluster. Cisco
Prime Network Registrar 8.3 protocol servers interoperate with versions 7.2 or later except as noted below.
Prime Network Registrar 8.3 protocol servers interoperate with versions 7.2 or later except as noted below.
Cisco Prime Network Registrar 8.2 and later DHCPv4 failover servers do not interoperate with versions prior to 8.2.
Therefore, if you are upgrading from 8.1 and earlier to 8.2 and later, you must upgrade both failover partners. Also,
any firewalls need to be updated to allow TCP traffic on the failover port (547). And, for 8.2 and later failover extends
to DHCPv6.
Therefore, if you are upgrading from 8.1 and earlier to 8.2 and later, you must upgrade both failover partners. Also,
any firewalls need to be updated to allow TCP traffic on the failover port (547). And, for 8.2 and later failover extends
to DHCPv6.
The HA protocol version has been updated in Cisco Prime Network Registrar 8.0 and communications with earlier
versions is not supported.
versions is not supported.
Caution:
By the nature of the EDNS0 protocol, Cisco Prime Network Registrar 8.3 DNS servers interoperate with earlier
versions of Cisco Prime Network Registrar DNS (and third party DNS vendors). EDNS0 defines the interoperability
with DNS servers that do not support EDNS0. Cisco Prime Network Registrar 8.3 DNS adheres to the RFC and
consequently interoperates with earlier versions of Cisco Prime Network Registrar.
versions of Cisco Prime Network Registrar DNS (and third party DNS vendors). EDNS0 defines the interoperability
with DNS servers that do not support EDNS0. Cisco Prime Network Registrar 8.3 DNS adheres to the RFC and
consequently interoperates with earlier versions of Cisco Prime Network Registrar.
Cisco Prime Network Registrar 8.3 DDNSv6 interoperates with Cisco Network Registrar 7.0 and later DNS servers
because of the use of the DHCID RRs (in place of TXT RRs for DDNSv6).
because of the use of the DHCID RRs (in place of TXT RRs for DDNSv6).
Cisco Prime Network Registrar 8.3 does not interoperate with Cisco Prime Network Registrar IPAM 8.1.1 or 8.1.2.
An updated version of Cisco Prime Network Registrar IPAM is required to interoperate with Cisco Prime Network
Registrar 8.3.
An updated version of Cisco Prime Network Registrar IPAM is required to interoperate with Cisco Prime Network
Registrar 8.3.
Cisco Prime Network Registrar Bugs
For more information on a specific bug or to search all bugs in a particular Cisco Prime Network Registrar release, see
.
This section contains the following information:
Resolved Bugs
lists the key issues resolved in the Cisco Prime Network Registrar 8.3.3 release.
Table 1
Resolved Bugs in Cisco Prime Network Registrar 8.3.3
Bug ID
Description
DNS HA main may stop communicating with its partner under load
DNS HA main refuses connection from HA partner and/or drops updates
Permanent v4 leases have incorrect renewal and rebinding times
GNU glibc send_dg Function File Overwrite Vulnerability
GSS Zone transfer via TCP sends last packet unsigned
View zone copy fails to copy RRs for reverse zones
Web UI connection never times out
XMLSoft libxml2 Library XML File Parsing Denial of Service Vulnerability
Server grants wrong subnet if requested length > 31
CDNS server crashes when 32
nd
CDNS64 object is created
CCM uses 100% CPU when loading Zone Dist page with views