The Long Registration Form

This document describes the long registration form for domains in the top level Internet domains of TC, VG, and MS. This form is primarily designed for corporate customers who want to distribute the responsibilities for running a domain between different people. If you are an individual then you're most welcome to use this form, but might prefer a shorter form instead.

Please note

• Names may be registered in these zones by filling in the form then emailing it to new@adamsnames.com.
• You must include the terms and conditions when you submit the form, otherwise it will not be recognized.
• At present the registration robot does not understand MIME attachments: you should cut and paste the form into the body of your message, taking care not to disturb its format.

There are eight sections to the registration form, but completing the form should not be particularly difficult. However if you simply want to register a name for your own use, you might find our basic form more suitable.

Of the eight sections, four deal with the domain itself. Each of the remaining four sections is concerned with a person or organization who helps to manage the domain: the registrant of the domain, the contact who manages it, the contact who is responsible for technical matters, and the contact who pays for it. It is helpful to regard the domain and contacts as independent objects: many domains can share common contact details, or a single entity might be responsible for different roles in a domain. All of these objects are stored in the same rwhois database.

Object IDs

Every object in the database, be it a domain or a contact, has a unique ID. When your registration is processed you will be told which objects have been registered, and their corresponding IDs. To avoid confusion with other domain databases, notably the Internic whois database, each ID's suffix denotes the domain in which the object is registered.

Sometimes you may wish to refer to an existing object; this is simple: just quote the ID of that object. Perhaps more commonly you will want to refer to an object which is being registered. For example you might want to register a new Organization and then also use if for the three contact roles. You can't specify the organization's ID because it's not registered yet! To solve this problem there are several keywords which expand to the ID of the object once registered:

Protecting the data

Clearly it is important that only authorized people can make changes to the domain. To this end, each object in the database is protected by a password. By default, a new password is generated for each object registered, but objects can share passwords if this is more convenient. For example, you might want to use the same password to protect all of your domains.

Passwords are stored in objects called guardians, which ar stored in the rwhois database alongside the contacts and domains. If you want an object to share the guardian of an existing object, you should complete the relevant field in the form; example of this are shown below. Like other objects in the database, every guardian has an ID. You should always quote the ID of the guardian and not the password itself.

Section 1: Action

1.  Purpose/Description.............: New Registration

Section 2: Domains to register

This section should contain the complete names of all the domains that you wish to register (e.g. foo.tc). e.g. to register foo.tc:

Domain(s) to Register (repeat as required)
2a. Complete Domain Names...........: foo.tc

Section 3: Domain Information

This section should contain the records to be placed in the DNS for the domain. Often the top level domain delegates each subdomain to two or more nameservers. The example below shows a domain delegated to two servers, ns1.foo.net and ns2.foo.net:

Domain Information
3a. Nameserver name (repeat if required): ns1.foo.net.
3a. Nameserver name (repeat if required): ns2.foo.net.
3b. A records (repeat if required)......:
3c. MX records (repeat if required).....:
3d. TXT record (optional)...............:

Unlike other registries we do not restrict you to NS resource records; you can also add A, MX, and TXT records or any mixture of these. This might be particularly useful if you just wish to just reserve a name rather then setting up your own nameservers, it is enough to simply specify a text record e.g.:

Domain Information
3a. Nameserver name (repeat if required):
3b. Nameserver address (if in domain)...:
3c. A records (repeat if required)......:
3d. MX records (repeat if required).....:
3e. TXT record (optional)...............: Reserved by ACME Inc.

Another popular use of this is to point the domain at a webserver. e.g. to make www.foo.tc, and foo.tc both point at a webserver with IP address 123.234.45.56:

Domain Information
3a. Nameserver name (repeat if required):
3b. Nameserver address (if in domain)...:
3c. A records (repeat if required)......: 123.234.45.56
3c. A records (repeat if required)......: 123.234.45.56:www
3d. MX records (repeat if required).....:
3e. TXT record (optional)...............: 

• A records must be an internet address in dotted-quad format.
• MX records must contain the canonical name of the host, then a colon, and then the priority of the server e.g. joanna.william.org:10.
• Records for names inside the domain can be added; simply add the subname of the record after a colon.
• No more than six records for each domain is allowed.

The names provided for the nameservers should be the canonical name of the machine. It is not necessary to supply the IP address of the nameservers, but if they lie inside the delegated domain you will need to supply A records e.g.:

Domain(s) to Register (repeat as required)
2a. Complete Domain Names...........: foo.tc

Domain Information
3a. Nameserver name (repeat if required): ns1.foo.tc.
3a. Nameserver name (repeat if required): ns2.foo.tc.
3b. A records (repeat if required)......: 123.45.67.89:ns1
3b. A records (repeat if required)......: 123.45.76.89:ns2
3c. MX records (repeat if required).....:
3d. TXT record (optional)...............:

Section 4: Additional Information

This section is entirely optional. The first field allows extra information to be saved in the database which is not reflected in the DNS records. Typically this might be an URL to a related domain.

The second field allows the user to control the means by which the domain record is protected. As explained above, by default each object in the database is assigned an independent password, but if this record is supplied it will be assumed to point to an existing guardian object which will instead be used to protect the domain's details.

Sections 5-8: The contacts

Sections five to eight each define a contact. Each domain is associated with four contacts, though some of these roles might be the responsibility of the same people. You may either register new contacts, or refer to existing ones when registering a new domain. The four contacts have quite different roles:

• Organization: the organization or person who has registered the domain.
• Administrative Contact: the person who is charged with the routine administration of the zone. Usually this will be somebody in the organization above.
• Technical Contact: the person who is charged with the technical administration of the zone. Questions about resource records, nameservers, and the like will be sent here.
• Billing Contact: the person who is charged with paying for the zone. Invoices and overdue account queries will be sent here.

Despite their different roles, each contact is specified in the same way. In the first example below, we show how to register a new contact; in the second we assign extra responsibilities to an existing contact.

Registering a new contact

Organization Using Domain Name (complete EITHER 5a OR 5b - 5h).
5a. Existing ID.....................:
or
5b. Name............................: Mr Fred Flintstone
5c. Address (repeat as required)....: 1, The Cave
5c. Address (repeat as required)....: Bedrock
5c. Address (repeat as required)....: Arkansas
5c. Address (repeat as required)....: 12345
5d. Country Code (2 letter).........: US
5e. Phone number....................: (123) 456 7890
5f. Email address...................: fred@flintstone.tc
5g. Fax number (optional)...........: 
5h. See-Also (optional).............: http://www.flintstone.tc/
5i. Guardian ID (optional)..........:

Most of this should be fairly obvious. The major difference between our form and that of some other registeries is that we impose structure on neither the name, nor the address of the contact. Beyond this:

• The Country Code should be the two-digit ISO country code.
• Telephone and fax numbers should include the international dialling code. If no telephone number is available, please use the special value of 999999.
• If no email address is available, please use the special value `null'.

As with the domain record options are provided to record additional information, and to share the password protecting the contact with an existing record.

You are reminded that failure to supply accurate contact information can lead the the removal of your domain.

Referring to an existing contact

To refer to an existing contact, simply specify its ID. Object IDs are discussed above. As an example the form below uses the same contact for all the contacts:

Organization Using Domain Name (complete EITHER 5a OR 5b - 5h).
5a. Existing ID.....................:
or
5b. Name............................: Mr Fred Flintstone
5c. Address (repeat as required)....: 1, The Cave
5c. Address (repeat as required)....: Bedrock
5c. Address (repeat as required)....: Arkansas
5c. Address (repeat as required)....: 12345
5d. Country Code (2 letter).........: US
5e. Phone number....................: (123) 456 7890
5f. Email address...................: fred@flintstone.tc
5g. Fax number (optional)...........: 
5h. See-Also (optional).............: http://www.flintstone.tc/
5i. Guardian ID (optional)..........:

Administrative Contact (complete EITHER 6a OR 6b - 6h).
6a. Existing ID.....................: &org
...

Technical Contact (complete EITHER 7a OR 7b - 7h).
7a. Existing ID.....................: &org
...

Billing Contact (complete EITHER 8a OR 8b - 8h).
8a. Existing ID.....................: &org
...