Personal tools

From HEXONET Wiki

Revision as of 11:30, 13 August 2012 by 188.107.121.138 (Talk)

Jump to: navigation, search
.AF is the official country code Top-Level-Domain of Afghanistan.




TLD

.af

Registry

CoCCA

Dispute Policy

Rules

Registrar

1api GmbH

WHOIS-Server

whois.nic.af

WHOIS-Update

Real-Time

Min. Characters

3

Max. Characters

63

Character Set
  • Letters and numbers
  • Hyphens ("-"), however not at the beginning or directly in front of the TLD
  • IDN: not allowed
Limitations
  • Registrant Contacts: Required: 1 / Maximum: 1
  • Admin Contacts: Required: 0 / Maximum: 1
  • Tech Contacts: Required: 0 / Maximum: 1
  • Billing Contacts: Required: 0 / Maximum: 1

{{{Possible Extensions}}}

IDN capable

No

Restore capable

Real-Time

Handle Updates

Supported

Registration System

Real-Time

Allowed number of NS

2 to 10

Registry Nameservercheck

No

Host IP-Addresses Type

IPv4 / IPv6

Hosts managed as

Object

Root Nameserver Update

hourly

SEC DNS Interface

DS data interface

Transferclass

Pull

Transfer Periods

0Y

Transfer Authcode required

No

Transfer Real-Time

No

Transfer ACK by

Registrar

Transfer NACK by

Registrar

Transfer Lock

Yes

Owner Change by

Update


Domain Registration

Domains can be registered in Real-Time with the API AddDomain command.

command = AddDomain
domain  = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)

OPTIONAL

auth = <TEXT> | <NULL>
transferlock = 0 | 1 | <NULL>
subuser = <TEXT> | <NULL>

Domain Transfer

The transfer has to be initiated by the gaining registrar and can be requested with the API TransferDomain command.
As soon as a domain transfer has been initiated it can either be approved ("ACK") by Registrar or denied ("NACK") by Registrar.

command = TransferDomain
domain = (DOMAIN)

REQUIRED

auth = <TEXT> | <NULL>
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
auth = <TEXT>

OPTIONAL

order = CREATE | REPLACE | UPDATE

nameserver# = <TEXT> | <NULL>
subuser = <TEXT> | <NULL>
ownercontact0 = <CONTACT> | <NULL>
admincontact0 = <CONTACT> | <NULL>
techcontact0 = <CONTACT> | <NULL>
billingcontact0 = <CONTACT> | <NULL>
transferlock = 0 | 1 | <NULL>

Delete Domain

Domains can be deleted with the API DeleteDomain command.
There is a Deletion Restorable Period of 5 days and a following Deletion Hold Period of 14 days.

command = DeleteDomain
domain = (DOMAIN)

REQUIRED

n/a

OPTIONAL

n/a

Restore Domain

Restores can be processed in realtime. A restore is possible within 5 days upon deletion. Please use the command RestoreDomain.

command = RestoreDomain
domain = (DOMAIN)

REQUIRED

n/a

OPTIONAL

renewalmode = <NULL> | <TEXT>
subuser = <TEXT>

Ownerchange

An Ownerchange is free of charge and can be done with the API ModifyDomain command.

Authorization code

There are special requirements regarding the format of the authorization code. Please consider the following restrictions, if you want to assign a new authorization code to a .COM domain:

  • Minimum 8 characters
  • having at least one (1) numeric,
  • one (1) alphabetic, and
  • one (1) special character


These syntax rules are legible as of November 14th, 2009. It is possible that updates for domains which still have an "old" AuthCode assigned, will fail with this error message:

505 AUTH - minimum 8 characters, containing at least one numeric, one alphabetic and one special character

You may generate a valid random auth code by adding this parameter to the ModifyDomain command:

GENERATERANDOMAUTH = 1

Example:

 command = ModifyDomain
 domain = domain.com
 generaterandomauth = 1

Restore Process

To restore a domain as a RegistrarOC customer, you simply have to execute the RestoreDomain command. HEXONET directly forwards the restore request to the registry, which performs the restore in real-time. As soon as the restore is complete, the domain will get assigned to your account with the original domain data.

Please do not initiate a restore directly at the registry (e.g. using the registrar webinterface). All restore operations must be performed through our system.