# $Id: appli-en-xxx.txt 21278 2021-10-15 13:29:47Z thomas.corte $ #----------------------------------------------------------------------- # | | # | knipp | Knipp Medien und Kommunikation GmbH # ------- section: 0 doc-id: appli-en-xxx.txt version: 4.0.3 reference: # This form is designed for the processing of .xxx domain applications # for the Surise and Landrush phase and for preregistrations for the # General Availability phase. PLEASE NOTE THAT FOR SUNRISE- AND # LANDRUSH APPLICATIONS A SPECIAL PRICING SCHEME APPLIES. # The exact prices can be found at: # http://drs.knipp.de/domains/pricelist.do#xxx # # Explanations to each of the different sections and fields are # available at http://drs.knipp.de/domains/types/stld/xxx/appli-help.do # That prevents this form from inflating and keeps it manageable. # # Each of the fields that have to be completed starts at the beginning # of a line, followed by a colon. The data have to be entered # behind the colon. Lines which start with a pound sign (#) are comments # and may be omitted. # # Please send the completed form to "drs@knipp.de". # 1. Domain name # # Example # section: 1 # mode: new # domain: exxxample.xxx # authinfo: my-authinfo section: 1 mode: new domain: comment: authinfo: # 2. Domain holder or registrant # # Example # section: 2 # person: Jack Jones # organization: Acme Ltd. # address-1: Examplestreet 123 # address-2: # address-3: # postal-code: 80033 # city: Muenchen # state: Bayern # country: DE # phone: +49.898333832 # fax: +49.89833384 # email: jackjones@example.com # authinfo: my secret 1 # handle: section: 2 person: organization: address-1: address-2: address-3: postal-code: city: state: country: phone: fax: email: authinfo: handle: # 3. Administrative contact (admin-c) # # Layout as in section 2 section: 3 person: organization: address-1: address-2: address-3: postal-code: city: state: country: phone: fax: email: authinfo: handle: # 4. Technical contact (tech-c) # # Layout as in section 2 section: 4 person: organization: address-1: address-2: address-3: postal-code: city: state: country: phone: fax: email: authinfo: handle: # 5. Billing contact # # Layout as in section 2 section: 5 person: organization: address-1: address-2: address-3: postal-code: city: state: country: phone: fax: email: authinfo: handle: # 6. Technical details (forwarding, nameserver, etc.) # # Example # www-forwarding: http://www.register-me.de/~tobey # email-forwarding: tobey@doobeedoo.de # nsentry1: www 10001 IN A 62.52.24.2 # nsentry2: " IN A 62.52.24.3" # nsentry3: " IN MX 10 mail.doobeyydoo.de" # nsentry4: " 10000 IN MX 20 mail2.doobeydoo.de" # nsentry5: " IN MX 30 mail2.doobeydoo.de" # ns-domain-name1: dns.doobeydoo.de # ns-ip-address1: 192.253.23.1 # ns-domain-name2: dns2.doobeydoo.de # ns-ip-address2: 192.253.23.2 # ns-domain-name3: dns3.doobeydoo.de # ns-ip-address3: 192.253.23.2 # hserver: 195.123.12.2 section: 6 www-forwarding: email-forwarding: nsentry1: nsentry2: nsentry3: nsentry4: nsentry5: nsentry6: nsentry7: nsentry8: nsentry9: nsentry10: ns-domain-name1: ns-ip-address1: ns-domain-name2: ns-ip-address2: ns-domain-name3: ns-ip-address3: ns-domain-name4: ns-ip-address4: ns-domain-name5: ns-ip-address5: ns-domain-name6: ns-ip-address6: ns-domain-name7: ns-ip-address7: ns-domain-name8: ns-ip-address8: hserver: # 7. Customer data # # Example # customer-no: 12345 # password: absolutely!Secret section: 7 customer-no: password: # 8. Registration terms and conditions # # The applicant accepts the following terms and conditions, which are # specified by the use of an URL. The terms and conditions become # inherent part of the application. section: 8 accept-agb:http://drs.knipp.de/company/info/agb/domains-rev20030301a.do accept-registry:http://drs.knipp.de/domains/types/stld/xxx/reg-rev20110801a-en.txt #--- end-of-template ---------------------------------------------------