domain:create

XML Template for church domains

XML Template for church domains
<?xml version="1.0" encoding="UTF-8"?>
<request
    xmlns:domain="http://www.eurodns.com/domain"
    xmlns:nameserver="http://www.eurodns.com/nameserver"
    xmlns:contact="http://www.eurodns.com/contact"
    xmlns:company="http://www.eurodns.com/company"
    xmlns:extension="http://www.eurodns.com/extension"
    xmlns:secdns="http://www.eurodns.com/secdns"
    xmlns:nameserverprofile="http://www.eurodns.com/nameserverprofile"
    xmlns:zoneprofile="http://www.eurodns.com/zoneprofile">

    <domain:create>
        <domain:name>#DOMAIN.TLD#</domain:name>
        <domain:year>#SUBSCRIPTION PERIOD#</domain:year>
        <domain:renewal>#RENEWAL MODE#</domain:renewal>
        <domain:folderid>#DOMAIN FOLDERID#</domain:folderid>
        <nameserverprofile:id>#NAMESERVER PROFILEID#</nameserverprofile:id>
        <zoneprofile:id>#ZONE PROFILEID#</zoneprofile:id>
    </domain:create>

    <nameserver:create>
        <nameserver:priority>#PRIORITY#</nameserver:priority>
        <nameserver:fqdn>#FULLY QUALIFIED DOMAIN NAME#</nameserver:fqdn>
        <nameserver:ipaddr>#IP ADDRESS#</nameserver:ipaddr>
    </nameserver:create>

    <contact:create>
        <contact:type>#TYPE#</contact:type>
        <contact:contactprofileid>#CONTACT PROFILE ID#</contact:contactprofileid>
        <contact:firstname>#FIRSTNAME#</contact:firstname>
        <contact:lastname>#LASTNAME#</contact:lastname>
        <contact:company>#COMPANY#</contact:company>
        <contact:address1>#ADDRESS LINE 1#</contact:address1>
        <contact:address2>#ADDRESS LINE 2#</contact:address2>
        <contact:address3>#ADDRESS LINE 3#</contact:address3>
        <contact:city>#CITY#</contact:city>
        <contact:zipcode>#ZIP/POSTAL CODE#</contact:zipcode>
        <contact:country_code>#COUNTRY CODE#</contact:country_code>
        <contact:email>#EMAIL ADDRESS#</contact:email>
        <contact:phone>#PHONE NUMBER#</contact:phone>
        <contact:fax>#FAX NUMBER#</contact:fax>
    </contact:create>

    <extension:claims>
        <extension:noticeid>#NOTICE ID#</extension:noticeid>
        <extension:lookupkey>#CLAIM KEY#</extension:lookupkey>
        <extension:accepteddate>#ACCEPTED DATE#</extension:accepteddate>
        <extension:ip>#IP#</extension:ip>
    </extension:claims>

    <extension:create>
        <extension:secdns>
            <secdns:keydata>
                <secdns:flag>#FLAG#</secdns:flag>
                <secdns:protocol>#PROTOCOL#</secdns:protocol>
                <secdns:algorithm>#ALGORITHM#</secdns:algorithm>
                <secdns:publickey>#PUBLIC KEY#</secdns:publickey>
            </secdns:keydata>
        </extension:secdns>
    </extension:create>

    <extension:create>
        <extension:service>
            <service:domainprivacy>#WHOIS PRIVACY#</service:domainprivacy>
        </extension:service>
        <extension:data tld="church">
            <extension:registry>
                <registry:language>#LANGUAGE#</registry:language>
            </extension:registry>
        </extension:data>
    </extension:create>
</request>


<domain:create> (Occurences: 1)
R #DOMAIN.TLD# Domain to be registered
R #SUBSCRIPTION PERIOD# Number of years to register
O #RENEWAL MODE# Domain renewal mode (autoexpire,autorenew) (Default: set as you specified in your user settings)
O #DOMAIN FOLDERID# ID of the folder to put the domain into
O #NAMESERVER PROFILEID# Use a nameserver profile instead of specifying the nameserver details
O #ZONE PROFILEID# Set a zone profile to be applied on domain

<nameserver:create> (Occurences: 2-10)
Note: Repeat this section to specify multiple nameservers. Optional if nameserverprofile:id is provided
R #PRIORITY# Priority of the nameserver (1-9)
R #FULLY QUALIFIED DOMAIN NAME# Fully qualified domain name of the nameserver
R #IP ADDRESS# IPv4 address of the nameserver

<contact:create> (Occurences: 4)
Note: The four contacts admin, billing, tech, org have to be specified.
R #TYPE# admin, billing, tech, org
O #CONTACT PROFILE ID# Use a contact profile instead of specifying the contact details
R #FIRSTNAME# Firstname
R #LASTNAME# Lastname
O #COMPANY# Company
R #ADDRESS LINE 1# Address, Line 1
O #ADDRESS LINE 2# Address, Line 2
O #ADDRESS LINE 3# Address, Line 3
R #ZIP/POSTAL CODE# ZIP/Postal code
R #COUNTRY CODE# Country code (ISO 3166-1-alpha-2)
R #EMAIL ADDRESS# Email address
R #PHONE NUMBER# Phone number format: +999999999
Starting with +country phone code
O #FAX NUMBER# Phone number format: +999999999
Starting with +country phone code

<extension:claims> (Occurences: 0,1)
R #NOTICE ID# Notice id
R #CLAIM KEY# Claim key of the domain
R #ACCEPTED DATE# Client accepted date (Epoch Timestamp format)
R #IP# Client IP address

<extension:service> (Occurences: 0,1)
R #WHOIS PRIVACY# Activate whois privacy on this domain (Yes/No) (Default: No)

<extension:create> (Occurences: 0,1)
<extension:secdns> (Occurences: 0,1)
<secdns:keydata> (Occurences: 0,5)
Note: if you’re using DNSSEC, you will not be able to use EuroDNS name servers
R #FLAG# DNSKEY Flags Field (DNSKEY Flags list)
R #PROTOCOL# DNSKEY Protocol Field (DNSKEY Protocol list)
R #ALGORITHM# DNSKEY Algorithm Field (DNSKEY Algorithm list)
R #PUBLIC KEY# DNSKEY Public Key Field. Base64 encoding of the Public Key

<extension:create>
R #LANGUAGE# IDN language

The following XML code will be returned if the action was successful
<?xml version="1.0" encoding="UTF-8"?>
<response xmlns="http://www.eurodns.com/">
    <result code="1001">
        <msg>Command completed successfully, action pending</msg>
    </result>
    <resData>
        <domain:create>
            <domain:name>#DOMAIN NAME#</domain:name>
            <domain:roid>#DOMAIN ROID#</domain:roid>
        </domain:create>
    </resData>
</response>

<resData> (Occurences: 1)
<domain:create> (Occurences: 1)
R #DOMAIN NAME# Name of the domain that has been ordered
R #DOMAIN ROID# Roid of the domain that has been ordered

Legend
O The element is optional an does not have to be present in the request and/or answer
R The element is mandatory and must be present in the request and/or answer