This repository has been archived by the owner. It is now read-only.
Public specification for the DK Hostmaster mail based domain registration service
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
3.04
4.00
5.00
LICENSE
README.md
README_3.04.md
README_4.00.md

README.md

DK Hostmaster Mailform Service Specification


⚠️ This service has been decommissioned June 30, 2018 ⚠️

Please refer to the EPP service for implementation of domain name registration towards DK Hostmaster A/S.

Please contact us if you have any questions:

tech@dk-hostmaster.dk


Public specification for the DK Hostmaster mailform domain registration service.

2017/12/03 Revision: 5.0

Table of Contents

Introduction

This documentation describes the current version 5.00, earlier revisions might still be actively supported for for documentation on these revisions please see:

About this Document

This specification describes version 5 (5.X.X) of the service and version 5.XX of the form implementations. Future releases will be reflected in updates to this specification, please see the document history section below.

Any future extensions and possible additions and changes to the implementation are not within the scope of this document and will not be discussed or mentioned throughout this document.

This document is owned and maintained by DK Hostmaster A/S and must not be distributed without this information.

All examples provided in the document are fabricated or changed from real data to demonstrate commands etc. any resemblence to actual data are coincidental.

Printable version can be obtained via this link, using the gitprint service.

Document History

  • 5.0 2016-12-28

    • Documentation migrated from proprietary text/HTML files to dedicated Github repository, we reset history and start from version 5.00 to be consistent with earlier documentation, API revisions and service versions.
    • The revision introduces the pre-activation token
  • 4.0 2016-12-28

    • Documentation migrated from proprietary text/HTML files to dedicated Github repository
    • This revision introduces DNSSEC and keyholder user
  • 3.0 2016-12-28

    • Documentation migrated from proprietary text/HTML files to dedicated Github repository

The .dk Registry in Brief

DK Hostmaster is the registry for the ccTLD for Denmark (dk). The current model used in Denmark is based on a sole registry, with DK Hostmaster maintaining the central DNS registry.

Mail-form Service

The DK Hostmaster mail-form service is a service offered to external parties offering registration of danish domain names on the ccTLD .dk to registered registrars.

The service requires the use of and possible development of client-side software and integration. This is beyond the scope of this specification as the API and other assets for assisting in this are the primary object of this document.

In addition to the assets, DK Hostmaster aims to assist client, users and developers of client software with integration towards DK Hostmaster and therefore provide facilities to ease this integration.

The Form

The top of the form reads [CPAI]. The 4 letters describe 4 columns that continue down the form. They stand for:

  • Company (Danish: Virksomhed)
  • Danish Public sector organisation (Danish: Offentlig virksomhed)
  • Association (Danish: Forening)
  • Individual (Danish: Privatperson)

The columns determine how the individual sections are to be filled in. If, for example, the registrant is a company, then column 'C' must be used for section 4. If the billing contact is a Danish public sector organisation, then 'P' must be used when filling in section 6.

Field 2c must, only contain an 'N'.

Field 2d concerns the billing contact and may be used only if the billing contact is a Danish public sector organisation that is to be invoiced via the Danish OIOXML/UBLXML standard. Field 2e also concerns the billing contact, but may be used by anyone requiring a purchase order number on future invoices relating to the domain name.

Fields 2d and 2e are not included in section 6 because the electronic account code (Danish: DimensionsKontoStreng) and purchase order number will be linked with the individual domain name and not the billing contact's user ID. If the billing contact is changed, the electronic account code and purchase order number will therefore be removed from the domain name.

The other fields in sections 1, 2 and 3 are not associated with any specific user type.

If section 5 is not filled in, section 4 will automatically be copied into section 5.

If section 6 is not filled in, section 5 will automatically be copied into section 6.

Section 7-12 is about DNSSEC and shall only be put to use of the keyholder (section 7) and up to 5 keysets (sections 8-12) should be appointed to the domain from the time of set up.

DK Domain Version Number: 5.00en Field types [CPAI]

Field C P A I Description
Registrar section
1a. Registrar ID + + + + Unique id for the registrar submitting the form
1b. Registrar's reference * * * * Optional ID for identification by the registrar
Domain name section
2a. Domain name + + + + Application domain name
2b. Registration period (years) + + + + 1, 2, 3 or 5 years
2c. VID (VIP domain name) + + + + Can only be N
2d. Billing contact's PO-number * * * * Optional purcharse order number
2e. Electronic account code - * - - EAN-number for eletronical billing, only applicable for public organisations
2f. Preactivations token * * * * Optional pre-activation token from the pre-activation service, the token is not valid application will be regarded as a regular application
Name servers section
3a. Name + + + + Mandatory name server
3b. Name + + + + Mandatory name server
3c. Name * * * * Optional extra nameserver
3d. Name * * * * Optional extra nameserver
3e. Name * * * * Optional extra nameserver
3f. Name * * * * Optional extra nameserver
3g. Name * * * * Optional extra nameserver
Registrant contact section The registrant section can either be filled in as a user-id or a complete set of data
4. User ID ! ! ! ! Existing user-id
4a. User type + + + + User type C (company), P Public Organisation, A Association or I individual
4b. Company/Organisation + + + - Name of company, Organisation or Association
4c. VAT number + + * - VAT/CVR number
4e. Person - - - + Name of individual
4f. Address 1 + + + + Mandatory address field
4g. Address 2 * * * * Optional address field
4h. Address 3 * * * * Optional address field
4i. Postal code + + + + Mandatory zip/postal code
4j. City + + + + Mandatory city name
4k. Country code + + + + Mandatory two-letter country code (ISO-3166-1)
4l. E-mail address + + + + Mandatory e-mail address
4m. Phone number + + + + Mandatory phone number
4n. Fax number * * * * Optional fax/facsimile number
Administrator contact section The administrator contact section can either be filled in as a user-id or a complete set of data, if not filled in data from the above Registrant contact section will be used
5. User ID ! ! ! ! Existing user-id
5a. User type (CPAI) + + + + User type C (company), P Public Organisation, A Association or I individual
5b. Company/Organisation + + + - Name of company, Organisation or Association
5c. VAT number + + * - VAT/CVR number
5e. Person * * * + Name of individual
5f. Address 1 + + + + Mandatory address field
5g. Address 2 * * * * Optional address field
5h. Address 3 * * * * Optional address field
5i. Postal code + + + + Mandatory zip/postal code
5j. City + + + + Mandatory city name
5k. Country code + + + + Mandatory two-letter country code (ISO-3166-1)
5l. E-mail address + + + + Mandatory e-mail address
5m. Phone number + + + + Mandatory phone number
5n. Fax number * * * * Optional fax/facsimile number
Billing contact section The billing contact section can either be filled in as a user-id or a complete set of data, if not filled in data from the above Registrant contact section will be used
6. User ID ! ! ! ! Existing user-id
6a. User type (CPAI) + + + + User type C (company), P Public Organisation, A Association or I individual
6b. Company/Organisation + + + - Name of company, Organisation or Association
6c. VAT number + + * - VAT/CVR number
6d. EAN number - + - - EAN-number for eletronical billing, only applicable for public organisations
6e. Person * * * + Name of individual
6f. Address 1 + + + + Mandatory address field
6g. Address 2 * * * * Optional address field
6h. Address 3 * * * * Optional address field
6i. Postal code + + + + Mandatory zip/postal code
6j. City + + + + Mandatory city name
6k. Country code + + + + Mandatory two-letter country code (ISO-3166-1)
6l. E-mail address + + + + Mandatory e-mail address
6m. Phone number + + + + Mandatory phone number
6n. Fax number * * * * Optional fax/facsimile number
Keyholder contact section The keyholder contact section can either be filled in as a user-id or a complete set of data, if DS keys are included and the section is not filled in data from the above Registrant contact section will be used
7. User ID ! ! ! ! Existing user-id
7a. User type (CPAI) + + + + User type C (company), P Public Organisation, A Association or I individual
7b. Company/Organisation + + + - Name of company, Organisation or Association
7c. VAT number + + * - VAT/CVR number
7d. Person * * * + Name of individual
7e. Address 1 + + + + Mandatory address field
7f. Address 2 * * * * Optional address field
7g. Address 3 * * * * Optional address field
7h. Postal code + + + + Mandatory zip/postal code
7i. City + + + + Mandatory city name
7j. Country code + + + + Mandatory two-letter country code (ISO-3166-1)
7k. E-mail address + + + + Mandatory e-mail address
7l. Phone number + + + + Mandatory phone number
7m. Fax number * * * * Optional fax/facsimile number
DNSSEC section
8a. Keytag * * * * Unique keytag of DS keyset 1, the keytag has to be unique to the domain name set of keys
8b. Algorithm ^ ^ ^ ^ Algorithm used for DS keyset
8c. Digest_type ^ ^ ^ ^ Digest type used for DS keyset
8d. Digest ^ ^ ^ ^ Digest calculated for DS keyset
9a. Keytag * * * * Unique keytag of DS keyset 2, the keytag has to be unique to the domain name set of keys
9b. Algorithm ^ ^ ^ ^ Algorithm used for DS keyset
9c. Digest_type ^ ^ ^ ^ Digest type used for DS keyset
9d. Digest ^ ^ ^ ^ Digest calculated for DS keyset
10a. Keytag * * * * Unique keytag of DS keyset 3, the keytag has to be unique to the domain name set of keys
10b. Algorithm ^ ^ ^ ^ Algorithm used for DS keyset
10c. Digest_type ^ ^ ^ ^ Digest type used for DS keyset
10d. Digest ^ ^ ^ ^ Digest calculated for DS keyset
11a. Keytag * * * * Unique keytag of DS keyset 4, the keytag has to be unique to the domain name set of keys
11b. Algorithm ^ ^ ^ ^ Algorithm used for DS keyset
11c. Digest_type ^ ^ ^ ^ Digest type used for DS keyset
11d. Digest ^ ^ ^ ^ Digest calculated for DS keyset
12a. Keytag * * * * Unique keytag of DS keyset 5, the keytag has to be unique to the domain name set of keys
12b. Algorithm ^ ^ ^ ^ Algorithm used for DS keyset
12c. Digest_type ^ ^ ^ ^ Digest type used for DS keyset
12d. Digest ^ ^ ^ ^ Digest calculated for DS keyset

Form Keys

! If this field is filled in, the rest of the section should not be completed because the contents of the other fields will automatically be filled in with details from the user ID concerned.
+ Field must be filled in.
- Field must not be filled in.
* Field may be filled in.
^ Field may be filled in, but only if the preceding field has been filled in.

 

Max. number of characters for the individual fields


-

a

b

c

d

e

f

g

h

i

j

k

l

m

n

1


13

40

2


66

1

1

20

20

50

3


254

15

254

15

254

15

254

15

254

15

254

15

254

15

4

13

1

40

20


40

40

40

40

10

40

2

254

20

20

5

13

1

40

20


40

40

40

40

10

40

2

254

20

20

6

13

1

40

20

13

40

40

40

40

10

40

2

254

20

20

7

13

1

40

20

40

40

40

40

10

40

2

254

20

20

8

5

3

3

256

9

5

3

3

256

10

5

3

3

256

11

5

3

3

256

12

5

3

3

256

General advice concerning completion of the application form

Your application will be rejected if you modify the form or break the lines.

Submission of the application form

Send one application per e-mail, entering hostmaster@dk-hostmaster.dk as the address in the “To” field. The application must not be sent as an attached file, Cc or similar.

It must be sent as plain text in one of the following formats:

  • US-ASCII
  • ISO-8859-1
  • Windows-1252

If we accept your application, you will receive a unique tracking number. You should save this and use it as your reference in the future.

If we reject your application, you will not receive a tracking number. We will however advise you of why we have rejected the application.

You will find the blank forms here:

Resources

Pre-activation

The mail form only support the transport of the pre-activation token (Preactivations token). The token has to have been pre-registered with DK Hostmaster using the pre-activation service. If the provided token is not valid or existing at the time of reception of the application, the application will be processed as no pre-activation has taken place.

More information and documentation on the pre-activation service is available at the DK Hostmaster website:

DNSSEC

More information and documentation on the use of DNSSEC service is available at the DK Hostmaster website:

Mailing list

DK Hostmaster operates a mailing list for discussion and inquiries about the DK Hostmaster mail-form service. To subscribe to this list, write to the address below and follow the instructions. Please note that the list is for technical discussion only, any issues beyond the technical scope will not be responded to, please send these to the contact issue reporting address below and they will be passed on to the appropriate entities within DK Hostmaster.

Issue Reporting

For issue reporting related to this specification, the pre-activation service, sandbox or production environments, please contact us. You are of course welcome to post these to the mailing list mentioned above, otherwise use the address specified below: