Follow this link to
the e-mail application form.
It is designed for the processing of generic domain applications.
That includes, next to the established generic top level domains
com, net, org, info, biz, mobi, asia, and me, especially all TLDs that
have been newly introduced since 2012. Exempted are
aero,
tel and
name,
for which only the traditional TLD-sepcifc templates can be used, as before.
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.
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-generic.txt
version: 4.0.1
Is required for further processing by Knipp. Please do not delete.
reference:
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.
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
deletion-date:
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.
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.
Please note that in this template for generic TLDs - as opposed to the
TLD-specific templates - it is necessary that you explicitly specify for which
TLD the contact modification shall be performed. To do so, the TLD has to be
given in section 1 in addion to the "mode:" field, in a new field tld: .
It is also important to note that the "tld:"-field is only allowed for the
new-contact and update-contact modes, and only in the templates for
new generic TLDs.
Next to domain,
the complete domain name has to be given.
For example:
domain: blue-wind.tld.
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.
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.
You can choose it freely during the registration of a new domain.
It must consist of at least 4 and at most 16 characters.
Example: authinfo: secret-123.
The field authinfo may be omitted; in this
case, the system automatically generates a suitable and secure character string,
which you can view in the DRS web interface.
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. At the same time, you have to constitute a new password
by using the new-authinfo-field.
This specification is mandatory. The same rules concerning the characters apply
for new-authinfo, of course, since it becomes
the authinfo for the domain after the change.
Important:
The authinfo-fields may not be used for deletions
(i.e. mode: delete).
Important:
The new-authinfo-field is only neccessary to
change the registrar and may not be used for updates or for the registration
of a new domain!
The registrant is the designated holder of the domain.
This can be a natural person or a legal person.
This is determined via the
individual-field.
individual: Y
means that the holder is a natural person, while
individual: N
stands for a legal person (e.g. an organization or a company).
fname and
lname
determine first name and last name of the contact person.
These fields must always be given. By the parameter
title
you can optionally enter an academic title for the contact
person (e.g. “Prof. Dr.”). The
organization-field
has to specify the organization or company if a legal
person was chosen as the holder (i.e.
individual: N).
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”!
phone:
fax:
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.
authinfo:
Analogue to the
authinfo-field in
section 1 (Registration data).
This parameter might become necessary in the future.
Independently of the actual usage at the registry,
this field has to be filled out by now already.
The field authinfo may be omitted; in this
case, the system automatically generates a suitable and secure character string,
which you can view in the DRS web interface.
handle:
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: C-12345.
Important:
The different top level domains each require their own set of handles.
For example, .info handles can not be used for new generic top level domains,
even if both handles specify the same contact data!
Administrator (section 3)
The administrator is an authorized person who is acting on behalf of the
registrant. He can, for example, request modifications of a domain.
The administrator and the holder of a domain
can be the same person.
The administrator can be a legal department or an external office, as it is
often the case with larger companies.
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)
The billing contact is the person who responsible for the payment
within an organization. This distinction is reasonable in larger companies,
although in the majority of cases the billing contact is identical to the
domain holder.
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.
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:
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.
If one of the name servers that you operate
is part of a .com, .net, .org or new generic zone,
then you have to additionally provide the IP address of that server
in the corresponding “ns-ip-address” field.
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:
If one of the name servers that you operate
is part of a .com, .net, .org or new generic zone,
then you have to additionally provide the IP address of that server
in the corresponding “ns-ip-address” field.
Example:
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:
hserver: 105.207.3.3
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.tld. IN A 195.254.6.12
nsentry2: www IN A 195.254.6.12
nsentry3: mail IN MX 10 smtp.provider.de.
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.tld. IN A 195.254.6.12
nsentry2: " IN MX 10 smtp.provider.de."
nsentry3: " IN MX 20 backup.provider.de."
nsentry4: www IN A 195.254.6.12
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>)
lock:
Giving lock: yes offers the possibility to automatically
set a lock on a domain after a successful registration or a successful transfer.
By omitting this field (or by giving lock: no, respectively)
no lock will be set as usual. (This option is not available for .de and .eu domains, since
neither DENIC nor EURid support a lock function on the Registry level.)
DNSSEC
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:
The placeholders for DS records have the following meaning:
Placeholder
Description
<key-tag>
The key tag of the DNSKEY record referred to by the DS record.
<alg>
The algorithm of the DNSKEY record referred to by the DS record.
<digest-type>
The algorithm used to construct the digest of the DNSKEY record.
<digest>
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:
Placeholder
Description
<flags>
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.
<protocol>
The protocol. Must have the value 3.
<alg>
The public key's cryptographic algorithm.
<pub-key>
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)
customer-no:
password:
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.
These fields have to be included as in the template without any changes.
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.