Table of contents

For each job sent to AutoDNS, the system responds with feedback on the processing status of the job in the system (job) and the status of completion of the specific job (task). Depending on the job type, only system responses are returned in real time or additional system notifications. The delivery type email, push or polling can be selected for the system notifications.

Message types in AutoDNS

System responses

  • Realtime system responses: These responses are returned directly after an request has been sent.

    • Success (S): Request was successfully completed.

      Error (E): Error during processing with specific error message (EF, e.g. “EF0101”).

      Notify (N): Order has been accepted and is being processed further. The final status is transmitted later via notifications (Success/Error). Example

Difference between status code and error code

Status codes always begin with an S, E or N and describe the status of the job.  Error messages begin with an EF and describe the error that has occurred.

Notifications

  • Internal notifications via polling, push or email: Result from orders with “Notify” status (N). These notifications transmit the final status (success/error) after processing has been completed.

  • External notifications: External events (e.g. from a registry) trigger messages that are not assigned to an internal job.

Notification types

Internal notifications via polling, push or email

These messages are directly associated with a job in the system.

  • Status types

    • Success (S): Job was succesfully processed

    • Failed (F): Job failed

    • Running: Only for special tasks, e.g transferIn. Indicates, that the job ist still in process.

See: Request examples for  Domain jobs, contact jobs, ownerchange jobs und transfer jobs.

Externally triggered notifications

These messages are triggered by external events without reference to an internal task.


List of external notifications

TransferOut

  • transfer_start - Start of an outgoing domain transfer.
  • transfer_autoack - Automatic confirmation of an outgoing domain transfer (AutoAck). Only for gTLDs.
  • transfer_autonack - Automatic refusal of an outgoing transfer (AutoNack).
  • transfer_reminder - Reminder of an ongoing transfer.
  • domain_away - Deletion of a domain from the database, e.g. in the case of domain transfers without the participation of the registrar.

Domain AutoUpdate

  • autoupdate_dns_error- Successful execution of an automatic update. Only for .de domains. An automatic update is only performed if the connectivity check, which is part of the registration process, has failed.
  • autoupdate_dns_success - Successful connectivity check.
  • autoupdate_deferred_success - Successful deferred AutoUpdate.
  • autoupdate_deferred_error - Failed deferred AutoUpdate.

OCVAL (OwnerC validation)

  • ocval_reminder - Reminder to deactivate the domain (5 days before).
  • ocval_activation - Information about the disconnection of the name servers and the non-accessibility of the domain.
  • ocval_deactivation - Information about the reconnection of the nameservers and the re-accessibility of the domain.

Purge notifications

  • zone_deleted - zone successfully deleted

  • contact_deleted - contact successfully deleted

Examples for messages

System responses

 XML

        <status>
            <type>success</type>
            <code>S0301</code>
            <text>The domain contact was updated successfully.</text>
        </status>

JSON

    "status": {
        "resultCode": "S0301",
        "text": "The domain contact was updated successfully.",
        "type": "SUCCESS"

External notifications

 TransferOut (JSON)

{
    "notification": {
        "type": "transfer_start",
        "domain": "example.com",
        "timestamp": "2024-12-30T12:00:00Z"
    }
}

Zone purge (XML)

  <notification>
    <type>zone_deleted</type>
    <zone>example.com</zone>
    <timestamp>2024-12-30T12:00:00Z</timestamp>
</notification>

Messaging process

  • Job start

    • System response „success“, „error“ oder „notify“ is returned.
  • Notify process
    • With the  “Notify” status of the sxstem response, the final status "success" or "error" is transmitted via a notification.
  • External events

    • Direct notification of events outside the system (e.g. transferOut, zone purge).

See: Schematic representation of order processing for domains and domain contacts, zones, users and inquire jobs, transfer and ownerchange.

Notification structure and keywords (XML)

Keyword OccursDescription

summary

1

Number of Notifications in the queue

message

1

Message object

message / id

1

Message ID. This is needed for confirmation (PollACK)

message / owner

1

Owner of the notification:

message / owner / user

1

User name

message / owner /context

1

User context = Personal AutoDNS ID

message / created

1

Notification date

message / job

0 - 1

Order object (for job messages)

message / job / domain

0 - 1

Domain object

message / job / handle

0 - 1

Contact object

message / job / ctid

0 - 1

Order ID that the customer has assigned to the order.

message / job / transfer

0 - 1

Extended information on transfers or owner changes.

message / job / transfer / status

0 - 1

Transfer status. Additional information about the status is sent during transfers and owner changes. This is purely informative and depends on the respective TLD.

Whether an order is completed is recognized by the order status (error/success).

Possible transfer statuses

  • start

  • failed

  • nack

  • ack

  • foa1-sent

  • autoupdate_success

  • autoupdate_failed

message / job / system_notify


Additional information from the system

message / job / nic_response


Additional information from the NIC

message / job / imported

0 - 1

If data is imported during an order, it is indicated here.

message / job / imported / ownerc

0 - 1

The ID of the contact that was imported (e.g., for EU, ES transfers).

 For all order types, this tag must be checked.

message / job / status

1

Order status object

message / job / status / type

1

Order status

  • success

  • error

  • notify

message / job / status / code

1

Notification code

message / job / status / text

0 - 1

Notification text

message / job / status / object

0 - 1

Object

message / job / status / object / type

1

Object type

message / job / status / object / value

1

Object value

message / notify

0 - 1

Object of the notification message

message / notify / type

1

Notification type, e.g., "transfer_start"

message / notify / domain

0 - 1

Domain object

message / notify / handle

0 - 1

Contact object

message / notify / transfer

0 - 1

Extended information on transfers or owner changes

message / notify / transfer / start

0 - 1

Date of transfer start

message / notify / transfer /end

0 - 1

Date of transfer end

message / notify / transfer / autonack

0 - 1

Date of automatic NACK

message / notify / transfer / autoack

0 - 1

Date of automatic ACK

message / notify / transfer /reminder

0 - 1

Date of the reminder notification

message / notify / transfer / gaining_registrar

0 - 1

Future registrar

message / notify / transfer / loosing_registrar

0 - 1

Previous registrar

message / notify / status

1

Status object

message / notify / status / type

1

Order status. In polling notifications, always "success".

message / notify / transfer / code

1

Notification code

message / notify / transfer / text

0 - 1

Notification text

message / notify / transfer / object

0 - 1

Object

message / notify / transfer / object /type

1

Object type

message / notify / transfer / object /value

1

Object value