Cisco Cisco Prime Network Registrar 8.1 Technical References
Record Processing Rules
Cisco Prime Network Registrar IPAM 8.1.1 CLI and API Guide
307
Record Processing Rules
RR Type
Description
SOA
Data from the SOA record is used to update a domain in Cisco Prime Network Registrar IPAM. The
domain name is taken from the name field of the resource record. If the domain does not exist in
Cisco Prime Network Registrar IPAM processing for that record stops. If the domain exists in Cisco
Prime Network Registrar IPAM, data from the imported record is used to update the serial number
of the domain.
A
Data from A records is used to create resource record entries attached to domains in Cisco Prime
Network Registrar IPAM and additionally can create individual IP addresses and devices. Note that:
• if a domain name that matches the zone name is not defined in Cisco Prime Network Registrar
• if a domain name that matches the zone name is not defined in Cisco Prime Network Registrar
IPAM then processing of the resource record stops.
• if the name field contains the zone name, with additional fields to the left of the domain name
then an IP address and device will be created.
• if the name field matches exactly the zone name then no IP address and device will be created.
• if an address and device is to be created the DNS Listener will use the left most label of the
• if an address and device is to be created the DNS Listener will use the left most label of the
name field as the host portion of the FQDN for the host.
• if the address found in the rdata field of the resource record can be located within a block
defined in Cisco Prime Network Registrar IPAM, an IP address will be created using the rdata
field, and a device will be created using the name field. The device and IP address will also be
associated with the resource record in addition to the domain.
• if no block is defined that contains the address then the address device pair will not be created.
If the IP address already exists in a block defined in Cisco Prime Network Registrar IPAM and
there is no host name associated with the linked device, the host name will be taken from the
name field of the resource record.
PTR
Data from PTR records is used in the same way as data from A records with the exception that the
name and rdata field are swapped when creating an IP address and device.
NS
NS records are ignored by the DNS Listener daemon.
MX
MX records are imported into Cisco Prime Network Registrar IPAM and attached to the domain
supplied in the name field.
SRV
The data from SRV records are processed in the same way as other resource records with the
exception of the name field. The name field of SRV records specifies a service available for the
domain for which it is a part of. The service type and protocol is encoded in the left portion of its
name field. To avoid collision with the rest of the domain name space, leading under-bars are
prepended to the labels that describe the service. This practice is not always followed in the field and
so the DNSImport
CLI uses the following rule to determine where the domain name part of the
name field starts. It considers all the labels to the right of the right-most label that starts with an
underscore to be part of the domain name of the SRV record.
For example in the following SRV record:
For example in the following SRV record:
_ldap._tcp.pdc._msdcs.sw.cisco.com. 600 SRV 0 100 400 pdc.sw.cisco.com.
The service specification part would be:
_ldap._tcp.pdc._msdcs
and the domain name part would be:
sw.cisco.com.
All others
The domain name that the resource record will be placed in is taken from the name field of the
resource record after the left label has been removed. If the domain can not be found in Cisco Prime
Network Registrar IPAM processing of the resource record will stop. If the domain is found in Cisco
Prime Network Registrar IPAM, a resource record object is created using the data supplied by the
imported record, and it is linked to the domain.