Knowledge

DNS_ERROR_NOT_ALLOWED_UNDER_DNAME - 9570 (0x2562)

No data is allowed to exist underneath a DNAME record.

Updated: Feb 21, 2026

Introduction

This article provides a detailed technical explanation of the DNS_ERROR_NOT_ALLOWED_UNDER_DNAME error code, including its meaning and implications for developers.

Technical Background

The Domain Name System (DNS) is responsible for translating domain names into IP addresses. A DNAME record is used to create an alias for another domain name. However, certain restrictions apply to the placement of records within a DNS zone.

Error Details

The DNS_ERROR_NOT_ALLOWED_UNDER_DNAME error code indicates that an attempt was made to add or modify data under a DNAME record in a DNS zone. According to DNS standards and implementation practices, no other resource records are allowed to exist directly beneath a DNAME record because the DNAME record itself is intended to be a pointer to another domain name.

Common Causes

  • Attempting to create or modify an A, AAAA, MX, CNAME, or any other type of DNS record under a DNAME record.
  • Incorrectly configured DNS zone files that include conflicting records.

Real-World Context

This error typically occurs during the management and maintenance of DNS zones. Administrators must ensure that no data is placed directly beneath a DNAME record to maintain proper DNS functionality.

Is This Error Critical?

The criticality of this error depends on the specific operation being performed. If an attempt is made to add or modify data under a DNAME, it can lead to incorrect resolution and potential service disruptions. However, if the operation was intended to be performed at a different level in the DNS hierarchy, the impact may be minimal.

How to Diagnose

  1. Review Operation Context: Verify that the operation being attempted is appropriate for the current context within the DNS zone.
  2. Validate Parameters: Ensure that all parameters passed to the API or command are correct and do not include any records under a DNAME.
  3. Confirm Object Types: Confirm that the object types involved in the operation match the expected types, such as ensuring no A or AAAA records are placed under a DNAME record.
  4. Verify Input Data: Check for any corrupted data or incorrect configurations within the DNS zone files.

How to Resolve

  1. Correct Parameter Usage: Ensure that all parameters passed to the API or command are appropriate and do not include any records under a DNAME.
  2. Adjust Operation Context: If necessary, adjust the operation context to ensure it is performed at an appropriate level in the DNS hierarchy.
  3. Restore Data: If data corruption is suspected, restore from backups or correct the zone files as needed.
  4. Retry Operation with Valid Inputs: After making corrections, retry the operation using valid inputs.

Developer Notes

Developers should be aware of the restrictions on DNAME records and ensure that their operations do not violate these rules to avoid encountering this error.

Related Errors

  • DNS_ERROR_DNSSEC_FAILED (9013): Indicates issues with DNS Security Extensions (DNSSEC).
  • DNS_ERROR_RCODE_REFUSED (9568): Indicates a refusal by the server to perform an operation due to policy or configuration.

FAQ

Q: What does the DNS_ERROR_NOT_ALLOWED_UNDER_DNAME error mean?

A: This error indicates that data cannot be placed directly under a DNAME record in a DNS zone. Only a DNAME record is allowed at this level.

Q: How can I prevent this error from occurring?

A: Ensure that all operations are performed according to the correct hierarchy within the DNS zone and do not include any records under a DNAME record.

Summary

The DNS_ERROR_NOT_ALLOWED_UNDER_DNAME error code is specific to DNS management and indicates an attempt to place data under a DNAME record. Understanding this error and its implications is crucial for maintaining proper DNS functionality and avoiding service disruptions.