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:

#-----------------------------------------------------------------------
#   |       |
#   | 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-name.txt
         version: 4.0.5

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.

This section specifies what shall be registered.

Important: As opposed to other top level domains (like .de or .com), .name domains provide an e-mail service (e-mail forwarding) in addition to the domains. Therefore, the structure of this section differs from that of other application forms. Alternatively you can order the only the domain, only the E-mail service, or both services.

Domains can be registered as third level domains or - since January 14th, 2004 - as second level domains. Thus, each domain name contains two dots or a single dot.

           section: 1
      registration:
              mode:
            domain:
           comment:
          language:
       short-email:
          authinfo:
      new-authinfo:

Next to Registration provide the character string (=domain name). Example: registration: jack.jones.name.

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.

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.

Here is an example template for the creation of a new handle for com/net domains. Simply replace the sections 0 and 8 by the corresponding sections from the correct e-mail template.

Next to domain, please confirm if you want to register the domain by choosing yes or no. (It is possible to register only the e-mail service but not the domain.)

The field comment can be used to save a free-text comment about this domain.

The language-field is required for internationalised domain names (IDNs). Otherwise it is optional.

At short-email, please indicate by choosing yes or no whether or not you want to register the e-mail service. (“no” if you intend to register only the domain.) The e-mail service is available for third level domains only.

Important: The field short-email has to contain no when registering an IDN, because e-mail addresses are not available for such domain names.

Important: The short-email-field will only be accepted for mode: new and may not be used in combination with other modes (i.e. update, ctsr, or delete). For modifications of this type, please contact our support team.

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 8 and at most 32 characters and has to contain at least one digit, one letter and one special character (e.g. ! § $ % & = ?). 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!

Example 1: Registration of the domain jack.jones.name and the appropriate E-mail address jack@jones.name. The password is jac-jon-&1.

      registration: jack.jones.name
            domain: yes
       short-email: yes
          authinfo: jac-jon-&1

Example 2: Registration of the e-mail address william@smith.name only. The password is secret-123!.

      registration: william.smith.name
            domain: no
       short-email: yes
          authinfo: secret-123!

            person:
      organization:

The registrant is the designated holder of the domain. As opposed to many other top level domains, only natural persons can be given here, because .name domains are intended for personal use only.

At the field person, the name of the holder has to be given. The parameter organization can optionally be used for additional specifications. For example, you could enter organization: insurance broker if the domain shall be used for job-related purposes, too.

         address-1:
         address-2:
         address-3:
       postal-code:
              city:
             state:
           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. 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: C2468-NAME.

Important: The different top level domains each require their own set of handles. For example, .info handles can not be used for .name domains, even if both handles specify the same contact data!

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.

            person:
      organization:
         address-1:
         address-2:
         address-3:
       postal-code:
              city:
             state:
           country:
             phone:
               fax:
             email:
          authinfo:
            handle:

The parameters have to be filled out in the same way as described for the domain holder (or by specifying a handle).

The technical contact is the contact person for technical concerns. He is responsible for operating the name servers, for instance.

            person:
      organization:
         address-1:
         address-2:
         address-3:
       postal-code:
              city:
             state:
           country:
             phone:
               fax:
             email:
          authinfo:
            handle:

The parameters have to be filled out in the same way as described for the domain holder (or by specifying a handle).

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.

            person:
      organization:
         address-1:
         address-2:
         address-3:
       postal-code:
              city:
             state:
           country:
             phone:
               fax:
             email:
          authinfo:
            handle:

The parameters have to be filled out in the same way as described for the domain holder (or by specifying a handle).

    www-forwarding:
  email-forwarding:
       short-email:
          nsentry1:
          nsentry2:
          nsentry3:
          nsentry4:
          nsentry5:
   ns-domain-name1:
    ns-ip-address1:
   ns-domain-name2:
    ns-ip-address2:
   ns-domain-name3:
    ns-ip-address3:
     stealthserver:
              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.

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.

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

Our DRS provides several features, e.g. multiple E-mail forwardings etc., see as well the forwarding specific frequently asked questions and answers.

When newly registering a third level domain, you can specify in section 1 that you want to use the e-mail service. In that case, you can enter the e-mail address to which the incoming mails shall be sent in the short-email-field. If, for example, you want to use the e-mail service for the domain john.malkovich.name to forward all e-mails for john@malkovich.name to a hotmail account, it would look like this:

       short-email: john_malkovich1953@hotmail.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.

You operate all the name servers by yourself.

   ns-domain-name1: your-first-dns.some-domain.de
   ns-domain-name2: your-second-dns.john.malkovich.name
    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 a .name 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.

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 a .name zone, 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.john.malkovich.name
    ns-ip-address1: 195.194.2.77
   ns-domain-name2: ns3.knipp.de

The other parameters of this section (not listed here) remain empty.

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 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: john.malkovich.name. 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: john.malkovich.name. 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.)

       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.

           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.

Please note the following information concerning this e-mail application form: