Personal tools

From HEXONET Wiki

Jump to: navigation, search
(Created page with "{{#repositoryinfo: CENTRALNIC-LIVE-1API | la }} {{#var:ABOUTTLD}} {{Sidebar}} <br> = Registry = {{Summarybox | TLD={{#IfEmpty: {{#var:TLD}} | {{#var:TLD}} | - }} | Regis...")
 
 
(3 intermediate revisions by one user not shown)
Line 1: Line 1:
{{#repositoryinfo: CENTRALNIC-LIVE-1API | la }}  
+
{{Infobox ccTLD
{{#var:ABOUTTLD}}
+
| name = .LA
 +
| image    =[[File:La.png|150px]]
 +
| introduced = 1996
 +
| country = Laos
 +
| registry = CentralNIC
 +
| idn capable = Yes
 +
| webpage = [https://www.hexonet.net/domain-name/la Register .LA]
 +
}}
 +
{{#repositoryinfo: RRPPROXY-LIVE-1API | la }}  
 
{{Sidebar}}
 
{{Sidebar}}
 +
<div style="font-size: 250%;">'''.LA'''</div><br/>
 +
.LA is the official country code Top-Level-Domain (ccTLD) of Lao Peoples Democratic Republic. .LA - is marketed as the new city Top-Level-Domain for Los Angeles or as the State Code of Louisiana in the U.S.
  
 
+
__TOC__
<br>
+
 
+
  
 
= Registry =
 
= Registry =
Line 142: Line 150:
  
 
{{#var:CATEGORY}}
 
{{#var:CATEGORY}}
 
 
<headertabs/>
 

Latest revision as of 13:56, 12 February 2019

.LA

.LA is the official country code Top-Level-Domain (ccTLD) of Lao Peoples Democratic Republic. .LA - is marketed as the new city Top-Level-Domain for Los Angeles or as the State Code of Louisiana in the U.S.

La.png
Introduced 1996
Country Laos
Registry CentralNIC
IDN Capable Yes
Webpage Register .LA

Contents


[edit] Registry

TLD

-

Registry

CentralNic

Dispute Policy

Rules

Registrar

1api GmbH

WHOIS-Server

whois.centralnic.net

WHOIS-Update

Real-Time

Min. Characters

1

Max. Characters

63

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

{{{Possible Extensions}}}

IDN capable

Yes

Restore capable

Real-Time

Handle Updates

Supported

Registration System

Real-Time

Allowed number of NS

1 to 10

Registry Nameservercheck

No

Host IP-Addresses Type

IPv4 / IPv6

Hosts managed as

Object

Root Nameserver Update

every 15min

SEC DNS Interface

DS data interface

Transferclass

Pull

Transfer Periods

0Y

Transfer Authcode required

Yes

Transfer Real-Time

No

Transfer Pending Period

5 days

Transfer Expire Action

ACK

Transfer ACK by

Registrar

Transfer NACK by

Registrar

Transfer Lock

Yes

Owner Change by

Update


[edit] Periods

{{{Possible Extensions}}}

Registration Periods

1-10 years

Add Grace Period

0 days

Accounting Period

0 days

Finalization Period

42 days

Failure Period

42 days

Payment Period

-61 days

Deletion Restorable Period

30 days

Deletion Hold Period

5 days

Explicit Renewals

Yes

Renewal Periods

1-9 years


[edit] API

[edit] 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>

[edit] Domain Transfer

The transfer has to be initiated by the gaining registrar and can be requested with the API TransferDomain command.
A valid Authorization Code must be provided to initiate a transfer successfully. You may obtain the authorization code from the losing registrar.
As soon as a domain transfer has been initiated it can either be approved ("ACK") by Registrar or denied ("NACK") by Registrar. If the registry receives neither a denial ("NACK") nor an approval ("ACK") the transfer will be ACKed after 5 days.

command = TransferDomain
domain = (DOMAIN)

REQUIRED

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

OPTIONAL

order = CREATE | REPLACE | UPDATE

subuser = <TEXT> | <NULL>
period = <PERIOD>
transferlock = 0 | 1 | <NULL>

[edit] Delete Domain

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

command = DeleteDomain
domain = (DOMAIN)

REQUIRED

n/a


[edit] Restore Domain

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

command = RestoreDomain
domain = (DOMAIN)

REQUIRED

n/a

OPTIONAL

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


[edit] Ownerchange

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

[edit] TLD specific

[edit] IDN Registration

CentralNIC only allows IDN characters published in the lists you can find here: IDN Tables for .LA

[edit] Addons

The following overview shows you all available Domain Addons which can be used for this special kind of TLD. It also shows the respective API parameters which are required to activate the Domain Addons:

Addon Class Parameter to (de)activate *1) Renewal term *2) Affected Parameters *3)
Proxy (WHOISTRUSTEELITE_RRPPROXY) X-ACCEPT-WHOISTRUSTEELITE-TAC = 0 | 1 1 month All Contacts
Proxy (WHOISTRUSTEE_RRPPROXY) X-ACCEPT-WHOISTRUSTEE-TAC = 0 | 1 1 month All Contacts






*1) Parameter to (de)activate: When accessing our backend through the API, you can either activate the addon with X-ACCEPT-WHOISTRUSTEELITE-TAC=1 or deactivate it with
      X-ACCEPT-WHOISTRUSTEELITE-TAC=0
*2) Renewal Term: Is the minimum renewal term of the "Addon Class"
*3) If you are using a "Proxy" Domain Addon normally all contact handles are affected (registrant, admin, tech, and billing contact).
      
      



[edit] RegistrarOC

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.