Reference: Resource Records with Windows DNS - BlueCat Address Manager - 8.3.1

Address Manager Administration Guide

prodname
BlueCat Address Manager
version_custom
8.3.1

Lists of Windows DNS resource records.

You can create and edit resource records in Address Manager. You can also import resource records from a Windows DNS server. For complete details, refer to Managing Resource Records.

Resource Record Types—Windows

Address Manager supports the following types of resource records. After you switch a Managed Windows server to Read-Write mode, any new resource records added to a zone can be deployed to that server.

Resource Record Type Description
Host Record Designates an IP address for a device. A new host requires a name and an IP address. Multiple addresses may exist for the same device.
CNAME Alias Record Specifies an alias for a host name. The alias record type requires a name.
TXT Text Record Associates arbitrary text with a host name. A text record includes name and text information. This record is used to support record types such as those used in Sender Policy Framework (SPF) e-mail validation.
HINFO Host Info Record Specifies optional text information about a host. The host info record includes CPU and OS information.
Service Record Defines services available within a zone, such as LDAP. A service record requires a name, priority, port, and weight. A lower priority value indicates precedence. The port value indicates the port on which the service is available. The weight value is used when multiple services have the same priority value; a higher weight value indicates precedence.
Mail Exchanger Record Designates the host name and preference for a mail server or exchanger. An MX record requires a name and a priority value. Priorities with a lower numeric value are chosen first in assessing delivery options.

Generic Resource Record Types—Windows

Generic resource records are used to manage Resource Record types that are not natively managed in Address Manager. You can manage the following types of Generic Records to a Managed Windows server.

Record Type Description
A (IPv4 Address) Maps hosts to IPv4 addresses.
A6 (IPv6 Address) Maps hosts to IPv6 addresses.
AAAA (IPv6 Address) Maps hosts to IPv6 addresses. Normally, this record is created by adding a host record in Address Manager and linking it to an IPv6 address.
PTR (Pointer) Provides a reverse mapping of an IP address to a host name.
RP (Responsible Person) Associates an email address and optional human-readable text data with a host.
WKS (Well-Known Service) Describes the well-known services supported by a particular protocol by a host.

Unsupported Resource Records—Windows

Address Manager does not support the deployment of the following Generic resource record types to Managed Windows servers:

  • AFSDB, APL, CERT, DNAME, DS, DHCID, IPSECKEY, ISDN, KEY, KX, LOC, MB, MG, MINFO, MR, NSAP, PX, RT, SINK, SPF, SSHFP, X.25.

Address Manager does not support the import or notification of the following resource record types from Managed Windows DNS servers:

  • AFSDB, ATMA, DNAME, DHCID, MG, MB, MINFO, NXT, KEY, RT, MR, SIG, X.25.

Importing Resource Records—Windows

Resource records are included during the initial import of a zone from a Managed Windows DNS server. After the initial import, resource records are no longer included in subsequent imports of the same zone, but they are sent to Address Manager through the notification mechanism instead.
Note: If the parent IPv4 or IPv6 network does not exist in Address Manager, the host records are skipped during import and are not brought into Address Manager. Behavior during notification is somewhat different. If the parent network does not exist, Address Manager creates a generic record in the zone to represent the host record.
  • If the DDW server is disabled or not available, and resource records data between the Windows zone and Address Manager is out-of-synch you can reconcile resource records by selecting the Re-import Resource Records check box when you perform the next import.
  • If you select this option, all existing resource records are deleted from all zones for which the server is master, and then re-added. While it is rarely necessary to perform a forced import, it is useful in the event that the DDW server fails and needs to be replaced. While the DDW server is not functioning, Address Manager no longer receives notifications. To reconcile all resource records, a re-import is necessary.

Deploying Resource Records

When you deploy a DNS zone with either a Master or Active Directory Integrated Master deployment role, resource records that exist in the zone on Address Manager and that are supported by both Address Manager and Windows DNS are created on the Windows server.
Note: On the very first deployment of a zone, if a resource record that is supported by both Address Manager and Windows exists on Windows but not on Address Manager, it is deleted from the Windows server. On all subsequent deployments, records that exist in Windows but not on Address Manager are not deleted.

Linked Resource Records

Address Manager links host records to IP addresses, and CNAME, MX, and SRV records to their associated host record. This ensures referential integrity, and helps prevent stale resource records in the DNS zone. For example, if you delete a host record, you also delete any CNAME, MX, and SRV records that are linked to that host.

In Address Manager, the following DNS objects are linked:

  • Host records are linked to IP addresses. The IP network must exist in Address Manager before you can create the host record.
  • CNAME (alias) are linked to either existing host records, existing CNAME records or to external host records.
  • MX records are linked to either existing host records or to external host records.
  • SRV records are linked to either existing host records or to external host records.
    Note: Deleting a dynamic A or AAAA host record on a Managed Windows server deletes the host record and any linked records from Address Manager. However, the linked records still exist on the Managed Windows server until the next deployment.