Possible responses in reaction to customer applications
The procedure for transmitting results of time-consuming operations
Messages you will receive from the DRS without prior request
Link Info
In the following, the different types of responses and messages are listed
which are generated by the DRS robot.
It is also explained under which circumstances the response is given and
an example of what the response might look like.
The exact meaning of the
keys and
the possible values can be found here.
If you send an e-mail application form to the DRS, e.g. to request the
registration or the transfer of a domain,
you will receive a response of the DRS robot with the result
of the application. The same is true for applications which can not be carried
out directly (e.g. when starting a domain transfer).
Syntactical errors in the e-mail application form
If syntactical errors are ascertained by the parser already, e.g. missing fields
or fields including invalid values, an appropriate message describing the
errors will be sent.
In the example below the country field was falsely filled with "GERMANY"
instead of "DE" in section 2 of the application form. Besides that
the required phone number is missing:
For .de domains, there is the particularity that a domain can possibly be
registered but not delegated, if the name server configuration was not set up
correctly. This means that the domain can not be used yet and the customer has
to configure the name server correctly within a period of one month; otherwise
the domain will be released to be registrable by others. The appropriate
DRS response includes the result code 23300, which is dedicated to this
situation, as well as an information according the domain's date of deletion
provided in the "nested" key-value pair
expire.date: 2003-11-28T23:00:00.0Z
If an error occurs when starting a transfer, the DRS response provides
indications of the failure. In the example below, a transfer for the appropriate
domain is already underway.
The start of a transfer results in a failure, if the authorization information
to initiate the transfer (AuthInfo), which is required by most of the
registries, is invalid:
A successfully started domain transfer to Knipp can result in a failure,
if for example the present registrar declines the transfer; in this case
an appropriate answer would be as follows:
The .de registry completes domain registrations
asynchronously, that is the result of a domain application
cannot be determined immediately, and may possibly not be available until
hours later. Therefore the DRS's first response to an application of
a .de domain is only a message about the
initiation of the process:
Some registries still require manual interaction of the support staff.
Similarly to the above case of .de domains, the result of a domain application
is possibly only available hours later.
Therefore the DRS's first response to an application of such a domain is simply
a notification that the command has been received and processed successfully:
In certain cases the DRS has to send e-mails, even if they are not a direct or
indirect response to a customers' application. These "unrequested" DRS messages
also include a machine-readable part.
Start of an outgoing domain transfer
If the DRS receives a notification by a registry that indicates the transfer
of a domain, it will send an e-mail to inform the respective customer.
In the following example, the transfer of the
domain acme.com away from Knipp was started.
The deadline information says that the customer has to acknowledge or decline
the transfer until 4.11.2003 11:10h. If the customer does not react in
this period of time, the transfer will automatically be acknowledged.