FAQTechnical Documentation
DRS Documentation
General FAQ
Whois Accuracy Program (WAP)
Domain Types
OverviewIDN ExtensionsIDN character setFAQWhoisRegister OnlineNaming ConventionE-mail TemplateTemplate HelpRegistration Terms
.de Domains
.eu Domains
IDN Extensions
Register Online
E-mail Template
Template Help
Registration Terms
The .eu Code of Conduct
.biz.com/.net.info.name.orgNew Generic TLDs
Generic Domains
Sponsored Domains
Template HelpFAQ.ac Ascension Island.af Afghanistan.ag Antigua and Barbuda.at Austria.au Australia.be Belgium.bz Belize.ca Canada.cc Cocos (Keeling) Islands.ch/.li Switzerland and Liechtenstein.cn China.co Colombia.cx Christmas Islandmore...
Special Types
FAQE-mail TemplateTemplate HelpRegistration Terms
FAQTechnical BackgroundCountries OverviewCharacter SetsConverterExample Website
Internationalized Domain Names (IDN)
Redirection FAQ
Service Bundle
Price List
Application Form
Premium-Partner-Program (P3)

Instructions for filling out the e-mail application formfor .eu domains

Follow this link to the e-mail application form.
This page describes the most important parameters of the e-mail application form. The respective parts of the template are shown within a colored area, with helpful comments located below them. Self-explanatory parameters like email will not be mentioned here.
The e-mail application form is intended for experts and the automated processing by robots. You will need technical experience to fill out the form, e.g. to give the correct information in section 6. If you are not sure about the meaning of all the terms, you should use the comfortable web interface of our DRS.
The form is divided into multiple sections:

E-mail application form

Introduction (section 0)

#   |       |
#   | knipp |                        Knipp Medien und Kommunikation GmbH
#    -------
All the lines beginning with # are comments and can be ignored. These lines are only used to improve structure and readability. The same is true for blank lines. They are only used to clearly arrange the form and can be added or deleted arbitrarily.
         section: 0
The application form is divided into several sections. Each section forms a chapter by itself and is separated from the other chapters by the key section. Do not remove these lines.
          doc-id: appli-en-eu.txt
         version: 4.2.1
Is required for further processing by Knipp. Please do not delete.
You can insert any text you like here. This text will be quoted in all of the responses of our system. This allows for an easy recognition and classification of your applications by your robots, if you want to automatically process our responses.
You might want to use this field to indicate reference numbers of your customers, for example, or a contract number, etc.

Registration data (section 1)

           section: 1
With the mode-parameter you can define if you wish to perform a new registration ( mode: new), a transfer from another registrar (mode: ctsr), an update ( mode: update), or a deletion ( mode: delete). An update can be used to modify the contact data or to change the WWW forwardings, for instance. If you leave the mode-parameter empty, a new registration will be initiated.
Important: If you choose mode: update you must fill out all sections, not only the parts to change. For mode: delete, only the sections 0, 1, 7, and 8 may be filled. The sections from 2 to 6 must not appear. Likewise, no authinfo-fields (see below) may be used for a deletion.
mode: update-dnssec: Due to its DNSSEC support there is an additional mode for this TLD that allows for a quick update of the DNSSEC data. In this mode it is sufficient to include the new DNSSEC data in section 6 of the form. The other domain data will remain unchanged. An optional comment can be included in section 1 to be stored with the domain. Please refer to our example template for a DNSSEC update and mind the note on PGP signing in section 6.
In a similar fashion, for mode: update-dnssec only the sections 0, 1, 6, 7 and 8 may be used. The sections 2 to 5 may not appear, while section 6 must solely contain the new DS- or DNSKEY entries.
Deletion: When deleting a domain via e-mail template, the domain is marked for deletion, i.e. the requested end date is set. The optional field
allows to set the requested end date. The value can be either a date in the future, e.g. 2096-02-29, or scheduled, which means that the domain will be deleted at its scheduled end date. If deletion-date is not specified, the deletion will take place at the earliest possible date.
Note that the effective deletion from our system does only take place in the course of specific maintenance phases that are scheduled in regular intervals. Thus, the deletion can be canceled using our web interface until the beginning of the relevant maintenance phase.
For .eu, .com, .net, .biz, .info, .mobi and .us domains, a 30 day Redemption Grace Period starts with the deletion (40 days in case of .eu). During this period, the deleted domain cannot be registered by third parties and is free to be reactivated by the former registrant. (This results in costs, however.) For other top level domains a similar mechanism does not exist.
Creation and update of handles: In addition to the possibilities described above, you can also create new handles or update the data of an existing handle with the modes mode: new-contact and mode: update-contact. To do so, the sections 0, 1, 2, 7 and 8 have to be filled, with the complete new contact data in section 2. (Example: Template for the creation of a new handle for .eu domains.) When creating a new handle for .eu domains, an additional field type: has to be given to specify the type of the contact. Possible values are “registrant” and “onsite”.
Next to domain, the complete domain name has to be given. For example: domain: my-company.eu. Only one domain name can be given per e-mail application form.
The field comment can be used to save a free-text comment about this domain.
Mit dem Parameter language können Sie die Sprachkennzeichnung für den Domainnamen festlegen. Sie dient dazu, mögliche alternative Schreibweisen des Namens zu bestimmen. Insbesondere im asiatischen Raum kann es vorkommen, dass verschiedene Schreibweisen für denselben Begriff existieren. Einige Registries bieten an, solche alternativen Domainnamen gleich mit zu registrieren oder deren Registrierung durch Dritte zu blockieren. Da das DRS von Knipp bereits für die Nutzung dieser Optionen ausgelegt ist, kann eine Sprachkennzeichnung angegeben werden.
For .eu domains, filling the language field is optional, unless it is a pre-registration for an internationalized domain name. In that case, the language has to be specified.
authinfo is some kind of password, which is required for changing the registrar of a domain. It thus protects you against unauthorized persons initiating such an operation. If at some time you want to change the sponsoring registrar (CTSR), you have to know the authinfo for the respective domain and to name it in this field. This proves that you are authorized to request the change. For security reasons, the authinfo is not valid indefinitely, but only for 40 days. Example: authinfo: XXXX-2U79-Y5QS-MSE2.

Domain holder (section 2)

The registrant is the designated holder of the domain. This can be a natural person or a legal person.
In case of a natural person, only person has to be filled out. If the holder is a legal person (e.g. a company), you have to specify it at organization in any case. Nevertheless, a contact person must also be given at field person
The parameter address-1 is intended for the street address. Filling this field is mandatory. address-2 and address-3 can be used for additional entries (for the zip-code or other add-ons).
The postal-code-parameter (mandatory field) is intended for the zip/postal code, while city (mandatory as well) holds the name of town. state (Region, Area, Province, State) is an optional parameter, as opposed to country. The country parameter is required to hold the international country code representation according to ISO-3166, like “DE”, “AT”, or “CH”. This field is case-insensitive (so using “de” or “De” will work as well), but it may not contain periphrases like “Germany” or “Switzerland”!
Important: The owner of a .eu domain has to be located in one of the member states of the EU. Thus, only the following country codes are allowed.
Allowed ISO3166 country codes for .eu domain owners
Austria, Republic of
Belgium, Kingdom of
Cyprus, Republic of
Czech Republic
Denmark, Kingdom of
Spain, Spanish State
Finland, Republic of
France, French Republic
United Kingdom of Great Britain & N. Ireland
French Guiana
Greece, Hellenic Republic
Hungary, Hungarian People's Republic
Italy, Italian Republic
Luxembourg, Grand Duchy of
Malta, Republic of
Netherlands, Kingdom of the
Poland, Polish People's Republic
Portugal, Portuguese Republic
Sweden, Kingdom of
Slovakia (Slovak Republic)
Specifying a phone number in field phone is mandatory. The number has to be given in the following format: +CCC.NNNNN, where CCC represents the country code (e.g. 49 for Germany) and NNNN is the actual number including the area code. Using a plus sign in front of the country code and a dot to separate it from the rest of the number is mandatory, too. Example: +49.8912345678
If a fax number is available, it can be specified at fax. The format has to be the same as in phone.
The field vat-number is optional and can be used to specify a Value Added Tax identification number
The language field contains the preferred language of the contact. It must be provided and may only contain one of the language codes listed below.
Allowed language codes for .eu domain owners
handle provides an alternative way to specify contact data. With every successful registration of a domain, a handle is being created for every contact provided during the registration process. Once you have a handle for a set of contact data, you don't have to manually fill out the fields if you want to use the same data again. Instead, it suffices to specify the appropriate handle in this field. This saves you a lot of typing. If you fill out the fields and enter a handle at the same time, the values specified in the fields will be ignored and those from the handle will be taken instead.
Example: handle: c3186966.
Important: The different top level domains each require their own set of handles. For example, .biz handles can not be used for .eu domains, even if both handles specify the same contact data!
Important: Additionally, with the .eu registry EURid, the handles are bound to specific functions of the contact. I.e., the handle of a domain owner cannot be used to specify a technical contact, even it is the same person with the same data.

Administrator (section 3)

A contact like that does not exist for .eu domains.

Technical contact (section 4)

The technical contact is the contact person for technical concerns. He is responsible for operating the name servers, for instance.
In the case of .eu domains, a technical contact specified by the domain owner is called “Onsite contact”. Specifying this contact is optional. If you do not name an Onsite contact, a technical contact from Knipp will be entered for the domain. It is not possible to edit this contact, but you can replace it with your own Onsite contact anytime.
The parameters have to be filled out in the same way as described for the domain holder (or by specifying a handle).

Billing contact (section 5)

A contact like that does not exist for .eu domains.

Technical data (section 6)

The completion of this section requires some amount of previous technical knowledge. It will be difficult for you to specify the proper values without an adequate knowledge of the technical background. Some basic terms are listed in our glossary. If you are not familiar with these terms, we suggest that you use the comfortable web interface of our DRS, which will assist you with helpful information.
For registered domains, several different modes of operation with many variants exist. In the enumeration below we have only listed those modes that can be configured by means of this e-mail application form. All the other variants, including mixed ones, can be adjusted via our DRS.

Domain parking

You do not need to actually use the domain right away, but you want to register it already. You can easily do this by providing the following entries:
   ns-domain-name1: ns2.knipp.de
   ns-domain-name2: ns3.knipp.de
The remaining parameters of this section (not listed here) remain empty. Whenever you want to start using the domain, you can update these entries free of charge.

E-mail and WWW forwarding

All http requests shall be forwarded to an existing URL. All e-mails targeted at this domain shall be forwarded to another e-mail address. Example:
    www-forwarding: http://students.example.edu/home/~jjones/index.htm
  email-forwarding: j.jones@aol.com
The remaining parameters of this section (not listed here) remain empty. Our DRS provides several other features, like multiple e-mail forwardings, etc. See our frequently asked questions and answers on forwardings for more information.

All the name servers operated by the customer

You operate all the name servers by yourself.
   ns-domain-name1: your-first-dns.example.com
   ns-domain-name2: your-second-dns.example.com
   ns-domain-name3: possibly-your-third-dns.example.com
If one of your name servers is part of a .eu zone (e.g. example.eu), you have to provide the IP address of that server as well. Example:
   ns-domain-name1: your-first-dns.example.com
   ns-domain-name2: your-second-dns.example.eu
   ns-domain-name3: possibly-your-third-dns.example.com
The other parameters of this section (not listed here) remain empty.

Slave name server operated by Knipp

You operate one name server by yourself, while the slave name server shall be operated by Knipp. We provide this service free of charge, by the way. Please use ns3.knipp.de for this purpose. Example:
   ns-domain-name1: dns.your-server.de
   ns-domain-name2: ns3.knipp.de
If one of the name servers that you operate is part of the .eu zone of the domain that you are about to register (“new-domain.eu” in this case), then you have to additionally provide the IP address of that server in the corresponding “ns-ip-address” field. Example:
   ns-domain-name1: your-first-dns.new-domain.eu
   ns-domain-name2: ns3.knipp.de
The other parameters of this section (not listed here) remain empty.

Stealth name server (formerly known as hidden primary)

You operate the master name server yourself but do not want it to be known to the outside world for some reason. In this case, Knipp can operate the official name servers for you, which then retrieve the data from your name server. You just have to specify the IP address of your name server (which is the stealth name server in that case). This service by Knipp is free of charge. Example:
The other parameters of this section (not listed here) remain empty.
Important: Please make sure that the name servers “ns2.knipp.de” and “ns3.knipp.de” are allowed to carry out zone transfers from your system.

Knipp operates the name servers

Knipp shall operate the name servers, but you would like to define the data to be used in the zone. In the example below, a WWW server is supposed to be entered, to which the domain itself points, as well as a mail relay.
          nsentry1: my-domain.eu. IN A
          nsentry2: www IN A
          nsentry3: mail IN MX 10 smtp.example.com.
The other parameters of this section (not listed here) remain empty. Additional entries or modifications are possible by using our DRS.
Important: If you would like to add zone entries, whose first entry is empty (the so-called owner-entry), you have to put the whole entry in quotation marks. Leaving it blank means that the entry of the previous line will be used. Example:
          nsentry1: my-domain.eu. IN A
          nsentry2: " IN MX 10 smtp.example.com."
          nsentry3: " IN MX 20 backup.example.com."
          nsentry4: www IN A
Please bear in mind that MX-entries can point to host names only, but never to IP addresses (the host names used here are “smtp.example.com.” and “backup.example.com.”, respectively). Remember that MX-entries of a different domain than the domain itself must always end with a dot as shown in the example above. (backup.example.com<DOT>)
Please note that the lock: field is not available for .de, .ch/.li- and .eu domains and that it is not allowed in these templates, since these registries do not support a lock function.


Two kinds of DNSSEC data can be specified: DS records and DNSKEY records.
The number of records in the e-mail template is not limited. The names of the fields are all the same, always “ds” or “dnskey”. In case more records are specified than allowed by the registry, an error is returned.
The format of the entries is the RDATA presentation format defined in RFC 4034:
                ds: <key-tag> <alg> <digest-type> <digest>
            dnskey: <flags> <protocol> <alg> <pub-key>
The placeholders for DS records have the following meaning:
The key tag of the DNSKEY record referred to by the DS record.
The algorithm of the DNSKEY record referred to by the DS record.
The algorithm used to construct the digest of the DNSKEY record.
The digest of the DNSKEY record referred to by the DS record, represented as a sequence of hexadecimal digits. Whitespace is allowed within the value.
The placeholders for DNSKEY records have the following meaning:
The flags specifying whether the record holds a DNS zone key and whether the key is intended for use as a secure entry point. Valid values: 0, 256, 257.
The protocol. Must have the value 3.
The public key's cryptographic algorithm.
The public key material, encoded in Base64. Whitespace is allowed within the value.
Note on PGP signing: In order not to counteract the purpose of DNSSEC and to guarantee for a genuine transmission it is advisable to sign e-mails containing DNSSEC data via PGP. Please get in touch with Knipp Support who will activate the signature functionality for you and accept your public PGP key.

Customer data (section 7)

Please provide your 5-digit customer number at customer-no, and your e-mail password in field password. (Attention: Your e-mail password is required here, not the one used for the web interface). Each employee of a company receives his own unique access data. This ensures that the DRS can identify which person within your company initiated which process.

Registration terms and conditions (section 8)

           section: 8
accept-agb: http://drs.knipp.de/.../agb-rev...-en.txt
accept-registry: http://drs.knipp.de/domains/types/.../reg-rev...-en.txt
These fields have to be included as in the template without any changes.

General information

Please note the following information concerning this e-mail application form:
  • Please do not send e-mail applications in HTML-format. Always use the so-called ASCII-format instead. Every modern e-mail client provides a way to adjust this.
  • Each line in the form holds one key-value pair, with key and value being separated by a colon. Example: organization: My Company Ltd.. The value has to be on the same line as the key. The value must not be wrapped to the next line in case the the maximum number of characters is exceeded. Make sure to configure your e-mail client accordingly.
  • Whitespace (blanks) before and after the key and behind the separator (colon) will be ignored. So, you can use whitespace to arrange the text and thus to increase the readability of the request.
  • You can also use local language characters for the values of the contacts. These characters will automatically be converted to the corresponding ASCII characters. For example: Albrecht-Dürer-Street 5 will be converted to Albrecht-Duerer-Street 5. Note: It is safer to directly enter the ASCII version, because not all local language characters can be converted correctly. (All characters in the domain-field remain unmodified, of course.)
  • Please send the completed e-mail application forms to the address drs@knipp.de. Do not use support@knipp.de for this purpose. This second address is designated for general requests to our support team.
print (C) 1996-2024 Knipp Medien und Kommunikation GmbH|webmaster@knipp.de