Originally published at WebServer - Eos Net srl . Any Please leave comments there.
last few days will begin the first phase of the synchronous domains. Com.
As we previously indicated, this first phase will be a little laborious and boring because for 2 years domain registration. It decided that the synchronous and asynchronous system will have to live, creating, surely, some problemuccio for transfer and Maintainer Registrar, a bit of confusion in the minds of customers who will have to assess who buy a domain name extension. it rather than transfer it to decide where and if to transfer.
more than a month with Softgens Ltd we are working on any platform, and synchronous system.
We are working on the management console of a "brutal" xml, we have created is useful to work directly with the registry for testing and would later be used by the admin panel, admin side management domains and management of domains by the customer, and management LAR
We had to work hard on the party will use the customer because we had to integrate the platform with our ASP.net WHMCS management orders.
management features included in the LAR and DOMAINS:
the order after the customer has requested registration / transfer domains. it will, through the 'order completed "page to WHMCS and" lar synchronous ", go to the new platform written entirely in ASP.Net with MSSQL database, where you can perform the request registration / transfer / change data, change dns, change registrant.
ASP.Net platform communicates with WHMCS to control: domain deadlines, payment, order number existing in the legal domain, real email, login and password real
This dialogue between platforms, although very different, we were able interesting to create controls to limit attempts to create fake lar, transfers domains unpaid renewals for domains that are not paid, ETCC.
The big problem we had for the possible transfers from Maintainer to Registrar.
Problems:
-the customer may not know whether his is a REG or
MNT-MNT to the transfer procedure between REG and REG to REG-
is exceedingly different from the transfer process also happens to REG MNT without the consent of the royal REG.
Solutions:
When the customer enters on the platform through our useful links to verify order, domain and paid for, will see if the monitor is trasfeirmento MNT or REG
at this point will be redirected continuing At appropiata for the transfer with automatic procedure.
If the transfer order is paid (the platform communicates with WHMCS) may proceed with sending the data to transfer.
If it is a transfer between REG follow the simple way of inserting AUTHINFO and define the data that the system automatically retrieves from the whois.
If it is a transfer from MNT to REG, must complete the online filing of the registrant and admin fields and then display the data that should insert, unfortunately, one of six possible to send fax to the registry.
The customer thanks to the platform, you can see if domains are pending or registered / transferred. The platform
dialogue with WHMCS and the registry will monitor the situation of.
The customer can manage domains by a panel which is very simple, where you can:
change in self-dns-
simple change in the data range (address, phone, email)
-change independently, following payment data REGISTRANT (name, surname, company name, VAT number, tax identification number and nationality)
The panel is also very useful for customers retailers. it domains
ADMIN The platform is able to bring their database MSSQL with the synchronous system EPP registry. ADMIN
platform is structured to communicate with a EPP sottopiattaforma where all the xml, all the controls on the xml, all the code has been revised from scratch, including XML, in order to simplify the management of 100% and to be able to do so that there is no room for error without ever having to dip into a xml file by the Registrar.
In practice, since the customer will fill in a registration request, simply click to enter data into the database and send the forms to the registry without having edict nothing but the DNS (our decision to change the DNS)
Problems to simplify the management of domains without ever having to dip into the console "brutal" "xml and make manual changes in the admin panel:
- when you submit an amendment or domain registration, EPP you must send a request with the nameservers and their host in the case of nameserver.
We had to make it so that it automatically generates a unique xml fields with the correct nameservers in order to avoid having to create several xml
since the possibility of sending nameservers are manifold. 2 nameservers, 2 nameserver ip, 2 nameservers and one without la'ltro ip with ip, nameserver 3 ... etc ... etc .... At the end
We opted for a single XML file that exploded just the right number of strings, full, past the platform based on the nameserver included by us or by the customer.
- inclusion of various controls on the platform for social security numbers, VAT,
-phone notifications, and custom operations for counting credit-
changes DNS UPDATE DOMAIN
custom auto-calculation of the ID and password (auth info) controls in accordance with the EPP registry
Thought:
surely pass the test for the accreditation will not be easy but not difficult either. The biggest problem is the post-accreditation.
If the base was not created its own management platform, the new Registrar could be really difficult.
It 's true that the Registry, and others have made available to the gentle console to communicate with the EPP registry, but the real problems on management in production are moltplici:
- creation of LAR legally be stored for several years as the Register may request information inq ny time. Lar
these to be valid must demonstrate that the customer has agreed to certain clauses and online arrive at the registration had to follow certain validation steps.
- A change registrant. If the base there is a system that fails to address the customer to the right form, the Registrar will lose a lot of time explaining to the customer the steps
-adjusting exchange before and after a transfer. If there is a basic system customers may have to pay twice for trivial errors in a domain being transferred, since a simple modification of a letter in last name / company / VAT at the time of the new contact, the registry charges the operation again
The Registrar who did not train properly a custom platform and especially the courts, will operate many times but not in synchronous asynchronous almost since it will operate with cutting and pasting of data, controls the name servers etc ... ....
The Registrar does not check that the payments platform for a transfer from MNT to REG may be ahead of payments for domains that are not in fact been paid. At this point we have discussed a lot with the registry to see to change their policy and in line with that asynchronous or one between two REG, but do not seem to want to change the rule.
To date we do not know if we can win approval for the 28/09, with the loss of time to customize the xml.
We will also be ready with the exam but want to go into production with the platform customized automatic admin / client / epp / WHMCS fully functional and tested at 100%. Become a Registrar
without this platform would create significant problems for us and customers is asking too much time on manual intervention via the console epp "brutal" ")
0 comments:
Post a Comment