Create reseller[Link]

Purpose

create a reseller that can be linked to a domain

DNS Belgium uses the organisation extension for resellers, based on the relevant RFC’s:

The implementation of the organisation extension is limited to the reseller role, organisation name and organisation website. DNS Belgium doesn’t require more information and any extra information provided by the registrar will be ignored.

Some components of the command need further explanation:

  • <org:id> is required. Contains the unique reference to the reseller chosen by the registrar.

  • <org:role> is required. Only type ‘reseller’ is allowed. Multiple roles are not supported and will be ignored. Status and id are not supported and will be ignored.

  • <org:postalInfo> contains the address information of the reseller. DNS Belgium only accepts type ‘loc’ with UTF-8 character set (containing non-ascii characters), the set of characters allowed are the characters from iso-8859-1 and iso-8859-15; if ‘int’ is specified as a type, this will be rejected as a policy error. Only 1 postalInfo block is accepted.

  • <org:name> is required. Contains the organisation name of the reseller.

  • <org:url> is required. Contains the website of the reseller.

All other attributes are not supported and will be ignored.

Please refer to the examples to see a complete request.

Examples[Link]

A create reseller command looks like:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
  <command>
    <create>
      <org:create xmlns:org="urn:ietf:params:xml:ns:epp:org-1.0">
        <org:id>reseller01</org:id>
        <org:role>
          <org:type>reseller</org:type>
        </org:role>
        <org:postalInfo type="loc">
          <org:name>My first Reseller</org:name>
        </org:postalInfo>
        <org:url>https://www.the-reseller-company.be</org:url>
      </org:create>
    </create>
    <clTRID>aa1c9912-21db-4984-a311-c675aea2f9b8</clTRID>
  </command>
</epp>

In case of successful creation, the EPP server responds with a standard EPP response message:

<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
  <response>
    <result code="1000">
      <msg>Command completed successfully</msg>
    </result>
    <trID>
      <clTRID>aa1c9912-21db-4984-a311-c675aea2f9b8</clTRID>
      <svTRID>dnsbe-121564676</svTRID>
    </trID>
  </response>
</epp>