Frequently Asked Questions - General Registrar FAQ
Answers to your general questions about being a .INFO registrar.
- What will I be able to do through the Registrar Administration Interface?
- What is the Registrar Administration Interface?
- How can I get access to Afilias' TLD zone file for .INFO domains?
- How often is .INFO WHOIS information updated?
- As a registrar, do I have to provide a WHOIS server for .INFO domains?
- How often are .INFO DNS zones updated?
- What are "thick" and "thin" registry models?
Among other tasks, the Registrar Admin Interface will allow a registrar to: view your current registrar account information, update your account information, edit a list of your contacts, and check the available balance in your account with Afilias for .INFO.
The Registrar Administration Interface is a Web-based tool that will allow a registrar to perform certain functions in the .INFO registry system. Access to the interface requires a username and password and a Web browser capable of supporting 128-bit SSL.
Afilias provides access to the .INFO TLD zone file per Appendix N of the Registry Agreement. Simply fill out the agreement form (PDF format) and fax it to Afilias.
The .INFO WHOIS is generally updated in near real time within approximately two (2) minutes of a change being received.
Yes. Afilias recommends that registrars point their WHOIS server to the Afilias port 43 WHOIS server at: whois.afilias.net
Updates to the zone information will be generated automatically every five minutes. These updates will reflect any modifications, additions, or deletions to the registry that have been made by the registrars during that time period. Only changes that have been committed to the database will be reflected in the zone information update.
The Afilias Registry is operated as a "thick" registry. A thick registry is one in which all of the information associated with registered entities, including both technical information (information needed to produce zone files) and social information (information needed to implement operational, business, or legal practices), is stored within a central registry repository. The registry-registrar protocol supported by Afilias is the Extensible Provisioning Protocol.
In contrast, registries that support a "thin" model only store the domain and name server information within the registry; contact information is stored at each registrar. As a result, each registrar must operate its own WHOIS server in order to provide access to this information.
