Lease Query Autoconfiguration
The RDU performs name resolution to determine the IP addresses of Network Registrar servers to which it sends lease queries. In case of a DNS failure, lease queries can fail. In Prime Cable Provisioning, you can directly configure the IP addresses of Network Registrar servers in a provisioning group to which the RDU must send lease query requests.
When you enable automatic configuration, the RDU adjusts its lease query configuration to set both IPv4 and IPv6 address lists from the Network Registrar servers in the provisioning group. It performs this task after comparing the current information registered with the server to the information stored in the RDU database. If the Prime Cable Provisioning Network Registrar extensions have moved from one provisioning group to another, the lease query configuration is changed to delete:
IP addresses that are present in the lease query configuration on the previous provisioning group object.
IP addresses that are no longer present in the IP address list.
The RDU searches the lease query configuration to verify if the provisioning group is configured to use the specified extension. If the provisioning group is not configured to use the extension, the RDU selects an address from the addresses being registered with the Network Registrar server and adds to the provisioning group’s lease query configuration.
If you disable this autoconfiguration, the RDU does not change its lease query configuration upon registering with the Network Registrar server. This feature is, by default, enabled.
To enable or disable autoconfiguration of lease query addresses in a provisioning group, you can set the LeaseQuery AutoConfig option from the administrator user interface. See Monitoring Provisioning Groups.