Diagram Legend

CLOSE

Domain UPDATE Request

Function

The request is used to change the data for a domain.

Requirements

The request can only be processed if this domain already exists and is managed by the RegAcc placing the request.

Features

• The domain holder cannot be changed using an UPDATE command. You must use the CHHOLDER request for this.

• If you omit optional keywords, existing values for these keywords will be deleted or replaced with the default values.

• If new name servers are specified in a UPDATE request and the predelegation check fails, the request will be rejected with an ‘Error’ and the owner details will not be changed.

• A domain UPDATE request may change the order of the name servers. When querying with the domain INFO request, the order of the name servers will always be displayed in the same way. A further update may change the order again.

Verification

• A domain UPDATE request automatically triggers a risk assessment.

• A domain UPDATE is still possible if contacts without a phone number or email are used.

• When the request is forwarded to the risk assessment, a notification is generated when the new protocol status changes to “pendingCreate” (transition “failed” → “pendingCreate”).

Common Mistakes

• The domain stated in the request does not exist.
• One of the Contacts stated in the request does not meet the requirements of the role to be assigned to it.
• The Holder stated in the request is not identical with the current holder of the domain.

Process Diagrams

Examples

• xml
• k/v

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<registry-request xmlns="http://registry.denic.de/global/5.0" xmlns:domain="http://registry.denic.de/domain/5.0" xmlns:dnsentry="http://registry.denic.de/dnsentry/5.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <domain:update>
    <domain:handle>domain-example-nsentry.de</domain:handle>
    <domain:contact role="holder">DENIC-1000022-EXAMPLE-XML-PERSON</domain:contact>
    <domain:contact role="abusecontact">DENIC-1000022-EXAMPLE-XML-GR</domain:contact>
    <domain:contact role="generalrequest">DENIC-1000022-EXAMPLE-XML-ABUSE</domain:contact>
    <dnsentry:dnsentry xsi:type="dnsentry:A">
      <dnsentry:owner>domain-example-nsentry.de</dnsentry:owner>
      <dnsentry:rdata>
        <dnsentry:address>81.91.170.12</dnsentry:address>
      </dnsentry:rdata>
    </dnsentry:dnsentry>
  </domain:update>
  <ctid>xml-74ba5156</ctid>
</registry-request>

1
2
3
4
5
6
7
8
9
10
11
12
13
<?xml version="1.0" encoding="UTF-8"?>

<registry-response xmlns="http://registry.denic.de/global/5.0" xmlns:tr="http://registry.denic.de/transaction/5.0">
  <tr:transaction>
    <tr:stid>a503e644-635c-4253-b598-84d0c2296a97</tr:stid>
    <tr:result>success</tr:result>
    <tr:ctid>xml-74ba5155</tr:ctid>
    <tr:result>success</tr:result>
    <tr:message level="info" code="53000080014">
      <tr:text>Domain "Status" is "pendingCreate"</tr:text>
    </tr:message>
  </tr:transaction>
</registry-response>

1
2
3
4
5
6
7
Version: 5.0
Action: UPDATE
Domain: domain-example-nsentry.de
Holder: DENIC-1000022-EXAMPLE-PERSON
Generalrequest: DENIC-1000022-EXAMPLE-GR
Abusecontact: DENIC-1000022-EXAMPLE-ABUSE
Nsentry: domain-example-nsentry.de IN A 127.0.0.1

1
2
3
Result: success
STID: afdd1680-6d5e-4e94-a77a-8ef4a267c6b1
Info: 53000080014 Domain "Status" is "pendingCreate"

Request Parameters

A Domain UPDATE request is composed of the fields of the "Domain" data object and some other parameters, which are described below: