Error Messages - BlueCat Address Manager - 9.2.0

Address Manager Administration Guide

Locale
English (United States)
Product name
BlueCat Address Manager
Version
9.2.0

The following contains error messages that might be displayed in the Address Manager user interface.

E-01: CNAME Record Looping
Description: A CNAME record might point to another and then that record points to the initial value. This is a variant of the CNAME chaining rule.
Severity: Error
Effect Deployment fails.
Association: All CNAME records involved in the loop.
How to Detect: Identify the CNAME record that links to a second CNAME record. Follow the link to determine if the reference is accurate.
Fix Link the CNAME record to an existing host record or external host record. If the record doesn't exist, create it.

 

E-02: Deployment Profile (Zone/View) without master role
Description: Deployment role of secondary exists without a primary.
Severity: Error
Effect Deployment fails.
Association: View/Zone (deployable or non-deployable) where role is defined.
How to Detect: Look for a view or zone with no primary or hidden primary deployment role.
Fix Assign a deployment role of primary or hidden primary in addition to or instead of the secondary role.

 

E-03: Validate Generic Records
Description: Generic record contains invalid data from previous versions of Address Manager that didn't perform strict validation.
Severity: Error
Effect Deployment fails.
Association: Generic record
How to Detect: The RDATA value of the generic record should be validated for compliance, and the record type should be verified to ensure it isn't one of the following reserved types:
  • SOA
  • SIG
  • TSIG
  • TKEY
  • IXFR
  • AXFR
Types should also be verified against known types in the BlueCat DNS API. Any record that contains invalid RDATA or unsupported record type should be flagged.
Fix Correct the record that's generating the error.

 

E-04: Invalid DHCP Match Class Values within DHCP Match Class
Description: Match values in a match class are invalid based on conditions in the class. If a user changes the match condition of a match class, without updating the match values, then the match values become invalid.
Severity: Error
Effect Deployment fails.
Note: The Address Manager user interface doesn't allow you to change the match conditions so that they conflict with the match values. To override this behavior, select the Ignore error check with existing match values and update. Then match values should be corrected manually.
Association: Configuration
How to Detect: Check the match values within a match class based on the match condition.
Fix Ensure that the match values in a match class are valid.

 

E-05: Reverse Mapping Zones without Master
Description: Reverse mapping zones without a primary role for same view.
Severity: Error
Effect Deployment fails.
Association: Reverse mapping zones (IPv4 block or network) where role is defined.
How to Detect: Look for a view or zone with no primary or hidden primary deployment role.
Fix Assign a primary deployment role to the IP block or network.

 

E-06: Enum Zones without Master
Description: Deployment role of secondary exists without a primary.
Severity: Error
Effect Deployment fails.
Association: ENUM zone (deployable and non-deployable) where role is defined.
How to Detect: Examine the deployment roles for an ENUM zone and flag if no primary (normal or hidden) is present.
Fix Set a primary or hidden primary deployment role at the ENUM zone or set a primary or hidden primary deployment role at the view level so that the ENUM zone inherits the correct roles.

 

E-08: Configuration using DNS ACLs can't be deployed to DNS/DHCP Server pre-v8.0.0
Description: Attempt to deploy DNS configuration referencing custom DNS ACLs to DNS/DHCP Server v7.1.1 or earlier is blocked.
Severity: Error
Effect Deployment fails.
Association: DNS/DHCP Server software version 7.1.1 or earlier
How to Detect: Verify that custom DNS ACLs don't have linked objects that are deployable to DNS/DHCP Server v7.1.1 or earlier.
Fix Upgrade to DNS/DHCP Server v8.0.0 or greater, or modify DNS deployment options and DNS64 configurations set to deploy to DNS/DHCP Server v7.1.1 or earlier by removing references to custom DNS ACLs.