EPP 1.0 Gateway Resource Guide
|
|
|
- Collin Perkins
- 9 years ago
- Views:
Transcription
1 Resource Guide REALTIME cctld EPP 1.0 SOLUTION HEXONET s Platform is the first of its kind industry wide. Instead of repeated and costly implementation, as well as, maintenance for arduous individual connections for each and every country code Registry, the allows registrars to connect to these same Registries through a single elegant EPP 1.0 protocol connection. EPP 1.0 is the easy way to turn cctlds into a profit center. HIGHLIGHTS Access over 100 cctlds via EPP Non-EPP cctlds made EPP compliant Real-time transactions Quickly open new revenue streams Sell high margin service add-ons SUPPORTED cctlds COUNTRY / cctld COUNTRY / cctld COUNTRY / cctld COUNTRY / cctld.ag - Antigua & Barbuda.AM - Armenia.AC - Ascension Island.AT - Austria.BE - Belgium.BZ - Belize.CA - Canada.CM - Cameroon.CN - China.CC - Cocos Keeling Islands.CX - Christmas Island.CZ - Czech Republic.DK - Denmark.DE - Germany.FR - France.GD - Grenada.HN - Honduras.IN - India.IO - Indian Ocean Territory.IM - Isle of Man.IT - Italy.JP - Japan.KI - Kiribati.LA - Laos Republic.LI - Liechtenstein.LU - Luxembourg.MU - Mauritius.MX - Mexico.FM - Mic.ME - Montenegro.MN - Mongolia.MS - Montserrat.NL - Netherlands.NZ - New Zealand.NU - Niue.PL - Poland.RU - Russia Federation.SH - Saint Helena.VC - St. Vincent & Grenadines.SC - Seychelles.SG - Singapore.GS - S. Georgia & Sandwich Is..ES - Spain.SE - Sweden.CH - Switzerland.TW - Taiwan.TL - Timor-Leste.TK - Tokelau.TM - Turkmenistan.TC - Turks & Caicos.TV - Tuvalu.UK - United Kingdom.US - United States.VG - Virgin Islands (British).WS - West Samoa... and MORE! HOW TO USE THIS GUIDE: This resource guide provides the resellers an overview of the. Standard EPP RFC command and responses are provided for comparison testing the command and responses. Requires an account with HEXONET Test commands and responses with the EPP Gatway using account credentials Implement EPP Gateway for all your cctlds
2 Pg. 1 Table of Contents 1 INTRODUCTION RELEVANT RFC DOCUMENTS TRANSPORT EPP OVER TCP SESSION HANDLING HELLO LOGIN LOGOUT DOMAIN MANAGEMENT CHECK DOMAIN AVAILABILITY DOMAIN NAME SERVER HANDLING CREATE DOMAIN USING NS OBJECTS CREATE DOMAIN USING NS ATTRIBUTES QUERY DOMAIN USING NS OBJECTS QUERY DOMAIN USING NS ATTRIBUTES UPDATE DOMAIN USING NS OBJECTS UPDATE DOMAIN USING NS ATTRIBUTES DELETE DOMAIN RENEW DOMAIN REQUEST DOMAIN TRANSFER CONTACT MANAGEMENT CHECK CONTACT AVAILABILITY CREATE CONTACT QUERY CONTACT UPDATE CONTACT DELETE CONTACT NAME SERVER HOST MANAGEMENT CHECK HOST AVAILABILITY CREATE HOST QUERY HOST UPDATE HOST DELETE HOST MESSAGE POLLING POLL MESSAGE QUEUE ACKNOWLEDGE MESSAGE EXTENSIONS KEY-VALUE EXTENSION... 34
3 Pg. 2 APPENDIX A WORKING EXAMPLES A.1 - AVAILABILITY CHECK FOR.COM,.DE,.CO.UK AND.EU DOMAINS A.2 - REGISTRATION OF A.EU DOMAIN USING REGISTRANT PROXY A.3 - MONTHLY REGISTRATION OF A.DE DOMAIN USING TRUSTEE SERVICE...37 A.4 - REGISTRATION OF A.DE DOMAIN MULTIPLE HOLDERS AND NS ENTRIES...38 A.5 - REGISTRATION OF AN.ASIA DOMAIN USING PROVIDED CED SERVICE...39 A.6 - TRADE OF A.EU DOMAIN A.7 - PUSHING A.CO.UK DOMAIN TO ANOTHER TAG...41 A.8 - PUSHING A.DE DOMAIN TO TRANSIT A.9 - PUSHING A.AT DOMAIN TO REGISTRY (BILLWITHDRAW) A.10 - ACTIVATING AUTHINFO1 FOR A.DE DOMAIN A.11 - DELETING AUTHINFO1 FOR A.DE DOMAIN A.12 - REQUESTING AUTHINFO2 FOR A.DE DOMAIN...45
4 Pg. 3 1 Introduction The provides a strict RFC EPP compatible protocol for handling gtlds and cctlds. The only exception is that the Gateway handles nameserver hosts as both attributes as well as objects. The actual model depends on each TLD and the registry managing it. The Gateway also supports an optional key-value extension, which is only required for additional features like trustee services, multiple registrants or trade commands. This key-value extension encapsulates all command options for a particular TLD not supported by the core EPP protocol mappings. 1.1 Relevant RFC Documents EPP Protocol and Object Mappings RFC 4930 (obsoletes RFC 3730) Extensible Provisioning Protocol (EPP) RFC 4931 (obsoletes RFC 3731) Extensible Provisioning Protocol (EPP) Domain Name Mapping RFC 4932 (obsoletes RFC 3732) Extensible Provisioning Protocol (EPP) Host Mapping RFC 4933 (obsoletes RFC 3733) Extensible Provisioning Protocol (EPP) Contact Mapping RFC 4934 (obsoletes RFC 3734) Extensible Provisioning Protocol (EPP) Transport over TCP EPP Extension Mappings RFC 3735 Guidelines for Extending the Extensible Provisioning Protocol (EPP)
5 Pg. 4 RFC 3915 Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP) RFC 4114 E.164 Number Mapping for the Extensible Provisioning Protocol (EPP) RFC 4310 Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP) RFC 5076 ENUM Validation Information Mapping for the Extensible Provisioning Protocol
6 Pg. 5 2 Transport 2.1 EPP over TCP Connections must be created using TLS/SSL over TCP, to the respective live/test environment. Upon the establishment of a connection (client and server TLS/SSL handshake) the EPP Gateway server will send a greeting message to the client. Gateway pings by sending a hello command will also generate a greeting message back to the client. Each EPP XML request must be encoded in UTF-8, and pre-pended by a 4 byte header, describing its total length in octets in network (big-endian) byte order.
7 Pg. 6 3 Session Handling To start an EPP Gateway session, the client must send a login command using valid credentials. An EPP Gateway session is closed by sending a logout command or simply by closing the TCP connection. After an initial greeting, clients can always query the Gateway by sending a hello command. 3.1 Hello An EPP client MAY request a <greeting> from the EPP server at any time. Often this command is used for checking the status of the EPP server. <hello /> <greeting> <svid>ispapi EPP Server</svID> <svdate> t23:50:25.0z</svdate> <svcmenu> <version>1.0</version> <lang>en</lang> <objuri>urn:ietf:params:xml:ns:contact-1.0</objuri> <objuri>urn:ietf:params:xml:ns:host-1.0</objuri> <objuri>urn:ietf:params:xml:ns:domain-1.0</objuri> <svcextension> <exturi> </svcextension> </svcmenu> <dcp> <access> <all/> </access> <statement> <purpose> <admin/> <prov/> </purpose> <recipient> <ours/> <public/> </recipient> <retention> <stated/> </retention> </statement> </dcp> </greeting>
8 Pg Login An EPP Gateway session must be established before any operations can be sent to the gateway. Additionally, EPP limits login ID to a maximum of 16 characters. <login> <clid>test.user</clid> <pw>test.passw0rd</pw> <options> <version>1.0</version> <lang>en</lang> </options> <svcs> <objuri>urn:ietf:params:xml:ns:host-1.0</objuri> <objuri>urn:ietf:params:xml:ns:contact-1.0</objuri> <objuri>urn:ietf:params:xml:ns:domain-1.0</objuri> <svcextension> <exturi> </svcextension> </svcs> </login> <svtrid>ro </svtrid>
9 Pg Logout An EPP Gateway session in general should be must closed with the Logout command after all instructions are complete, unless for performance reasons you wish to keep the connection open. Please remember that the connection is automatically closed when the TCP timeout occurs or the TCP session is closed. <logout /> <result code="1500"> <msg>command completed successfully; ending session</msg> <svtrid>ro </svtrid>
10 Pg. 9 4 Domain Management Once a session is established the complete set of domain management commands can be issued from checking domain availability, creating a domain, updating a domain s objects, to even deleting a domain. EPP commands issued to the EPP Gateway are process in REAL-TIME and responded back to the client. 4.1 Check Domain Availability Example <check> command: <check> <domain:check <domain:name>example.com</domain:name> <domain:name>example.net</domain:name> <domain:name>example.org</domain:name> </domain:check> </check> Example <check> response: <resdata> <domain:chkdata <domain:cd> <domain:name avail="1">example.com</domain:name> </domain:cd> <domain:cd> <domain:name avail="0">example.net</domain:name> <domain:reason>in use</domain:reason> </domain:cd> <domain:cd> <domain:name avail="1">example.org</domain:name> </domain:cd> </domain:chkdata> </resdata> <svtrid>54322-xyz</svtrid>
11 Pg Domain Name server Handling Name server hosts for domain delegation can be specified as either references to existing host objects or as domain attributes, which describe a host machine. When using domain attributes to describe a name server host, IP addresses should be specified to generate proper DNS glue records. Name servers are specified within a <domain:ns> element. This element MUST contain one or more <domain:hostobj> elements or one (or more) <domain:hostattr> elements. A <domain:hostobj> element contains the fully qualified name of a known name server host object. A <domain:hostattr> element contains the following child elements: A <domain:hostname> element that contains the fully qualified name of a host. Zero or more OPTIONAL <domain:hostaddr> elements that contain the IP addresses to be associated with the host. o Each element MAY contain an "IP" attribute to identify the IP address format. o Attribute value "v4" is used to denote an IPv4 address format. o Attribute value "v6" is used to denote an IPv6 address format. o If the "IP" attribute is not specified, "v4" is the default attribute value. o IP address syntax requirements are described in Section 2.5 of the EPP host mapping [RFC4932]. Domain Host Object Example Example host object name server elements for domain example.com: <domain:ns> <domain:hostobj>ns1.example.com</domain:hostobj> <domain:hostobj>ns1.example.net</domain:hostobj> </domain:ns> Domain Host Attribute Example Example host attribute name server elements for domain example.com: <domain:ns> <domain:hostattr> <domain:hostname>ns1.example.com</domain:hostname> <domain:hostaddr ip="v4"> </domain:hostaddr> <domain:hostaddr ip="v6">1080:0:0:0:8:800:200c:417a</domain:hostaddr> </domain:hostattr> <domain:hostattr> <domain:hostname>ns1.example.net</domain:hostname> </domain:hostattr> </domain:ns>
12 Pg Create Domain Using NS Objects The create command allows the creation of a domain name. During the domain creation process other objects important to a domain are also created. Example <create> command: <create> <domain:create <domain:name>example.com</domain:name> <domain:period unit="y">2</domain:period> <domain:ns> <domain:hostobj>ns1.example.com</domain:hostobj> <domain:hostobj>ns1.example.net</domain:hostobj> </domain:ns> <domain:registrant>jd1234</domain:registrant> <domain:contact type="admin">sh8013</domain:contact> <domain:contact type="tech">sh8013</domain:contact> <domain:authinfo> <domain:pw>2foobar</domain:pw> </domain:authinfo> </domain:create> </create> Example <create> response: <resdata> <domain:credata <domain:name>example.com</domain:name> <domain:crdate> t22:00:00.0z</domain:crdate> <domain:exdate> t22:00:00.0z</domain:exdate> </domain:credata> </resdata> <svtrid>54321-xyz</svtrid>
13 Pg Create Domain Using NS Attributes A create command allowing the creation of a domain name using <domain:hostattr> instead of <domain:hostobj>, in the case where a registry requires creation of a domain through attributes and not objects. The EPP Gateway will automatically convert between the two for most registries. - SNIPPET Example <create> command: <create> <domain:create <domain:name>example.com</domain:name> <domain:period unit="y">2</domain:period> <domain:ns> <domain:hostattr> <domain:hostname>ns1.example.com</domain:hostname> </domain:hostattr> <domain:hostattr> <domain:hostname>ns1.example.net</domain:hostname> </domain:hostattr> </domain:ns> 4.5 Query Domain Using NS Objects The EPP <info> command is used to retrieve information associated with a domain object. Example <info> command: <info> <domain:info <domain:name hosts="all">example.com</domain:name> </domain:info> </info>
14 Pg. 13 Example <info> response for an authorized client: <resdata> <domain:infdata <domain:name>example.com</domain:name> <domain:roid>example1-rep</domain:roid> <domain:status s="ok"/> <domain:registrant>jd1234</domain:registrant> <domain:contact type="admin">sh8013</domain:contact> <domain:contact type="tech">sh8013</domain:contact> <domain:ns> <domain:hostobj>ns1.example.com</domain:hostobj> <domain:hostobj>ns1.example.net</domain:hostobj> </domain:ns> <domain:host>ns1.example.com</domain:host> <domain:host>ns2.example.com</domain:host> <domain:clid>clientx</domain:clid> <domain:crid>clienty</domain:crid> <domain:crdate> t22:00:00.0z</domain:crdate> <domain:upid>clientx</domain:upid> <domain:update> t09:00:00.0z</domain:update> <domain:exdate> t22:00:00.0z</domain:exdate> <domain:trdate> t09:00:00.0z</domain:trdate> <domain:authinfo> <domain:pw>2foobar</domain:pw> </domain:authinfo> </domain:infdata> </resdata> <svtrid>54322-xyz</svtrid> 4.6 Query Domain Using NS Attributes This query command is used exactly as the Using NS Object sample above. The EPP Gateway determines between the registry differences on your behalf. Example <info> command: <info> <domain:info <domain:name hosts="all">example.com</domain:name> </domain:info> </info>
15 Pg Update Domain Using NS Objects The EPP <update> command allows modification of attributes of a domain object. The <update> command MUST contain a <domain:update> element that identifies the domain. The <domain:update> element contains the following child elements: A <domain:name> element that contains the fully qualified name of the domain object to be updated. An OPTIONAL <domain:add> element that contains attribute values to be added to the object. An OPTIONAL <domain:rem> element that contains attribute values to be removed from the object. An OPTIONAL <domain:chg> element that contains object attribute values to be changed. Example <update> command: <update> <domain:update <domain:name>example.com</domain:name> <domain:add> <domain:ns> <domain:hostobj>ns2.example.com</domain:hostobj> </domain:ns> <domain:contact type="tech">mak21</domain:contact> <domain:status s="clienthold" lang="en">payment overdue.</domain:status> </domain:add> <domain:rem> <domain:ns> <domain:hostobj>ns1.example.com</domain:hostobj> </domain:ns> <domain:contact type="tech">sh8013</domain:contact> <domain:status s="clientupdateprohibited"/> </domain:rem> <domain:chg> <domain:registrant>sh8013</domain:registrant> <domain:authinfo> <domain:pw>2barfoo</domain:pw> </domain:authinfo> </domain:chg> </domain:update> </update>
16 Pg. 15 Example <update> response: <svtrid>54321-xyz</svtrid> > 4.8 Update Domain Using NS Attributes In cases where a registry supports NS Attributes instead of NS Objects, replace <domain:hostobj> with <domain:hostattr>. In most cases the EPP Gateway converts between different registries on your behalf. - SNIPPET <domain:add> <domain:ns> <domain:hostattr> <domain:hostname>ns2.example.com</domain:hostname> </domain:hostattr> </domain:ns> <domain:contact type="tech">mak21</domain:contact> <domain:status s="clienthold" lang="en">payment overdue.</domain:status> </domain:add> <domain:rem> <domain:ns> <domain:hostattr> <domain:hostname>ns1.example.com</domain:hostname> </domain:hostattr> </domain:ns> <domain:contact type="tech">sh8013</domain:contact> <domain:status s="clientupdateprohibited"/>
17 Pg Delete Domain The <delete> command allows a client to delete a domain object. In addition to the standard EPP command elements, the <delete> command MUST contain a <domain:delete> element that identifies the domain. Example <delete> command: <delete> <domain:delete <domain:name>example.com</domain:name> </domain:delete> </delete> Example <delete> response: <extvalue> <value xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> <epp:undef/> </value> <reason>200 Command completed successfully</reason> </extvalue> <svtrid>rw </svtrid>
18 Pg Renew Domain The EPP Gateway <renew> command is used to extend the validity period of an existing domain. The elements needed to identify and extend the validity period of a domain include the current expiration date of the domain (<domain:curexpdate>) and the period to extend, which is measured in whole numbers and is of unit y for years. Example <renew> command: <renew> <domain:renew <domain:name>example.com</domain:name> <domain:curexpdate> </domain:curexpdate> <domain:period unit="y">5</domain:period> </domain:renew> </renew> Example <renew> response: <resdata> <domain:rendata <domain:name>example.com</domain:name> <domain:exdate> t22:00:00.0z</domain:exdate> </domain:rendata> </resdata> <svtrid>54322-xyz</svtrid>
19 Pg Request Domain Transfer The <transfer> command is used to manage changes in domain sponsorship of an existing domain. Clients can request, cancel, approve, reject, or query a transfer request using the "op" command attribute. A client who wishes to assume sponsorship of a known domain from another client uses the <transfer> command with the value of the "op" attribute set to "request". Once a transfer has been requested, the same client can cancel the request using a <transfer> command with the value of the "op" attribute set to "cancel". A request to cancel the transfer MUST be sent to the server before the current sponsoring client either approves or rejects the transfer request and before the server automatically processes the request due to responding client inactivity. Once a transfer request has been received by the Gateway, the server MUST notify the current domain sponsor of the requested transfer. The current status of a pending <transfer> command for any domain can be found using the <transfer> query command. The current domain sponsor MAY explicitly approve or reject the transfer request. The client can approve the request using a <transfer> command with the value of the "op" attribute set to "approve". Clients can reject the request using a <transfer> command with the value of the "op" attribute set to "reject". Automatically approving/rejecting transfer requests not explicitly approved or rejected by the current domain sponsor within a fixed amount of time is recommended and left to the developer to implement. Objects eligible for transfer MUST have the associated authorization password to complete a <transfer> command. - Request Example <transfer> request command: <transfer op="request"> <domain:transfer <domain:name>example.com</domain:name> <domain:period unit="y">1</domain:period> <domain:authinfo> <domain:pw>2foobar</domain:pw> </domain:authinfo> </domain:transfer> </transfer>
20 Pg Request Example <transfer> response: <result code="1001"> <msg>command completed successfully; action pending</msg> <resdata> <domain:trndata <domain:name>example.com</domain:name> <domain:trstatus>pending</domain:trstatus> <domain:reid>clientx</domain:reid> <domain:redate> t22:00:00.0z</domain:redate> <domain:acid>clienty</domain:acid> <domain:acdate> t22:00:00.0z</domain:acdate> <domain:exdate> t22:00:00.0z</domain:exdate> </domain:trndata> </resdata> <svtrid>54322-xyz</svtrid> - Approve Example <transfer> approve command: <transfer op="approve"> <domain:transfer <domain:name>example.com</domain:name> </domain:transfer> </transfer> Approve Example <transfer> approve response: <svtrid>54322-xyz</svtrid>
21 Pg Reject Example <transfer> reject command: <transfer op="reject"> <domain:transfer <domain:name>example.com</domain:name> </domain:transfer> </transfer> Reject Example <transfer> reject response: <svtrid>54322-xyz</svtrid> Cancel Example <transfer> cancel command: <transfer op="cancel"> <domain:transfer <domain:name>example.com</domain:name> </domain:transfer> </transfer> Cancel Example <transfer> cancel response: <svtrid>54322-xyz</svtrid>
22 Pg. 21 Query Example <transfer> query command: <transfer op="query"> <domain:transfer <domain:name>example.com</domain:name> <domain:authinfo> <domain:pw roid="jd1234-rep">2foobar</domain:pw> </domain:authinfo> </domain:transfer> </transfer> - Query Example <transfer> query response: <resdata> <domain:trndata <domain:name>example.com</domain:name> <domain:trstatus>pending</domain:trstatus> <domain:reid>clientx</domain:reid> <domain:redate> t22:00:00.0z</domain:redate> <domain:acid>clienty</domain:acid> <domain:acdate> t22:00:00.0z</domain:acdate> <domain:exdate> t22:00:00.0z</domain:exdate> </domain:trndata> </resdata> <svtrid>54322-xyz</svtrid>
23 Pg Contact Management The management of contacts via the EPP Gateway allows for easy checking, creation, deleting, and updating of domain contact handles. 5.1 Check Contact Availability The EPP <check> command is used to determine if a contact exists. It provides a hint that allows a client to anticipate the success or failure of provisioning, changing or deleting an object. Example <check> command: <check> <contact:check xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> <contact:id>sh8013</contact:id> <contact:id>sah8013</contact:id> <contact:id>8013sah</contact:id> </contact:check> </check> Example <check> response: <resdata> <contact:chkdata xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> <contact:cd> <contact:id avail="1">sh8013</contact:id> </contact:cd> <contact:cd> <contact:id avail="0">sah8013</contact:id> <contact:reason>in use</contact:reason> </contact:cd> <contact:cd> <contact:id avail="1">8013sah</contact:id> </contact:cd> </contact:chkdata> </resdata> <svtrid>54322-xyz</svtrid>
24 Pg Create Contact Example <create> command: <create> <contact:create xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> <contact:id>sh8013</contact:id> <contact:postalinfo type="int"> <contact:name>john Doe</contact:name> <contact:org>example Inc.</contact:org> <contact:addr> <contact:street>123 Example Dr.</contact:street> <contact:street>suite 100</contact:street> <contact:city>dulles</contact:city> <contact:sp>va</contact:sp> <contact:pc> </contact:pc> <contact:cc>us</contact:cc> </contact:addr> </contact:postalinfo> <contact:voice x="1234"> </contact:voice> <contact:fax> </contact:fax> <contact:authinfo> <contact:pw>2foobar</contact:pw> </contact:authinfo> </contact:create> </create> Example <create> response: <resdata> <contact:credata xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> <contact:id>sh8013</contact:id> <contact:crdate> t22:00:00.0z</contact:crdate> </contact:credata> </resdata> <svtrid>54321-xyz</svtrid>
25 Pg Query Contact The EPP <info> command is used to retrieve information associated with a contact object. Example <info> command: <info> <contact:info xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> <contact:id>sh8013</contact:id> <contact:authinfo> <contact:pw>2foobar</contact:pw> </contact:authinfo> </contact:info> </info> Example <info> response for an authorized client: <resdata> <contact:infdata xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> <contact:id>sh8013</contact:id> <contact:roid>sh8013-rep</contact:roid> <contact:status s="linked"/> <contact:status s="clientdeleteprohibited"/> <contact:postalinfo type="int"> <contact:name>john Doe</contact:name> <contact:org>example Inc.</contact:org> <contact:addr> <contact:street>123 Example Dr.</contact:street> <contact:street>suite 100</contact:street> <contact:city>dulles</contact:city> <contact:sp>va</contact:sp> <contact:pc> </contact:pc> <contact:cc>us</contact:cc> </contact:addr> </contact:postalinfo> <contact:voice x="1234"> </contact:voice> <contact:fax> </contact:fax> <contact: >[email protected]</contact: > <contact:clid>clienty</contact:clid> <contact:crid>clientx</contact:crid> <contact:crdate> t22:00:00.0z</contact:crdate> <contact:upid>clientx</contact:upid> <contact:update> t09:00:00.0z</contact:update> <contact:trdate> t09:00:00.0z</contact:trdate>
26 Pg. 25 <contact:authinfo> <contact:pw>2foobar</contact:pw> </contact:authinfo> </contact:infdata> </resdata> <svtrid>54322-xyz</svtrid> 5.4 Update Contact The EPP <update> command allows modification of attributes of a contact object. The <update> command MUST contain a <contact:update> element that identifies the contact. The <contact:update> element contains the following child elements: A <contact:id> element that contains the unique id of the contact to be updated. An OPTIONAL <contact:add> element that contains attribute values to be added to the object. An OPTIONAL <contact:rem> element that contains attribute values to be removed from the object. An OPTIONAL <contact:chg> element that contains object attribute values to be changed. Example <update> command: <update> <contact:update xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> <contact:id>sh8013</contact:id> <contact:add> <contact:status s="clientdeleteprohibited"/> </contact:add> <contact:chg> <contact:postalinfo type="int"> <contact:org/> <contact:addr> <contact:street>124 Example Dr.</contact:street> <contact:street>suite 200</contact:street> <contact:city>dulles</contact:city> <contact:sp>va</contact:sp> <contact:pc> </contact:pc> <contact:cc>us</contact:cc> </contact:addr> </contact:postalinfo> <contact:voice> </contact:voice> <contact:fax/>
27 Pg. 26 <contact:authinfo> <contact:pw>2foobar</contact:pw> </contact:authinfo> </contact:chg> </contact:update> </update> Example <update> response: <svtrid>54321-xyz</svtrid> 5.5 Delete Contact The <delete> command allows a client to delete a contact object. In addition to the standard EPP command elements, the <delete> command MUST contain a <contact:delete> that identifies the contact. Example <delete> command: <delete> <contact:delete xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"> <contact:id>sh8013</contact:id> </contact:delete> </delete> Example <delete> response: <svtrid>54321-xyz</svtrid>
28 Pg Name server Host Management The management of name servers via the EPP Gateway allows for easy checking, creation, deleting, and updating of name servers. 6.1 Check Host Availability The EPP <check> command is used to determine if a name server host exists. It provides a hint that allows a client to anticipate the success or failure of provisioning, changing or deleting a name server host object. Example <check> command: <check> <host:check xmlns:host="urn:ietf:params:xml:ns:host-1.0"> <host:name>ns1.example.com</host:name> <host:name>ns2.example.com</host:name> <host:name>ns3.example.com</host:name> </host:check> </check> Example <check> response: <resdata> <host:chkdata xmlns:host="urn:ietf:params:xml:ns:host-1.0"> <host:cd> <host:name avail="1">ns1.example.com</host:name> </host:cd> <host:cd> <host:name avail="0">ns2.example2.com</host:name> <host:reason>in use</host:reason> </host:cd> <host:cd> <host:name avail="1">ns3.example3.com</host:name> </host:cd> </host:chkdata> </resdata> <svtrid>54322-xyz</svtrid>
29 Pg Create Host Name server hosts can be created using the <host:create> element. Child elements include: A <host:name> element that contains the fully qualified name of a host. Zero or more OPTIONAL <host:addr> elements that contain the IP addresses to be associated with the host. o Each element MAY contain an "IP" attribute to identify the IP address format. o Attribute value "v4" is used to denote an IPv4 address format. o Attribute value "v6" is used to denote an IPv6 address format. o If the "IP" attribute is not specified, "v4" is the default attribute value. Example <create> command: <create> <host:create xmlns:host="urn:ietf:params:xml:ns:host-1.0"> <host:name>ns1.example.com</host:name> <host:addr ip="v4"> </host:addr> <host:addr ip="v4"> </host:addr> <host:addr ip="v6">1080:0:0:0:8:800:200c:417a</host:addr> </host:create> </create> Example <create> response: <resdata> <host:credata xmlns:host="urn:ietf:params:xml:ns:host-1.0"> <host:name>ns1.example.com</host:name> <host:crdate> t22:00:00.0z</host:crdate> </host:credata> </resdata> <svtrid>54322-xyz</svtrid>
30 Pg Query Host The EPP <info> command is used to retrieve information associated with a host object. Example <info> command: <info> <host:info xmlns:host="urn:ietf:params:xml:ns:host-1.0"> <host:name>ns1.example.com</host:name> </host:info> </info> Example <info> response: <resdata> <host:infdata xmlns:host="urn:ietf:params:xml:ns:host-1.0"> <host:name>ns1.example.com</host:name> <host:roid>ns1_example1-rep</host:roid> <host:status s="linked"/> <host:status s="clientupdateprohibited"/> <host:addr ip="v4"> </host:addr> <host:addr ip="v4"> </host:addr> <host:addr ip="v6">1080:0:0:0:8:800:200c:417a</host:addr> <host:clid>clienty</host:clid> <host:crid>clientx</host:crid> <host:crdate> t22:00:00.0z</host:crdate> <host:upid>clientx</host:upid> <host:update> t09:00:00.0z</host:update> <host:trdate> t09:00:00.0z</host:trdate> </host:infdata> </resdata> <svtrid>54322-xyz</svtrid>
31 Pg Update Host The EPP <update> command for name sever hosts allows modification of attributes of a host object. The <update> command MUST contain a <host:update> element that identifies the host. The <host:update> element contains the following child elements: A <host:name> element that contains full qualified name of the host to be updated. An OPTIONAL <host:add> element that contains attribute values to be added to the object. An OPTIONAL <host:rem> element that contains attribute values to be removed from the object. An OPTIONAL <host:chg> element that contains object attribute values to be changed. Example <update> command: <update> <host:update xmlns:host="urn:ietf:params:xml:ns:host-1.0"> <host:name>ns1.example.com</host:name> <host:add> <host:addr ip="v4"> </host:addr> <host:status s="clientupdateprohibited"/> </host:add> <host:rem> <host:addr ip="v6">1080:0:0:0:8:800:200c:417a</host:addr> </host:rem> <host:chg> <host:name>ns2.example.com</host:name> </host:chg> </host:update> </update> Example <update> response: <svtrid>54321-xyz</svtrid>
32 Pg Delete Host The <delete> command allows a client to delete a name server host object. In addition to the standard EPP command elements, the <delete> command MUST contain a <host:delete> that identifies the host. Example <delete> command: <delete> <host:delete xmlns:host="urn:ietf:params:xml:ns:host-1.0"> <host:name>ns1.example.com</host:name> </host:delete> </delete> Example <delete> response: <svtrid>54321-xyz</svtrid>
33 Pg Message Polling Discover and retrieve service messages from the EPP Gateway. 7.1 Poll Message Queue The EPP <poll> command is used to discover and retrieve service messages queued by the EPP Gateway. Each response returned from the server will include a server-unique message identifier, which will be required for acknowledging the receipt of a message. A counter exists to indicate the number of messages in the queue. After a client has received a message, the client MUST respond to the message with an explicit acknowledgement to confirm that the message has been received to make the next message in the queue (if any) available for retrieval. The <poll> command MUST be represented as an empty element with no child elements. An "op" attribute with value "req" is REQUIRED to retrieve the first message from the server message queue. Example <poll> command: <poll op="req"/> Example <poll> response with object-specific information: <result code="1301"> <msg>command completed successfully; ack to dequeue</msg> <msgq count="5" id="12345"> <qdate> t22:00:00.0z</qdate> <msg>transfer requested.</msg> </msgq> <resdata> <obj:trndata xmlns:obj="urn:ietf:params:xml:ns:obj-1.0"> <obj:name>example.com</obj:name> <obj:trstatus>pending</obj:trstatus> <obj:reid>clientx</obj:reid> <obj:redate> t22:00:00.0z</obj:redate> <obj:acid>clienty</obj:acid> <obj:acdate> t22:00:00.0z</obj:acdate> <obj:exdate> t22:00:00.0z</obj:exdate> </obj:trndata> </resdata>
34 Pg. 33 <svtrid>54321-xyz</svtrid> 7.2 Acknowledge Message After a client has received a message, the client MUST respond to the message with an explicit acknowledgement to confirm that the message has been received to make the next message in the queue (if any) available for retrieval. The <poll> command MUST be represented as an empty element with no child elements. An "op" attribute (with value "ack") and a "msgid" attribute (whose value corresponds to the value of the "id" attribute copied from the <msg> element in the message being acknowledged) are REQUIRED to acknowledge receipt of a message. Example <poll> acknowledgement command: <poll op="ack" msgid="12345"/> <cltrid>abc-12346</cltrid> Example <poll> acknowledgement response: <msgq count="4" id="12345"/> <cltrid>abc-12346</cltrid> <svtrid>54322-xyz</svtrid>
35 Pg Extensions The base EPP protocol does not support or make available some commands required to map all domain functionality. However, the EPP Gateway server supports xml base key-value extensions for this purpose. 8.1 Key-Value Extension The EPP Gateway supports xml based key-value extensions, which enables the use of commands and parameters not supported by the base EPP protocol. Below is the formal syntax. <?xml version="1.0" encoding="utf-8"?> <schema targetnamespace=" xmlns:keyvalue=" xmlns=" elementformdefault="qualified"> <!-- Child elements found in EPP commands. --> <element name="extension" type="keyvalue:extensiontype"/> <!-- Utility Types --> <complextype name="extensiontype"> <sequence> <element name="kv" type="keyvalue:kvtype" minoccurs="0" maxoccurs="unbounded"/> </sequence> </complextype> <complextype name="kvtype"> <attribute name="key" type="keyvalue:keytype" use="required"/> <attribute name="value" type="keyvalue:valuetype" use="required"/> </complextype> <simpletype name="keytype"> <restriction base="token"> <minlength value="1"/> <pattern value="[a-z0-9\-]*"/> </restriction> </simpletype> <simpletype name="valuetype"> <restriction base="token"> <minlength value="0"/> </restriction> </simpletype> <!-- End of schema. --> </schema>
36 Pg. 35 APPENDIX A Working Examples A.1 - Availability check for.com,.de,.co.uk and.eu Domains <check> <domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xsi:schemalocation="urn:ietf:params:xml:ns:domain-1.0 domain-1.0.xsd"> <domain:name>test12345.com</domain:name> <domain:name>test12345.de</domain:name> <domain:name>test12345.co.uk</domain:name> <domain:name>test12345.eu</domain:name> </domain:check> </check> <resdata> <domain:chkdata xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xsi:schemalocation="urn:ietf:params:xml:ns:domain-1.0 domain-1.0.xsd"> <domain:cd> <domain:name avail="1">test12345.com</domain:name> </domain:cd> <domain:cd> <domain:name avail="1">test12345.de</domain:name> </domain:cd> <domain:cd> <domain:name avail="0">test12345.co.uk</domain:name> </domain:cd> <domain:cd> <domain:name avail="0">test12345.eu</domain:name> </domain:cd> </domain:chkdata> </resdata> <svtrid>ro </svtrid>
37 Pg. 36 A.2 - Registration of a.eu Domain using Registrant Proxy <create> <domain:create <domain:name>trustee.eu</domain:name> <domain:period unit="y">1</domain:period> <domain:ns> <domain:hostobj>ns1.hexonet.net</domain:hostobj> <domain:hostobj>ns2.hexonet.net</domain:hostobj> </domain:ns> <domain:registrant>p-ail28309</domain:registrant> <domain:contact type="admin">p-ail28309</domain:contact> <domain:contact type="tech">p-ail28309</domain:contact> <domain:contact type="billing">p-ail28309</domain:contact> <domain:authinfo> <domain:pw>2foobar</domain:pw> </domain:authinfo> </domain:create> </create> <extension> <keyvalue:extension xmlns:keyvalue=' <keyvalue:kv key='x-eu-accept-trustee-tac' value='1' /> </keyvalue:extension> </extension> <extvalue> <value xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> <epp:undef/> </value> <reason>200 Command completed successfully</reason> </extvalue> <resdata> <domain:credata xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xsi:schemalocation="urn:ietf:params:xml:ns:domain-1.0 domain-1.0.xsd"> <domain:name>trustee.eu</domain:name> <domain:crdate> t14:40:53.0z</domain:crdate> <domain:exdate> t14:40:53.0z</domain:exdate> </domain:credata> </resdata> <extension> <keyvalue:extension xmlns:keyvalue=" xsi:schemalocation=" keyvalue-1.0.xsd"/> </extension> <svtrid>rw </svtrid>
38 Pg. 37 A.3 - Monthly registration of a.de Domain using Trustee Service <create> <domain:create <domain:name>1month.de</domain:name> <domain:period unit="m">1</domain:period> <domain:ns> <domain:hostobj>ns1.hexonet.net</domain:hostobj> <domain:hostobj>ns2.hexonet.net</domain:hostobj> </domain:ns> <domain:registrant>p-ail28309</domain:registrant> <domain:contact type="admin">p-ail28309</domain:contact> <domain:contact type="tech">p-ail28309</domain:contact> <domain:contact type="billing">p-ail28309</domain:contact> <domain:authinfo> <domain:pw>2foobar</domain:pw> </domain:authinfo> </domain:create> </create> <extension> <keyvalue:extension xmlns:keyvalue=' <keyvalue:kv key='x-de-accept-trustee-tac' value='1' /> </keyvalue:extension> </extension> <extvalue> <value xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> <epp:undef/> </value> <reason>200 Command completed successfully</reason> </extvalue> <resdata> <domain:credata xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xsi:schemalocation="urn:ietf:params:xml:ns:domain-1.0 domain-1.0.xsd"> <domain:name>1month.de</domain:name> <domain:crdate> t14:40:53.0z</domain:crdate> <domain:exdate> t02:40:47.0z</domain:exdate> </domain:credata> </resdata> <extension> <keyvalue:extension xmlns:keyvalue=" xsi:schemalocation=" keyvalue-1.0.xsd"/> </extension> <svtrid>rw </svtrid>
39 Pg. 38 A.4 - Registration of a.de Domain multiple Holders and NS entries <create> <domain:create <domain:name>multiholder.de</domain:name> <domain:period unit="y">1</domain:period> <domain:registrant>p-ail28309</domain:registrant> <domain:contact type="admin">p-ail28309</domain:contact> <domain:contact type="tech">p-ail28309</domain:contact> <domain:contact type="billing">p-ail28309</domain:contact> <domain:authinfo> <domain:pw>2foobar</domain:pw> </domain:authinfo> </domain:create> </create> <extension> <keyvalue:extension xmlns:keyvalue=' <!-- OWNERCONTACT0 already set by <domain:registrant> --> <keyvalue:kv key='ownercontact1' value='p-alx29517' /> <keyvalue:kv key='ownercontact2' value='p-taf28559' /> <keyvalue:kv key='x-de-nsentry0' value=' IN A ' /> <keyvalue:kv key='x-de-nsentry1' value='mail.multiholder.de IN A ' /> <keyvalue:kv key='x-de-nsentry2' value='multiholder.de IN MX 100 mail.multiholder.de.' /> </keyvalue:extension> </extension> <extvalue> <value xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> <epp:undef/> </value> <reason>200 Command completed successfully</reason> </extvalue> <resdata> <domain:credata xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xsi:schemalocation="urn:ietf:params:xml:ns:domain-1.0 domain-1.0.xsd"> <domain:name>multiholder.de</domain:name> <domain:crdate> t15:23:43.0z</domain:crdate> <domain:exdate> t15:23:40.0z</domain:exdate> </domain:credata> </resdata> <extension> <keyvalue:extension xmlns:keyvalue=" xsi:schemalocation=" keyvalue-1.0.xsd"/> </extension> <svtrid>rw </svtrid>
40 Pg. 39 A.5 - Registration of an.asia Domain using provided CED Service <create> <domain:create <domain:name>trustee.asia</domain:name> <domain:period unit="y">1</domain:period> <domain:ns> <domain:hostobj>ns1.hexonet.net</domain:hostobj> <domain:hostobj>ns2.hexonet.net</domain:hostobj> </domain:ns> <domain:registrant>p-ail28309</domain:registrant> <domain:contact type="admin">p-ail28309</domain:contact> <domain:contact type="tech">p-ail28309</domain:contact> <domain:contact type="billing">p-ail28309</domain:contact> <domain:authinfo> <domain:pw>2foobar</domain:pw> </domain:authinfo> </domain:create> </create> <extension> <keyvalue:extension xmlns:keyvalue=' <keyvalue:kv key='x-asia-ced-accept-trustee-tac' value='1' /> </keyvalue:extension> </extension> <extvalue> <value xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> <epp:undef/> </value> <reason>200 Command completed successfully</reason> </extvalue> <resdata> <domain:credata xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xsi:schemalocation="urn:ietf:params:xml:ns:domain-1.0 domain-1.0.xsd"> <domain:name>trustee.asia</domain:name> <domain:crdate> t15:23:43.0z</domain:crdate> <domain:exdate> t15:23:40.0z</domain:exdate> </domain:credata> </resdata> <extension> <keyvalue:extension xmlns:keyvalue=" xsi:schemalocation=" keyvalue-1.0.xsd"/> </extension> <svtrid>rw </svtrid>
41 Pg. 40 A.6 - Trade of a.eu Domain <update> <domain:update <domain:name>trustee.eu</domain:name> <domain:chg> <domain:registrant>p-ail28309</domain:registrant> </domain:chg> </domain:update> </update> <extension> <keyvalue:extension xmlns:keyvalue=' <keyvalue:kv key='command' value='tradedomain' /> </keyvalue:extension> </extension> <extvalue> <value xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> <epp:undef/> </value> <reason>200 Command completed successfully</reason> </extvalue> <extension> <keyvalue:extension xmlns:keyvalue=" xsi:schemalocation=" keyvalue-1.0.xsd"/> </extension> <svtrid>rw </svtrid>
42 Pg. 41 A.7 - Pushing a.co.uk Domain to another TAG <update> <domain:update <domain:name>push.co.uk</domain:name> </domain:update> </update> <extension> <keyvalue:extension xmlns:keyvalue=' <keyvalue:kv key='command' value='pushdomain' /> <keyvalue:kv key='target' value='new-tag' /> </keyvalue:extension> </extension> A.8 - Pushing a.de Domain to TRANSIT <update> <domain:update <domain:name>push.de</domain:name> </domain:update> </update> <extension> <keyvalue:extension xmlns:keyvalue=' <keyvalue:kv key='command' value='pushdomain' /> <keyvalue:kv key='target' value='transit' /> </keyvalue:extension> </extension>
43 Pg. 42 A.9 - Pushing a.at Domain to Registry (billwithdraw) <update> <domain:update <domain:name>push.at</domain:name> </domain:update> </update> <extension> <keyvalue:extension xmlns:keyvalue=' <keyvalue:kv key='command' value='pushdomain' /> <keyvalue:kv key='target' value='registry' /> </keyvalue:extension> </extension>
44 Pg. 43 A.10 - Activating AuthInfo1 for a.de Domain <update> <domain:update <domain:name>1month.de</domain:name> <domain:chg> <domain:auth><domain:pw>secret123</domain:pw></domain:auth> </domain:chg> </domain:update> </update> <extension> <keyvalue:extension xmlns:keyvalue=' <keyvalue:kv key='command' value='denic_createauthinfo1' /> </keyvalue:extension> </extension> <extvalue> <value xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> <epp:undef/> </value> <reason>200 Command completed successfully</reason> </extvalue> <extension> <keyvalue:extension xmlns:keyvalue=" xsi:schemalocation=" keyvalue-1.0.xsd"> <keyvalue:kv key="x-de-authinfo1-expirationdate" value=" "/> </keyvalue:extension> </extension> <svtrid>rw </svtrid>
45 Pg. 44 A.11 - Deleting AuthInfo1 for a.de Domain <update> <domain:update <domain:name>1month.de</domain:name> </domain:update> </update> <extension> <keyvalue:extension xmlns:keyvalue=' <keyvalue:kv key='command' value='denic_deleteauthinfo1' /> </keyvalue:extension> </extension> <extvalue> <value xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> <epp:undef/> </value> <reason>200 Command completed successfully</reason> </extvalue> <extension> <keyvalue:extension xmlns:keyvalue=" xsi:schemalocation=" keyvalue-1.0.xsd"/> </extension> <svtrid>rw </svtrid>
46 Pg. 45 A.12 - Requesting AuthInfo2 for a.de Domain <update> <domain:update <domain:name>1month.de</domain:name> </domain:update> </update> <extension> <keyvalue:extension xmlns:keyvalue=' <keyvalue:kv key='command' value='denic_createauthinfo2' /> </keyvalue:extension> </extension> <extvalue> <value xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> <epp:undef/> </value> <reason>200 Command completed successfully</reason> </extvalue> <extension> <keyvalue:extension xmlns:keyvalue=" xsi:schemalocation=" keyvalue-1.0.xsd"/> </extension> <svtrid>rw </svtrid>
SWITCH, Werdstrasse 2, P.O. Box, CH-8021 Zürich www.nic.ch. EPP Manual. Version 2.1.2 with DNSSEC and RGP. November 7, 2013 SWITCH
EPP Manual Version 2.1.2 with DNSSEC and RGP November 7, 2013 SWITCH Contents 1 Management Summary... 3 2 Introduction... 3 2.1 EPP standard + legal fundaments... 4 2.2 Conditions of use... 4 3 Using the
Creating Accounts... 3. Domain Management... 6
Domain Reseller User Guide Table of Contents Creating Accounts... 3 User Registration... 3 Domain Reseller Account Application... 4 Domain Management... 6 Register Domains... 6 Renew Domains... 8 List
Global Registry Services Registrar Frequently Asked Questions (FAQ) for TLDs using Afilias Technology
Global Registry Services Registrar Frequently Asked Questions (FAQ) for TLDs using Afilias Technology Prepared by Afilias November 2013 Table of Contents Foreword... 1 Non-Technical... 1 Accreditation,
Specifications for Registrars' Interaction with Flexireg Domain Registration System
Foundation for Assistance for Internet Technologies and Infrastructure Development Specifications for Registrars' Interaction with Flexireg Domain Registration System Version 1.1. Moscow, 2015 Table of
.INFO Agreement Appendix 1 Data Escrow Specification (22 August 2013)
.INFO Agreement Appendix 1 Data Escrow Specification (22 August 2013) Registry Operator and ICANN agree to engage in good faith negotiations to replace this Appendix with a Data Escrow Specification equivalent
OpenSRS Domain Transfers Guide. October 23, 2008
OpenSRS Domain Transfers Guide October 23, 2008 Table of Contents Introduction...3 About this Document...3 Users and Roles...4 General Transfer Rules...4 Domain Transfers in the Test Environment (Horizon)...4
Pre Delegation Testing (PDT) Frequently Asked Questions (FAQ)
Pre Delegation Testing (PDT) Frequently Asked Questions (FAQ) [Ver 1.7 2013-06- 04] List of contents General questions Who do I contact with questions about Pre- Delegation Testing?... 3 What is the process
NAT TCP SIP ALG Support
The feature allows embedded messages of the Session Initiation Protocol (SIP) passing through a device that is configured with Network Address Translation (NAT) to be translated and encoded back to the
Specifications for Registrars' Interaction with the Domain Registration System During Landrush and General Registration Periods
Фонд содействия развитию технологий и инфраструктуры Интернета Введено в действие: 24 сентября 2014 г. Foundation for Assistance for Internet Technologies and Infrastructure Development Specifications
OpenSRS Quickstart Guide April 15, 2011
OpenSRS Quickstart Guide April 15, 2011 Table of Contents Welcome to OpenSRS...3 Overview...3 Before You Begin...3 Our Two Environments: Live and Test...3 The OpenSRS Test Environment...4 The OpenSRS Live
Vodafone Business Product Management Group. Web and Domain Frequently Asked Questions (FAQs)
Vodafone Business Product Management Group Hosted Services Web and Domain Frequently Asked Questions (FAQs) Vodafone Group 2010 Other than as permitted by law, no part of this document may be reproduced,
Manual for Registrars. Automated Interface. General Availability
Manual for Registrars Automated Interface General Availability 1. What is an API? An application programming interface (API) is the interface that a computer system, library or application provides in
How to Transfer Domain Names and Get an Authorization Code
The Insider s Guide to Domain Name Transfers The Insider s Guide to Domain Name Transfers Version 1.0 (9/29/2011) Copyright 2011. All rights reserved. Distribution of this work or derivative of this work
THE MOST EFFICIENT DOmAIN management SERvICE IN THE WORLD
THE MOST EFFICIENT DOmAIN management SERvICE IN THE WORLD Realtime Register has been active in the web hosting and domain name industry for more than 10 years and has been IcaNN accredited since 2004.
1999-2006 enom, Inc. API response codes
API response codes Introduction When you run a query against the enom API, the response includes a numeric code and a corresponding text message. This allows us to standardize our responses and make them
API Commands Reseller Partners
API Commands Reseller Partners API Version 6.9 Revision Date: 21 st August 2014 Contents Commands... 3 useradd... 3 usermodify... 5 userget... 7 usersuspend... 9 domainadd... 10 domaincancel... 13 domaincheck...
First version of the document.
First version of the document. 2.1 Access to web forms... 6 2.2 Menu... 7 2.3 Dashboard... 8 2.4 Domain names... 9 2.4.1 Create domain name... 9 2.4.2 Query domain name details...11 2.4.3 Registrar domain
Registrar Ramp Up Process. Prepared by Afilias
Registrar Ramp Up Process Prepared by Afilias December 2013 Contents Introduction... 2 Get Started By Having Someone Contact You... 2 Become a Registrar... 3 Step One Business and Legal Process... 3 Step
SDNP.mw cctld DOMAIN REGISTRATION POLICY Ver 1.2 of 23 July 2015
SDNP.mw cctld DOMAIN REGISTRATION POLICY Ver 1.2 of 23 July 2015 Table of Contents 1. DEFNITIONS 2. PURPOSE AND SCOPE 3. ELIGIBILITY 4. CHOOSING A DOMAIN NAME TO REGISTER 5. SELECTING A REGISTRAR 6. REGISTERING
Computer Networks: Domain Name System
Computer Networks: Domain Name System Domain Name System The domain name system (DNS) is an application-layer protocol for mapping domain names to IP addresses DNS www.example.com 208.77.188.166 http://www.example.com
October 11, 2013 NEUSTAR REGISTRAR REFERENCE GUIDE
October 11, 2013 NEUSTAR REGISTRAR REFERENCE GUIDE This document is for informational purposes only. NEUSTAR MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
Domain Name Expiry Renewal and Deletion
Domain Name Expiry Renewal and Deletion Copyright 2010 Supreme Council of Information and Communication Technology (ictqatar) Table of Contents 1. Grace Period... 4 2. Domain Name Deletion Registrant Request
SIP : Session Initiation Protocol
: Session Initiation Protocol EFORT http://www.efort.com (Session Initiation Protocol) as defined in IETF RFC 3261 is a multimedia signaling protocol used for multimedia session establishment, modification
DATA COMMUNICATOIN NETWORKING
DATA COMMUNICATOIN NETWORKING Instructor: Ouldooz Baghban Karimi Course Book: Computer Networking, A Top-Down Approach By: Kurose, Ross Introduction Course Overview Basics of Computer Networks Internet
My Services Online Service Support. User Guide for DNS and NTP services
My Services Online Service Support User Guide for DNS and NTP services Table of Contents 1 MY SERVICES... 3 2 ACCESSING MY SERVICES VIA THE INTERNET... 3 2.1 Logging into My Services... 3 2.2 My Services
Implementing MDaemon as an Email Security Gateway to Exchange Server
Implementing MDaemon as an Email Security Gateway to Exchange Server Introduction MDaemon is widely deployed as a very effective antispam/antivirus gateway to Exchange. For optimum performance, we recommend
F-SECURE MESSAGING SECURITY GATEWAY
F-SECURE MESSAGING SECURITY GATEWAY DEFAULT SETUP GUIDE This guide describes how to set up and configure the F-Secure Messaging Security Gateway appliance in a basic e-mail server environment. AN EXAMPLE
Internet Technology 2/13/2013
Internet Technology 03r. Application layer protocols: email Email: Paul Krzyzanowski Rutgers University Spring 2013 1 2 Simple Mail Transfer Protocol () Defined in RFC 2821 (April 2001) Original definition
Syra Reseller System
Syra Reseller System Reseller Guide Syra Reseller Guide 1 Copyright 2013 Syra Networks Welcome On behalf of the entire team at Syra Networks, welcome to your new reseller account. The Syra Reseller System
Wharf T&T Limited DDoS Mitigation Service Customer Portal User Guide
Table of Content I. Note... 1 II. Login... 1 III. Real-time, Daily and Monthly Report... 3 Part A: Real-time Report... 3 Part 1: Traffic Details... 4 Part 2: Protocol Details... 5 Part B: Daily Report...
Section 1 Overview... 4. Section 2 Home... 5
ecogent User Guide 2012 Cogent Communications, Inc. All rights reserved. Every effort has been made to ensure that the information in this User Guide is accurate. Information in this document is subject
EPP Status Codes: What do they mean, and why should I know?
EPP Status Codes: What do they mean, and why should I know? Extensible Provisioning Protocol (EPP) domain status codes, also called domain name status codes, indicate the status of a domain name registration.
SOA Software API Gateway Appliance 7.1.x Administration Guide
SOA Software API Gateway Appliance 7.1.x Administration Guide Trademarks SOA Software and the SOA Software logo are either trademarks or registered trademarks of SOA Software, Inc. Other product names,
Preparing your Domain to transfer from Go Daddy
Preparing your Domain to transfer from Go Daddy Before you can transfer a domain: Getting Started Disable domain privacy. If the privacy service forwards incoming email, check the ʻforward toʼ contact
Creating your own service profile for SJphone
SJ Labs, Inc. 2005 All rights reserved SJphone is a registered trademark. No part of this document may be copied, altered, or transferred to, any other media without written, explicit consent from SJ Labs
Fasthosts Internet Parallels Plesk 10 Manual
Fasthosts Internet Parallels Plesk 10 Manual Introduction... 2 Before you begin... 2 Logging in to the Plesk control panel... 2 Securing access to the Plesk 10 control panel... 3 Configuring your new server...
IDP. User Manual v3.0. Section 4: Domain Transfers. www.safenames.net
IDP User Manual v3.0 Section 4: Domain Transfers www.safenames.net Table of Contents Domain Transfers... 3 Transfers In... 3 Transfers Out UNLOCK domains.... 7 Where do I find my AuthCode / Domain Password?...
Domain Name Registration Agreement
Domain Name Registration Agreement THIS AGREEMENT HAS A PROVISION FOR ARBITRATION OF DISPUTES BETWEEN THE PARTIES. This Services Agreement ("Agreement") sets forth the terms and conditions of your use
Managing Your Domain Names
Quick Start Guide Managing Your Domain Names Quick Start Guide Page 1 Quick Start Guide: Managing Your Domain Names Version 2.0 (7/22/2010) Copyright 2010 All rights reserved. Distribution of this work
.eu Domain Name Registration Policy v.7.0
.eu Domain Name Registration Policy 1/13 TABLE OF CONTENTS Table of Contents... 2 Definitions... 3 Object and Scope... 3 Section 1. The registrant must determine whether it meets the General Eligibility
Domain Name Renewal, Expiry & Deletion Policy
Domain Name Renewal, Expiry & Deletion Policy AEDA-POL-012 Version 1.0 Issue Date 21/04/2008 The.ae Domain Administration.aeDA PO Box 116688 Dubai, United Arab Emirates (UAE) www.aeda.ae Copyright 2008
Talk-101 User Guide. DNSGate
Talk-101 User Guide DNSGate What is DNSGate? DNSGate is a management interface to allow you to make DNS changes to your domain. The interface supports A, CNAME, MX and TXT records. What is DNS? DNS stands
THIRD-LEVEL DOMAIN NAMES REGISTRATION POLICY
Foundation for Assistance for Internet Technologies and Infrastructure Development Effective April 21, 2015 Version 1.0 THIRD-LEVEL DOMAIN NAMES REGISTRATION POLICY This Third-Level Domain Names Registration
Integrating Avaya Aura Presence Services with Microsoft OCS
Integrating Avaya Aura Presence Services with Microsoft OCS 6.1 Service Pack 5 December 2012 Contents Chapter 1: Introduction... 5 Overview - OCS/Lync integration... 5 The Presence Services server and
ACS 5.x and later: Integration with Microsoft Active Directory Configuration Example
ACS 5.x and later: Integration with Microsoft Active Directory Configuration Example Document ID: 113571 Contents Introduction Prerequisites Requirements Components Used Conventions Background Information
1 Introduction: Network Applications
1 Introduction: Network Applications Some Network Apps E-mail Web Instant messaging Remote login P2P file sharing Multi-user network games Streaming stored video clips Internet telephone Real-time video
API of DNS hosting. For DNS-master and Secondary services Table of contents
API of DNS hosting. For DNS-master and Secondary services Table of contents API of DNS hosting. For DNS-master and Secondary services... 1 1. Introduction... 3 2. Setting access area of application for
General Terms & Conditions for the Registration of.vg Domain Names April 14, 2014
General Terms & Conditions for the Registration of.vg Domain Names April 14, 2014 KSregistry GmbH (operating under the trade name Nic.VG) administers and operates the registry for internet Domain Names
Computer Networks. Chapter 5 Transport Protocols
Computer Networks Chapter 5 Transport Protocols Transport Protocol Provides end-to-end transport Hides the network details Transport protocol or service (TS) offers: Different types of services QoS Data
IBM SPSS Collaboration and Deployment Services Version 6 Release 0. Single Sign-On Services Developer's Guide
IBM SPSS Collaboration and Deployment Services Version 6 Release 0 Single Sign-On Services Developer's Guide Note Before using this information and the product it supports, read the information in Notices
Enterprise Architecture Office Resource Document Design Note - Domain Name System (DNS)
Date: 8/27/2012 Enterprise Architecture Office Resource Document Design Note - Domain Name System (DNS) Table of Contents 1 Overview...2 1.1 Other Resources...2 1.1.1 State of Minnesota Standards and Guidelines...2
GENERAL TERMS AND CONDITIONS for Registration of National Internet Domain Names
Pursuant to Article 27 Paragraph 1 of the Statute of the Serbian National Register of Internet Domain Names Foundation, the Conference of Co-Founders of the "Serbian National Register of Internet Domain
FTP Service Reference
IceWarp Server FTP Service Reference Version 10 Printed on 12 August, 2009 i Contents FTP Service 1 V10 New Features... 2 FTP Access Mode... 2 FTP Synchronization... 2 FTP Service Node... 3 FTP Service
ICE for Eclipse. Release 9.0.1
ICE for Eclipse Release 9.0.1 Disclaimer This document is for informational purposes only and is subject to change without notice. This document and its contents, including the viewpoints, dates and functional
Plesk 11 Manual. Fasthosts Customer Support
Fasthosts Customer Support Plesk 11 Manual This guide covers everything you need to know in order to get started with the Parallels Plesk 11 control panel. Contents Introduction... 3 Before you begin...
.ASIA Reserved Names Policies
Prepared by: DotAsia Organisation Date: 10-Aug-2007 Reference #: N/A Status: Complete Version: 2.0 Executive Summary This document describes the Reserved Names Policies for the.asia Registry. These policies
Technical Integration Guide
TECHNICAL INTEGRATION GUIDE February 25th, 2013 1 Technical Integration Guide - Version 2.7 - February 25th, 2013-1 - TECHNICAL INTEGRATION GUIDE February 25th, 2013 2 Table of content 1. Preface... 5
1.3 By requesting us to register or manage a domain names or names on your behalf, you agree to:
SPECIAL TERMS AND CONDITIONS FOR DOMAIN NAME MANAGEMENT SERVICES (DOMAIN PORTFOLIO MANAGEMENT SERVICE, LOCAL PRESENCE SERVICES AND ANONYMOUS REGISTRATION SERVICES) 1. Services 1.1 These Special Terms and
Sonian Getting Started Guide October 2008
Sonian Getting Started Guide October 2008 Sonian, Inc. For Authorized Use Only 1 Create your new archiving account 3 Configure your firewall for IMAP collections 4 (Skip this step if you will be using
Sentinel EMS v7.1 Web Services Guide
Sentinel EMS v7.1 Web Services Guide ii Sentinel EMS Web Services Guide Document Revision History Part Number 007-011157-001, Revision E. Software versions 7.1 and later. Revision Action/Change Date A
Configuration Notes 0215
Mediatrix Digital and Analog VoIP Gateways DNS SRV Configuration for a Redundant Server Solution (SIP) Introduction... 2 Deployment Scenario... 2 DNS SRV (RFC 2782)... 3 Microsoft Server Configuration...
Domain Registration/Domain Transfer/Domain Renewal Contract TERMS OF SERVICE
Domain Registration/Domain Transfer/Domain Renewal Contract TERMS OF SERVICE This contract is between Enter.Net, Inc., located at 815 N 12th Street, Allentown PA 18102, ("Enter.Net") and you, Enter.Net
MEFFGate Trading FIX INTERFACE SPECIFICATIONS
MEFFGate Trading FIX INTERFACE SPECIFICATIONS Version T1.2 30 July 2012 The information contained in this document is subject to modification without notice. Unless otherwise noted, the companies, names
AUSTRALIAN COMMUNICATIONS AUTHORITY CALL FOR EXPRESSIONS OF INTEREST FOR A TIER 1 REGISTRY OPERATOR FOR THE AUSTRALIAN TRIAL OF ENUM
AUSTRALIAN COMMUNICATIONS AUTHORITY CALL FOR EXPRESSIONS OF INTEREST FOR A TIER 1 REGISTRY OPERATOR FOR THE AUSTRALIAN TRIAL OF ENUM REFERENCE: 04/ACA017 Organisations are invited to express their interest
SIP: Ringing Timer Support for INVITE Client Transaction
SIP: Ringing Timer Support for INVITE Client Transaction Poojan Tanna ([email protected]) Motorola India Private Limited Outer Ring Road, Bangalore, India 560 037 Abstract-The time for which the Phone
Configuring DNS. Finding Feature Information
The Domain Name System (DNS) is a distributed database in which you can map hostnames to IP addresses through the DNS protocol from a DNS server. Each unique IP address can have an associated hostname.
Configuration of the DHCP server
104 Page 91 of 294 Contents This section contains information on the following topics: Overview................................................ 91 i2004 Internet Telephone....................................
.tirol Anti-Abuse Policy
Translation from German.tirol Anti-Abuse Policy This policy is based on Austrian legislation. In case of doubt the German version of this policy is in force. Page 1 Contents 1. Management Summary... 3
DNS Resolving using nslookup
DNS Resolving using nslookup Oliver Hohlfeld & Andre Schröder January 8, 2007 Abstract This report belongs to a talk given at the networking course (Institue Eurecom, France) in January 2007. It is based
DNS Conformance Test Specification For Client
DNS Conformance Test Specification For Client Revision 1.0 Yokogawa Electric Corporation References This test specification focus on following DNS related RFCs. RFC 1034 DOMAIN NAMES - CONCEPTS AND FACILITIES
SIP Trunking using the EdgeMarc Network Services Gateway and the Mitel 3300 ICP IP-PBX
June 26th, 2014 SIP Trunking using the EdgeMarc Network Services Gateway and the Mitel 3300 ICP IP-PBX Page 1 of 30 Table of Contents 1 Overview... 3 2 Prerequisites... 3 3 Network Topology... 4 4 Description
Architecture and Data Flow Overview. BlackBerry Enterprise Service 10 721-08877-123 Version: 10.2. Quick Reference
Architecture and Data Flow Overview BlackBerry Enterprise Service 10 721-08877-123 Version: Quick Reference Published: 2013-11-28 SWD-20131128130321045 Contents Key components of BlackBerry Enterprise
DNS. Some advanced topics. Karst Koymans. (with Niels Sijm) Informatics Institute University of Amsterdam. (version 2.6, 2013/09/19 10:55:30)
DNS Some advanced topics Karst Koymans (with Niels Sijm) Informatics Institute University of Amsterdam (version 2.6, 2013/09/19 10:55:30) Friday, September 13, 2013 Karst Koymans (with Niels Sijm) (UvA)
Transferring Your Internet Services
Page 1 of 6 Transferring Your Internet Services Below you will find the instructions necessary to move your web hosting, email, and DNS services to NuVox. The Basics Transferring your domain name Preparing
.ke Domain Name WHOIS Policy .ke Domain Name WHOIS Policy
.ke Domain Name WHOIS Policy 1/6 DEFINITIONS Terms defined in the Terms & Conditions and/or the.ke Dispute Resolution Rules are used herein with a capital letter. SECTION 1. PRIVACY POLICY 1.1. Processing
Configuring Security Features of Session Recording
Configuring Security Features of Session Recording Summary This article provides information about the security features of Citrix Session Recording and outlines the process of configuring Session Recording
VoIP Server Reference
IceWarp Server VoIP Server Reference Version 10 Printed on 12 August, 2009 i Contents VoIP Service 1 Introduction... 1 V10 New Features... 3 SIP REFER... 3 SIP Call Transfer Agent Settings... 3 NAT traversal
Service Level Agreement for Windows Azure operated by 21Vianet
Service Level Agreement for Windows Azure operated by 21Vianet Last updated: November 2015 1. Introduction This Service Level Agreement for Windows Azure (this SLA ) is made by 21Vianet in connection with,
IX Web Hosting. Billing Manual. July 31, 2012
IX Web Hosting Billing Manual July 31, 2012 Table of Contents 1 Introduction... 3 2 Billing Profile... 3 3 Domain Points... 4 4 Accessing the Billing and Administration System... 5 4.1 The My Products
DOMAIN AND EMAIL GLOSSARY The phrases and terms you may encounter, when registering a domain name
DOMAIN AND EMAIL GLOSSARY The phrases and terms you may encounter, when registering a domain name Don t know your Registrar from your Registry? No idea what a Name server actually does? Well, don t worry.
Dashboard Admin Guide
MadCap Software Dashboard Admin Guide Pulse Copyright 2014 MadCap Software. All rights reserved. Information in this document is subject to change without notice. The software described in this document
Configuring Health Monitoring
CHAPTER4 Note The information in this chapter applies to both the ACE module and the ACE appliance unless otherwise noted. The features that are described in this chapter apply to both IPv6 and IPv4 unless
FTP Service Reference
IceWarp Unified Communications Reference Version 11.3 Published on 1/6/2015 Contents... 3 About... 4 Reference... 5 General Tab... 5 Dialog... 6 FTP Site... 6 Users... 7 Groups... 11 Options... 14 Access...
Managing Software and Configurations
55 CHAPTER This chapter describes how to manage the ASASM software and configurations and includes the following sections: Saving the Running Configuration to a TFTP Server, page 55-1 Managing Files, page
Getting Started With Parallels Business Automation 4.4
Parallels Getting Started With Parallels Business Automation 4.4 Reseller's Guide Revision 1.0.18 (c) 1999-2008 ISBN: N/A Parallels 660 SW 39th Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425)