From HEXONET Wiki
| Line 181: | Line 181: | ||
= TLD specific = | = TLD specific = | ||
=== Domain Limitations and Requirements === | === Domain Limitations and Requirements === | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
= RegistrarOC = | = RegistrarOC = | ||
Revision as of 13:14, 22 March 2017
 |
|
| Introduced | 2005 |
|---|---|
| TLD Type | Generic |
| Category | Media |
| Registry | Telnic Ltd |
| IDN Capable | Yes |
| Webpage | Register .TEL |
Contents |
Registry
| TLD |
- |
| Registry |
- |
| Dispute Policy |
- |
| Limitations |
|
| Allowed number of NS |
to |
Periods
.TEL Updates on March 13th, 2017
Summary
As of March 13, 2017, previous DNS restrictions are lifted by the registry, allowing .TEL registrants the freedom to choose how to use and host their .TEL domain names.
A newly upgraded Telhosting platform is a ready-made option among others for customers to showcase their .TEL domain names.
A New Telhosting Platform
.TEL registrants will be issued an email with account details for the new, optional Telhosting system. This platform may be accessed at https://www.managemy.tel. More information will also be available on the registry's website (www.telnic.org). New content on this and other platforms will now resolve in the DNS.
iOS and Android apps will be available that will enable .TEL domain name customers using Telhosting to manage their domain names using their smartphone. Downloads for these apps will be available from Telnic's website or from the Apple and Google Play stores around March 2017.
Key Dates and Actions to be Taken
As of March 13th, 2017, the old Telhosting system was permanently shut down and any data was PERMANENTLY DELETED. Registrants who backed up their data may use it as a reference for populating their new account or as a data source for populating an independent and separate third party hosting solution.
It is also important to note that Telnic will not run the old and new platform simultaneously and will not be offering sub domain functionality in the new platform. Should .TEL registrants wish to continue to host their domain on a similar version to the current Telhosting platform which incorporates sub domains, please ask them to contact the .TEL registry at [email protected] to discuss options available.
More Information
For more details and Frequently Asked Questions, please refer to the following document provided by the .TEL Registry, as well as the registry's website (www.telnic.org).
API
Domain Registration
Domains can be registered with the API AddDomain command.
command = AddDomain domain = (DOMAIN)
REQUIRED
ownercontact0 = (CONTACT) admincontact0 = (CONTACT) techcontact0 = (CONTACT) billingcontact0 = (CONTACT) nameserver0 = (NAMESERVER) nameserver1 = (NAMESERVER)
OPTIONAL
secdns-ds# = <LONGTEXT> | <NULL> secdns-key# = <LONGTEXT> | <NULL> secdns-maxsiglife = <INT> auth = <TEXT> | <NULL> host# = <TEXT> | <NULL> transferlock = 0 | 1 | <NULL> subuser = <TEXT> | <NULL> nameserverset = <TEXT> | <NULL>
Domain Transfer
There is a special procedure to handle a domain transfer. Please contact our Support-Team if you should need further information.
command = TransferDomain domain = (DOMAIN)
REQUIRED
auth = <TEXT> | <NULL>
OPTIONAL
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER emaillanguage = <TEXT> emailurl = <TEXT> emaillanguage = <TEXT> emailtac = <TEXT> requestentity = <TEXT> emailsender = <TEXT> | <NULL> emailsubject = <TEXT> | <NULL> subuser = <TEXT> | <NULL> period = <PERIOD> transferlock = 0 | 1 | <NULL>
Delete Domain
Domains can be deleted with the API DeleteDomain command.
There is no Deletion Restorable Period.
command = DeleteDomain domain = (DOMAIN)
OPTIONAL
domainalerttriggercode = <TEXT> | <NULL> repository = <TEXT> | <NULL>
Restore Domain
command = RestoreDomain domain = (DOMAIN)
OPTIONAL
renewalmode = <NULL> | <TEXT> subuser = <TEXT>
