|
|||||||||
|
|||||||||
|
|||||||||
|
|
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:
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-enum.txt
version: 1.0.0
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.
Registration data (section 1) section: 1
mode:
domain:
comment:
language: de
authinfo:
new-authinfo:
With the
mode-parameter
you can define if you wish to perform a new registration (
mode: new),
a transfer from another registrar (a so-called
»Konnektivitätskoordination« - coordination of connectivity,
mode: kk),
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 may not appear.
Likewise, no authinfo-fields (see below)
may be used for a deletion.
Deletion: When deleting a domain via e-mail
template, the domain is marked for immediate deletion, i.e. the requested
end date is set to the date and time of the receipt of order.
The effective deletion from our system, however, does only take place in the
course of specific maintenance phases that are scheduled in regular intervals.
Thus, the deletion can be canceled by using our web interface
until the beginning of the next maintenance phase.
Next to domain,
the complete domain name has to be given.
For example:
domain: 3.0.7.9.1.3.2.9.4.e164.arpa.
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.
With the language parameter you can
specify a language code for the domain name. The language code can be used
to determine possible alternative notations of the name.
Especially in asian regions it occurs that there are several different ways
to represent the same term.
Some registries offer to include possible alternative notations
in a registration or to block their registration by third parties.
Knipp's DRS is already featured with this option, so you can use this field to
specify a language code.
Domain holder (section 2) Note:
Formerly, the DENIC used to collect these data in a rather unstructured
way in descr-fields.
Since May 2005, the contact information for the holder is collected
in specialized form fields (like street, city, etc.) and
stored with a so-called »holder handle« (see below).
person:
organization:
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
type:
A contact can be of one of the types listed in
section 4.
When creating a new contact for a registrant, the field
type is mandatory, when changing an existing
contact it is prohibited.
address-1:
address-2:
address-3:
postal-code:
city:
country:
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.
The mandatory 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.
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: DENIC-60-DRS1000000.
Important:
The different top level domains each require their own set of handles.
For example, .biz handles can not be used for .de 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.
type: Important:
Generally speaking, a contact can be of one of the types listed in
section 4. For the administrator,
however, only
type: person is allowed.
person:
This field has to be filled.
organization:
address-1:
address-2:
address-3:
postal-code:
city:
country:
phone:
fax:
email:
handle:
The parameters have to be filled out in the same way as described for the
domain holder (or by specifying a handle).
Technical contact (section 4)
The technical contact is the contact person for technical concerns.
He is responsible for operating the name servers, for instance.
type:
person:
organization:
address-1:
address-2:
address-3:
postal-code:
city:
country:
phone:
fax:
email:
handle:
These fields must be filled out in the same way
as for the administrator contact.
Alternatively, you can specify an adequate handle.
However, for this contact you must fill out
the fax field.
For type,
you can use the values as listed below.
Zone contact (section 5)
The contact for the zone data is the entity that is responsible
for the contents of the name server.
type:
person:
organization:
address-1:
address-2:
address-3:
postal-code:
city:
country:
phone:
fax:
email:
handle:
These fields must be filled out in the same way
as for the administrator contact.
Alternatively, you can specify an adequate handle.
However, for this contact you must fill out
the fax field.
Technical data (section 6) www-forwarding:
email-forwarding:
nsentry1:
nsentry2:
nsentry3:
nsentry4:
nsentry5:
ns-domain-name1:
ns-ip-address1:
ns-domain-name2:
ns-ip-address2:
ns-domain-name3:
ns-ip-address3:
hserver:
lock:
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.some-domain.de
ns-domain-name2: your-second-dns.3.0.7.9.1.3.2.9.4.e164.arpa
ns-ip-address2: 195.194.2.77
ns-domain-name3: possibly-another-dns.other-domain.de
If one of the name servers that you operate
is part of the ENUM zone of the domain that you are about to register
(�3.0.7.9.1.3.2.9.4.e164.arpa� in this case),
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:
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 ENUM zone of the domain that you are about to register
(�3.0.7.9.1.3.2.9.4.e164.arpa� 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.3.0.7.9.1.3.2.9.4.e164.arpa
ns-ip-address1: 195.194.2.77
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:
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: 0.3.0.7.9.1.3.2.9.4.e164.arpa. 60 IN NAPTR 10 101 "u" "E2U+tel" "!^[+]492319703(.*)$!tel:+49 231 9703 0!".
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: 0.3.0.7.9.1.3.2.9.4.e164.arpa. 60 IN NAPTR 10 101 "u" "E2U+tel" "!^[+]492319703(.*)$!tel:+49 231 9703 0!".
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.
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.
Registration terms and conditions (section 8)section: 8 accept-agb: http://drs.knipp.de/.../agb-rev20030301a-en.txt accept-registry: http://drs.knipp.de/domains/types/de/reg-rev20131203-en.txt
These fields have to be included without any changes.
Please note the following information concerning this
e-mail application form:
|
|||||||||||||||||||||||||||||||
|
|