EDNS1 - Error in reading a DNS zone.
Explanation: An error occurred while reading a DNS zone during export.
A possible cause is that the zone no longer exists in the tree.
Action: Refresh the tree to make sure the zone exists.
EDNS2 - Error in obtaining zone summary record.
Explanation: An error occurred while obtaining a list of DNS zones.
This is an internal database error that might be caused by corruption in the
database or by a network problem.
Action: Try to reproduce the problem and report it if it persists.
EDNS3 - Error in obtaining resource record summary record.
Explanation: An error occurred while obtaining a list of resource records.
This is an internal database error that might be caused by corruption in the
database or by a network problem.
Action: Try to reproduce the problem and report it if it persists.
EDNS4 - Error in obtaining DNS server summary record.
Explanation: An error occurred while obtaining a list of DNS servers.
This is an internal database error that might be caused by corruption in the
database or by a network problem.
Action: Try to reproduce the problem and report it if it persists.
EDNS5 - Error in obtaining resource record set summary record.
Explanation: An error occurred while obtaining a list of resource record
sets. This is an internal database error that might be caused by corruption
in the database or by a network problem.
Action: Try to reproduce the problem and report it if it persists.
EDNS100 - Failed to create zone, resource record set, or resource record.
Explanation: A general error occurred indicating a problem creating
a DNS zone. This error might occur during the creation of a zone or its corresponding
resource record sets and resource records. A possible cause is the user might
have tried to re-create an existing zone.
Action: Make sure the zone record does not exist in the tree before
creating it.
EDNS102 - Cannot modify the resource record because the A resource record does not exist for the specified domain name.
Explanation: While modifying a resource record that requires
a domain name, the domain name did not have a corresponding A resource
record.
Action: Make sure an A resource record exists for the domain name
being entered.
EDNS103 - Cannot create the resource record because an A resource record does not exist for the specified domain name.
Explanation: While creating a resource record that requires a
domain name, the domain name did not have a corresponding A resource record.
Action: Make sure there is an A resource record for the domain name
being entered.
EDNS104 - Cannot create the resource record because the record already exists.
Explanation: Creating a duplicate resource record is not valid.
Action: Make sure the resource record does not exist before creating
it.
EDNS105 - You have exceeded the maximum limit of 64 characters for a domain name. Please enter a domain name within this limit.
Explanation: The domain name is used to create an object in eDirectoryTM.
Because eDirectory limits the naming of an object to 64 characters long, the
domain name is restricted to this rule.
Action: Shorten the domain name to less than 65 characters.
EDNS108 - A zone with the same name already exists.
Explanation: Cannot have a duplicate zone name on the same tree.
Action: Make sure the DNS zone being created does not exist.
EDNS300 - You did not enter a valid DNS BIND file. Enter a BIND formatted DNS file.
Explanation: There is a problem reading the file or the file
does not have at least an SOA record.
Action: Use the browse button to find a valid DNS BIND file.
EDNS301 - Cannot import to an existing zone.
Explanation: The zone is already on the tree.
Action: Delete the existing zone and import the current one, or select
a different DNS BIND file to import.
EDNS302 - Error occurred while creating a zone.
Explanation: The SOA resource record in the BIND file might not
have the correct number of parameters or the correct values.
Action: Check the file for the SOA resource record to verify that
it contains the correct information.
EDNS303 - File is not a DNS BIND formatted file.
Explanation: There is a problem reading the file or the file does
not have at least an SOA record.
Action: Use the Browse button to find a valid DNS BIND file.
EDNS304 - You did not enter a valid context where the zone data is to be stored. Enter a valid context before proceeding.
Explanation: The context field was left empty or a context was
entered that does not exist.
Action: Browse the tree and select a context for the zone records
to be stored.
EDNS305 - You did not enter a valid DNS or NCP server to manage the zone. Browse the tree for the server or, if you are not sure, leave the field empty before proceeding.
Explanation: The DNS Server field is empty or you have entered a server
that does not exist.
Action: Use the browse button to select an existing DNS or NCPTM
Server object.
EDNS306 - DNS server record for the selected NCP server already exists. Select a different server. If you choose to continue, the DNS server record will not be created for you.
Explanation: The DNS server record selected already exists.
Action: If you want to create a new DNS server select a different NCP
Server object. If you want to use the existing one, no action is necessary
because the record already exists.
EDNS308 - If the zone type is secondary, a valid value must be entered for master server IP address.
Explanation: The Name Server IP Address field was left empty or an
invalid IP address value was entered.
Action: Enter the correct IP address of the master server for this
zone.
EDNS310 - A DNAME resource record already exists for this owner name.
Explanation: User tried to create another DNAME record for an owner
name.
Action: Make sure that the owner name does not have a DNAME resource
record associated with it before creating a DNAME record.
EDNS311 - A CNAME resource record already exists for this owner name.
Explanation: User tried to create another CNAME record for an owner
name.
Action: Make sure that the owner name does not have a CNAME resource
record associated with it before creating a CNAME record.
EDNS312 - An owner name cannot have both CNAME and other resource records.
Explanation: User tried to create a resource record for the owner
name which already has a CNAME record or vice versa.
Action: Make sure that the owner name does not have a CNAME resource
record associated with it before creating another record or vice versa.
EDNS316 - Allow Update List cannot be configured for a Secondary zone.
Explanation: User tried to save a secondary zone configuration with
allow-update option value set.
Action: Remove the value for allow-update option and try again.
EDNS317 - The option {0} cannot be configured for a Primary zone.
Explanation: User tried to save a primary zone configuration with
values set for options that are not meant for primary zone.
Action: Remove the values for the options showed in the error dialog
box and try again.