24 Shared Registration System (SRS) Performance

Prototypical answer:

SRS is EPP based, self-developed and well-tested, we were using it for different purpose before and we had enough time to evaluate its function. Its transport layer includes request limiter in case of too high number of requests from some particular registrar. Only certified registrars are allowed to connect, they have to give us their allocated IP address to connect with, their certificate file and have to obtain unique username and password combination to use in EPP login request. Every registrar is also limited to use maximum of four TCP connections at the same time.

DNS availability is 99.9%, and considering our planned number of domains there will not be any problem with stability, all requests are served in less than 100ms. DNS update time is set to 10 minutes. DNSSEC proper resolution is provided by BIND software and configured to do full chain resolution.

EPP server, Whois servers, database servers, backup servers and even diagnostics servers are doubled, so there are two running servers of each type. Additionally, for each service there is one additional backup server, which can replace malfunctioning productive server in case of hardware failure or housing outage. Database tables are synchronized directly using MySQL replication, including the third backup server. There are also two backup servers that save both incremental and full copy of registry data every one hour.

Regarding IPv6, all of our servers and network infrastructure is assigned IPv4 and IPv6 addresses. Registrars can use both protocols for both EPP and Whois services, they will connect to the same interface on the same physical servers. Our DNS system also supports handling of both IPv4 and IPv6 addresses, both types can be specified in EPP host commands.

Maintenance is provided by a team of three technicians who are monitoring the servers, monitor possible performance problems and security issues. Ideally, software is fully automatic and requires no manual maintenance. However it is necessary to monitor its function and resolve possible failures. Development team of two programmers is prepared to fix urgent problems in terms of two working days.
As stated before, the system is prepared for rather less amount of second level domain names. It is expected that the number of registered domains will not exceed 50000, however the system should handle 300000 domain names with no problems. If there will ever be the need to have more, there is no problem in adding additional servers in a few days. System is fully scalable and adding of new hardware will cause no interruption of operation.

Whois servers are available on ports 43 and 80 for standard and web-based Whois.

The biggest concerns about performance lay in SQL database servers. We have two live synchronized MySQL servers, which EPP servers use to get⁄save data and Whois use for getting data. Backups are also made in regular intervals. However, the data structure is well chosen and our measures and tests show, that two servers will be enough even with tens of thousands of domains. In immediate need to get more performance, we could connect the third backup server and extend SRS of new machines as soon as possible.

Similar gTLD applications: (0)