Domain names are being processed pretty fast these days, send us e-mail if your domain isn't activated within two days. We'll take care of the problem.
If you want your own domain name, fill out the form below and send it to hostmaster@internic.net or we will automatically do it for you. Please record the NIC tracking number that they give you. If you don't receive a tracking number, RESUBMIT your application. (You should get a tracking number within 6 hours of submitting your application.)
To see if a domain has been taken, use the check domain feature at http://www.x5.net/html/whois.html
You don't have to use us as the billing contact, just let us know if you don't.
Form:
******************* Please DO NOT REMOVE Version Number ********************
Domain Version Number: 3.5
********** Please see attached detailed instructions ***************
NETWORK SOLUTIONS, INC.
DOMAIN NAME REGISTRATION AGREEMENT
A.Introduction. This domain name registration agreement
("Registration Agreement") is submitted to NETWORK SOLUTIONS, INC.
("NSI") for the purpose of applying for and registering a domain name
on the Internet. If this Registration Agreement is accepted by NSI,
and a domain name is registered in NSI's domain name database and
assigned to the Registrant, Registrant ("Registrant") agrees to be
bound by the terms of this Registration Agreement and the terms of
NSI's Domain Name Dispute Policy ("Dispute Policy") which is
incorporated herein by reference and made a part of this Registration
Agreement. This Registration Agreement shall be accepted at the
offices of NSI.
B.Fees and Payments. Registrant agrees to pay a registration fee
of One Hundred United States Dollars (US$100) as consideration for the
registration of each new domain name or Fifty United States Dollars
(US$50) to renew an existing registration. The payment may be made
payable either directly to "Network Solutions, Inc.", or indirectly to
NSI through the Registrant's Internet Service Provider ("ISP").
Payment is due within thirty (30) days from the date of the invoice.
The non-refundable fee covers a period of two (2) years for each new
registration, and one (1) year for each renewal, and includes any
permitted modification(s) to the domain name's record during the
covered period.
C.Dispute Policy. Registrant agrees, as a condition to
submitting this Registration Agreement, and if the Registration
Agreement is accepted by NSI, that the Registrant shall be bound by
NSI's current Dispute Policy. The current version of the Dispute
Policy may be found at the InterNIC Registration Services web site:
"http://rs.internic.net/dispute.html".
D.Dispute Policy Changes or Modifications. Registrant agrees
that NSI, in its sole discretion, may change or modify the Dispute
Policy, incorporated by reference herein, at any time. Registrant
agrees that Registrant's maintaining the registration of a domain name
after changes or modifications to the Dispute Policy become effective
constitutes Registrant's continued acceptance of these changes or
modifications. Registrant agrees that if Registrant considers any such
changes or modifications to be unacceptable, Registrant may request
that the domain name be deleted from the domain name database.
E.Disputes. Registrant agrees that, if the registration of its
domain name is challenged by any third party, the Registrant will be
subject to the provisions specified in the Dispute Policy.
F.Agents. Registrant agrees that if this Registration Agreement
is completed by an agent for the Registrant, such as an ISP or
Administrative Contact/Agent, the Registrant is nonetheless bound as a
principal by all terms and conditions herein, including the Dispute
Policy.
G.Limitation of Liability. Registrant agrees that NSI shall have
no liability to the Registrant for any loss Registrant may incur in
connection with NSI's processing of this Registration Agreement, in
connection with NSI's processing of any authorized modification to the
domain name's record during the covered period, as a result of the
Registrant's ISP's failure to pay either the initial registration fee
or renewal fee, or as a result of the application of the provisions of
the Dispute Policy. Registrant agrees that in no event shall the
maximum liability of NSI under this Agreement for any matter exceed
Five Hundred United States Dollars (US$500).
H.Indemnity. Registrant agrees, in the event the Registration
Agreement is accepted by NSI and a subsequent dispute arises with any
third party, to indemnify and hold NSI harmless pursuant to the terms
and conditions contained in the Dispute Policy.
I.Breach. Registrant agrees that failure to abide by any
provision of this Registration Agreement or the Dispute Policy may be
considered by NSI to be a material breach and that NSI may provide a
written notice, describing the breach, to the Registrant. If, within
thirty (30) days of the date of mailing such notice, the Registrant
fails to provide evidence, which is reasonably satisfactory to NSI,
that it has not breached its obligations, then NSI may delete
Registrant's registration of the domain name. Any such breach by a
Registrant shall not be deemed to be excused simply because NSI did
not act earlier in response to that, or any other, breach by the
Registrant.
J.No Guaranty. Registrant agrees that, by registration of a
domain name, such registration does not confer immunity from objection
to either the registration or use of the domain name.
K.Warranty. Registrant warrants by submitting this Registration
Agreement that, to the best of Registrant's knowledge and belief, the
information submitted herein is true and correct, and that any future
changes to this information will be provided to NSI in a timely manner
according to the domain name modification procedures in place at that
time. Breach of this warranty will constitute a material breach.
L.Revocation. Registrant agrees that NSI may delete a
Registrant's domain name if this Registration Agreement, or subsequent
modification(s) thereto, contains false or misleading information, or
conceals or omits any information NSI would likely consider material
to its decision to approve this Registration Agreement.
M.Right of Refusal. NSI, in its sole discretion, reserves the
right to refuse to approve the Registration Agreement for any
Registrant. Registrant agrees that the submission of this Registration
Agreement does not obligate NSI to accept this Registration Agreement.
Registrant agrees that NSI shall not be liable for loss or damages
that may result from NSI's refusal to accept this Registration
Agreement.
N.Severability. Registrant agrees that the terms of this
Registration Agreement are severable. If any term or provision is
declared invalid, it shall not affect the remaining terms or
provisions which shall continue to be binding.
O.Entirety. Registrant agrees that this Registration Agreement
and the Dispute Policy is the complete and exclusive agreement between
Registrant and NSI regarding the registration of Registrant's domain
name. This Registration Agreement and the Dispute Policy supersede all
prior agreements and understandings, whether established by custom,
practice, policy, or precedent.
P.Governing Law. Registrant agrees that this Registration
Agreement shall be governed in all respects by and construed in
accordance with the laws of the Commonwealth of Virginia, United
States of America. By submitting this Registration Agreement,
Registrant consents to the exclusive jurisdiction and venue of the
United States District Court for the Eastern District of Virginia,
Alexandria Division. If there is no jurisdiction in the United States
District Court for the Eastern District of Virginia, Alexandria
Division, then jurisdiction shall be in the Circuit Court of Fairfax
County, Fairfax, Virginia.
Q.This is Domain Name Registration Agreement Version
Number 3.5. This Registration Agreement is only for registrations
under top-level domains: COM, ORG, NET, EDU, and GOV. By completing
and submitting this Registration Agreement for consideration and
acceptance by NSI, the Registrant agrees that he/she has read and
agrees to be bound by A through P above.
Authorization
0a. (N)ew (M)odify (D)elete.........: N
0b. Auth Scheme.....................:
0c. Auth Info.......................:
1. Purpose/Description.............: Commercial Service (if .com)
Internet Access Provider (if .net)
Non Profit Organization (if .org)
2. Complete Domain Name.............: taco.com (Example!)
Organization Using Domain Name
3a. Organization Name (Registrant)..:
3b. Street Address..................:
3c. City............................:
3d. State...........................:
3e. Postal Code.....................:
3f. Country Code (2 letter).........: us (or ae if you are in United Arab Emirates, etc.)
Administrative Contact/Agent
4a. NIC Handle (if known)...........:
4b. (I)ndividual or (R)ole?.........: I
4c. Name............................:
4d. Organization Name...............:
4e. Street Address..................:
4f. City............................:
4g. State...........................:
4h. Postal Code.....................:
4i. Country Code (2 letter).........:
4j. Phone Number....................:
4k. Fax Number......................:
4l. Email Address...................:
Technical Contact
5a. NIC Handle (if known)...........: XD6-ORG
5b. (I)ndividual or (R)ole?.........:
5c. Name............................:
5d. Organization Name...............:
5e. Street Address..................:
5f. City............................:
5g. State...........................:
5h. Postal Code.....................:
5i. Country Code (2 letter).........:
5j. Phone Number....................:
5k. Fax Number......................:
5l. Email Address...................:
Billing Contact
6a. NIC Handle (if known)...........:
6b. (I)ndividual or (R)ole?.........: I
6c. Name............................:
6d. Organization Name...............:
6e. Street Address..................:
6f. City............................:
6g. State...........................:
6h. Postal Code.....................:
6i. Country Code (2 letter).........:
6j. Phone Number....................:
6k. Fax Number......................:
6l. Email Address...................:
Primary Name Server
7a. Primary Server Hostname.........: tesla.x5.net
7b. Primary Server Netaddress.......: 207.213.164.26
Secondary Name Server(s)
8a. Secondary Server Hostname.......: blues.x5.net
8b. Secondary Server Netaddress.....: 207.33.41.130
END OF AGREEMENT
Don't know your country code? Here is is:
Country Code
----------------------------------------------------
AFGHANISTAN AF
ALBANIA AL
ALGERIA DZ
AMERICAN SAMOA AS
ANDORRA AD
ANGOLA AO
ANGUILLA AI
ANTARCTICA AQ
ANTIGUA AND BARBUDA AG
ARGENTINA AR
ARMENIA AM
ARUBA AW
AUSTRALIA AU
AUSTRIA AT
AZERBAIJAN AZ
BAHAMAS BS
BAHRAIN BH
BANGLADESH BD
BARBADOS BB
BELARUS BY
BELGIUM BE
BELIZE BZ
BENIN BJ
BERMUDA BM
BHUTAN BT
BOLIVIA BO
BOSNIA AND HERZEGOWINA BA
BOTSWANA BW
BOUVET ISLAND BV
BRAZIL BR
BRITISH INDIAN OCEAN TERRITORY IO
BRUNEI DARUSSALAM BN
BULGARIA BG
BURKINA FASO BF
BURUNDI BI
CAMBODIA KH
CAMEROON CM
CANADA CA
CAPE VERDE CV
CAYMAN ISLANDS KY
CENTRAL AFRICAN REPUBLIC CF
CHAD TD
CHILE CL
CHINA CN
CHRISTMAS ISLAND CX
COCOS (KEELING) ISLANDS CC
COLOMBIA CO
COMOROS KM
CONGO CG
COOK ISLANDS CK
COSTA RICA CR
COTE D'IVOIRE CI
CROATIA (local name: Hrvatska) HR
CUBA CU
CYPRUS CY
CZECH REPUBLIC CZ
DENMARK DK
DJIBOUTI DJ
DOMINICA DM
DOMINICAN REPUBLIC DO
EAST TIMOR TP
ECUADOR EC
EGYPT EG
EL SALVADOR SV
EQUATORIAL GUINEA GQ
ERITREA ER
ESTONIA EE
ETHIOPIA ET
FALKLAND ISLANDS (MALVINAS) FK
FAROE ISLANDS FO
FIJI FJ
FINLAND FI
FRANCE FR
FRANCE, METROPOLITAN FX
FRENCH GUIANA GF
FRENCH POLYNESIA PF
FRENCH SOUTHERN TERRITORIES TF
GABON GA
GAMBIA GM
GEORGIA GE
GERMANY DE
GHANA GH
GIBRALTAR GI
GREECE GR
GREENLAND GL
GRENADA GD
GUADELOUPE GP
GUAM GU
GUATEMALA GT
GUINEA GN
GUINEA-BISSAU GW
GUYANA GY
HAITI HT
HEARD AND MC DONALD ISLANDS HM
HONDURAS HN
HONG KONG HK
HUNGARY HU
ICELAND IS
INDIA IN
INDONESIA ID
IRAN (ISLAMIC REPUBLIC OF) IR
IRAQ IQ
IRELAND IE
ISRAEL IL
ITALY IT
JAMAICA JM
JAPAN JP
JORDAN JO
KAZAKHSTAN KZ
KENYA KE
KIRIBATI KI
KOREA, DEMOCRATIC PEOPLE'S REPUBLIC OF KP
KOREA, REPUBLIC OF KR
KUWAIT KW
KYRGYZSTAN KG
LAO PEOPLE'S DEMOCRATIC REPUBLIC LA
LATVIA LV
LEBANON LB
LESOTHO LS
LIBERIA LR
LIBYAN ARAB JAMAHIRIYA LY
LIECHTENSTEIN LI
LITHUANIA LT
LUXEMBOURG LU
MACAU MO
MACEDONIA, THE FORMER YUGOSLAV REPUBLIC OF MK
MADAGASCAR MG
MALAWI MW
MALAYSIA MY
MALDIVES MV
MALI ML
MALTA MT
MARSHALL ISLANDS MH
MARTINIQUE MQ
MAURITANIA MR
MAURITIUS MU
MAYOTTE YT
MEXICO MX
MICRONESIA, FEDERATED STATES OF FM
MOLDOVA, REPUBLIC OF MD
MONACO MC
MONGOLIA MN
MONTSERRAT MS
MOROCCO MA
MOZAMBIQUE MZ
MYANMAR MM
NAMIBIA NA
NAURU NR
NEPAL NP
NETHERLANDS NL
NETHERLANDS ANTILLES AN
NEW CALEDONIA NC
NEW ZEALAND NZ
NICARAGUA NI
NIGER NE
NIGERIA NG
NIUE NU
NORFOLK ISLAND NF
NORTHERN MARIANA ISLANDS MP
NORWAY NO
OMAN OM
PAKISTAN PK
PALAU PW
PANAMA PA
PAPUA NEW GUINEA PG
PARAGUAY PY
PERU PE
PHILIPPINES PH
PITCAIRN PN
POLAND PL
PORTUGAL PT
PUERTO RICO PR
QATAR QA
REUNION RE
ROMANIA RO
RUSSIAN FEDERATION RU
RWANDA RW
SAINT KITTS AND NEVIS KN
SAINT LUCIA LC
SAINT VINCENT AND THE GRENADINES VC
SAMOA WS
SAN MARINO SM
SAO TOME AND PRINCIPE ST
SAUDI ARABIA SA
SENEGAL SN
SEYCHELLES SC
SIERRA LEONE SL
SINGAPORE SG
SLOVAKIA (Slovak Republic) SK
SLOVENIA SI
SOLOMON ISLANDS SB
SOMALIA SO
SOUTH AFRICA ZA
SOUTH GEORGIA AND THE SOUTH SANDWICH ISLANDS GS
SPAIN ES
SRI LANKA LK
ST. HELENA SH
ST. PIERRE AND MIQUELON PM
SUDAN SD
SURINAME SR
SVALBARD AND JAN MAYEN ISLANDS SJ
SWAZILAND SZ
SWEDEN SE
SWITZERLAND CH
SYRIAN ARAB REPUBLIC SY
TAIWAN, PROVINCE OF CHINA TW
TAJIKISTAN TJ
TANZANIA, UNITED REPUBLIC OF TZ
THAILAND TH
TOGO TG
TOKELAU TK
TONGA TO
TRINIDAD AND TOBAGO TT
TUNISIA TN
TURKEY TR
TURKMENISTAN TM
TURKS AND CAICOS ISLANDS TC
TUVALU TV
UGANDA UG
UKRAINE UA
UNITED ARAB EMIRATES AE
UNITED KINGDOM GB
UNITED STATES US
UNITED STATES MINOR OUTLYING ISLANDS UM
URUGUAY UY
UZBEKISTAN UZ
VANUATU VU
VATICAN CITY STATE (HOLY SEE) VA
VENEZUELA VE
VIET NAM VN
VIRGIN ISLANDS (BRITISH) VG
VIRGIN ISLANDS (U.S.) VI
WALLIS AND FUTUNA ISLANDS WF
WESTERN SAHARA EH
YEMEN YE
YUGOSLAVIA YU
ZAIRE ZR
ZAMBIA ZM
ZIMBABWE ZW
---------------------------------------------------
Still confused? Here are the Internic instructions:
GENERAL INSTRUCTIONS
Changes from version 2.0 of the Domain Template are:
- Security information has been added in Section 0 for use with MODIFY
and DELETE submissions. For detailed information on Guardian, see:
ftp://rs.internic.net/policy/internic/internic-gen-1.txt
- No changes can be made to Contact or Host records while using the
MODIFY option on the Domain Template. For this purpose, Contact and
Host Templates are available at:
ftp://rs.internic.net/templates/contact-template.txt
ftp://rs.internic.net/templates/host-template.txt
- The ability to register role Contacts in addition to individual
Contacts has been added to Sections 4, 5, and 6.
- A separate field for a fax number has been added.
- A separate set of instructions has been added to facilitate the
transfer of a Domain name from one organization to another.
Use the above Domain Template for registering new Domain names, for making
changes to existing Domain name records, and for removing a Domain name
from the InterNIC database and Root Servers. The template, and only the
template, should be sent via email to HOSTMASTER@INTERNIC.NET. Please do
not send hardcopy registrations to the InterNIC. Your Internet Service
Provider (ISP) will be able to send email applications on your behalf if
you are not connected. In the Subject of the message, use the words
"NEW DOMAIN", "MODIFY DOMAIN", "DELETE DOMAIN", or "TRANSFER DOMAIN"
appropriately, followed by the Domain name to help sort and locate
incoming registration requests. In response to the submission of a
template, you should receive an auto-reply with a tracking number. Use
the tracking number in the Subject of any subsequent message you send
regarding that registration action. When the registration is completed
you will receive a notification via email.
Please DO NOT modify the template or remove the version number. The software
that processes the template looks for an item number, followed by a period,
followed by a colon. Information following the colon is compared with and
inserted into the database. Please send only one template per message.
When completing the template, make use of WHOIS at RS.INTERNIC.NET to
check to see if the Domain name, organization name, Contacts, and Name
Servers have been registered. Use that information where appropriate.
The instructions for completing each field are in the following four
Sections - one each for NEW, MODIFY, DELETE, and TRANSFER. Please read
the instructions carefully and make sure the template is properly completed
to accomplish the action you desire.
REGISTERING A NEW DOMAIN NAME
Section 0 - Authorization
In item 0a, enter the character N or the word NEW to indicate a NEW
Domain registration.
Items 0b and 0c are only REQUIRED for MODIFY and DELETE. These items
will be ignored for NEW.
Section 1 - Purpose of Registration
Briefly describe the organization and/or the purpose for which this
Domain name is being registered. The description should support the
choice of top-level Domain in Section 2. If the Domain name is for
an organization that already has a Domain name registered, describe
the purpose of this Domain and why the additional name is needed.
Indicate why existing names can not be used or why the proposed
second-level name can not be used as a third-level name under a
Domain name that is already registered.
Section 2 - Complete Domain Name
Top-level country Domains may be registered by inserting the two-letter
country code in this Section. For a list of country codes, see:
ftp://rs.internic.net/netinfo/iso3166-countrycodes
See RFC 1591 for a description of the duties and responsibilities of
top-level Domain administrators.
For second-level Domain names under COM, ORG, NET, EDU, or GOV, insert
the two-part name of the Domain you wish to register. For example,
EXAMPLE.COM. The total length of the two-part name may be up to 26
characters. The only characters allowed in a Domain name are alphabets,
digits and "-". A Domain name CAN NOT begin or end with a "-" (see
RFC 952). Consult RFC 1591 to determine the most appropriate top-level
Domain to join. Briefly:
- COM is for commercial, for-profit organizations
- ORG is for miscellaneous, usually, non-profit organizations
- NET is for network infrastructure machines and organizations
- EDU is for 4-year, degree granting institutions
- GOV is for United States federal government agencies
US state and local government agencies, schools, libraries, museums,
and individuals should register under the US Domain. See RFC 1480 for
a complete description of the US Domain and registration procedures.
GOV registrations are limited to top-level US Federal Government
agencies (see RFC 1816).
Section 3 - Organization using the Domain Name
The Domain name is considered to be registered to an organization,
even if the organization is an individual. It is important in this
Section to list the name and address of the end-user organization,
not the provider organization.
If the organization has the same name as one that is already
registered, explain this in Section 1 above.
Item 3b may be copied as necessary to reflect different lines of the
street address. If item 3c, 3d, or 3e does not apply for your country,
leave that item blank.
Item 3f MUST be the ISO two-letter country code. A list of ISO
two-letter country codes is available at:
ftp://rs.internic.net/netinfo/iso3166-countrycodes
Section 4, 5, 6 - Contacts
The Administrative Contact is the person who can speak on behalf of
the organization listed in Section 3. This person should be able to
answer non-technical questions about the organization's plans for
using the name and procedures for establishing sub-domains. See
RFC 1032 for more detail on Administrative Contacts.
The Technical Contact is the person who maintains the Domain's Primary
Name Server, resolver software, and database files. This person keeps
the Name Server running and interacts with technical people in other
Domains to solve problems that affect the Domain. The Internet Service
Provider (ISP) often performs this role.
The Billing Contact will be sent invoices for Domain registrations
and re-registrations. It is the Billing Contact's responsibility
to assure timely payment.
If the Technical or Billing Contact is missing from the template,
the Administrative Contact will be listed as filling those roles.
Each Contact in the InterNIC database is assigned a handle - a unique
identifier to differentiate it from all other records in the database.
Only one handle should exist for each individual or role.
If the handle is known, insert it in item "a" and leave the rest of
the Section blank. If the handle is given and additional information
is also provided, only the handle will be used. Any additional
information will be ignored. Use handles whenever possible.
If the Contact handle is unknown or has never been registered, leave
item "a" blank. The registration software will check for matches with
existing Contact records. If a Contact record is found in the database
that matches the information on the template in a significant way (name,
and emailbox or phone), the database information will be assumed.
Otherwise, the Contact will be registered. A Contact record CAN NOT be
updated while using the Domain Template. To update Contact information,
use the Contact Template available at:
ftp://rs.internic.net/templates/contact-template.txt
In item "b", indicate the type of Contact you are registering. If the
Contact is an individual, enter I or INDIVIDUAL. If it is a group or
organization where several individuals may be acting in that role,
enter R or ROLE.
In item "c", enter the name of the individual or role being registered.
If the Contact is an individual, the name should be entered as:
LASTNAME, FIRSTNAME MIDDLENAME
For example:
Smith, John X.
If the Contact is a role account, list the name of the role account in
item "c" and the name of the organization the role account represents in
item "d". Item "c" is REQUIRED for all Contacts. If the name of the
role account is the same as that of the organization, fill in item "c"
with that name and leave item "d" blank.
At least one line of address information is REQUIRED in item "e". This
address should be the postal mailing address for any correspondence
directed to the Contact. Enter the city and the standard two-letter
state abbreviation in items "f" and "g" respectively if the Contact
is located in the United States.
You may add as many lines as necessary for your street address. You may
do so by repeating item "e".
For the U.S. addresses, the postal code is REQUIRED in item "h".
Enter the ISO two-letter country code in Item "i". If no country code
is entered, the Contact is assumed to be located in the United States.
A list of ISO two-letter country codes is available at:
ftp://rs.internic.net/netinfo/iso3166-countrycodes
Every Contact is REQUIRED to provide at least one valid phone number in
item "j". For informational purposes, you may supply a fax number in
item "k".
A valid Internet email address is REQUIRED for all Contacts in item "l".
Separate the username and hostname parts of the mailbox by an "@" symbol.
For example:
user@example.com
Section 7, 8 - Name Servers
At least two independent Servers MUST be provided for translating names
to addresses for Hosts in the Domain. A Domain name may be removed from
the InterNIC database, after notice, if at least two Name Servers are
not reachable and functioning properly.
DO NOT list Name Servers if you do not have permission from the owners
to do so. Listing Name Servers without the explicit approval of the
owners is not only unethical, but can cause operational problems for
the Name Servers listed.
The Servers should be in physically separate locations and on different
networks, if possible. The Servers should be active and respond to
Domain Name System (DNS) queries BEFORE this application is submitted.
Incomplete information in Sections 7 and 8 will result in a returned
template. Most ISPs can provide one or more Name Servers if you do not
have your own.
Please provide the Fully Qualified Domain Name (FQDN) of the Host that
is to be the Name Server. For example, enter NS.EXAMPLE.COM and not
just NS.
If several Secondary Servers are desired, copy Section 8 as many times
as needed. Please DO NOT renumber or change the copied Section.
The registration software makes a cross check between the listed pairs
of Host names and IP addresses to see if there are any matches with
either in the database. If a match with an IP address in the database
is found, the name in the database will be assumed. If a match with a
Host name in the database is found, the IP address will be assumed.
If neither match a Host record in the database, the Name Server on the
template will be registered, assigned a handle, and entered into the
database.
Neither the name nor IP address of a registered Name Server will be
changed as a result of a Domain registration. A registered Name
Server's name or IP address can only be changed by submitting a
Host Template available at:
ftp://rs.internic.net/templates/host-template.txt
MODIFYING A DOMAIN NAME RECORD
Changing an existing record is done by replacement. That is, the contents
of various fields in the database are replaced with new information from
the template. If the modification involves first registering a Contact or
Name Server that is not in the database, the instructions for completing
Sections 4-8 in "REGISTERING A NEW DOMAIN NAME" apply. Use WHOIS if you
are not sure about the current information for a Domain, Name Server, or
Contact.
The Domain name itself CAN NOT be modified. To change the Domain name,
send two templates - the first to register the new name and the second
to remove the old name when it is no longer needed.
Changes will/will not be made according to the security parameters
established by the Contacts for the Domain and the entries in items 0b
and 0c. If the Contacts have not chosen any level of security, the
change will be made if the template comes from a reasonable source.
This source may be from a listed Contact for the Domain, others in
the same organization, the current provider, or a new provider that
is about to provide support for the Domain.
Likewise, notification of pending or finished changes will be made
according to the security parameters chosen by the Contacts. If
no security has been chosen, the notification of the change and the
approximate time the change will take effect will be sent to:
- the requester
- if Contacts are changing, both old and new Contacts
- if Name Servers are changing, the Technical Contacts for the
Domains in which the old and new Primary Name Servers reside
This notification will help ensure that all parties involved are aware of,
and agree with, the change.
Section 0 - Authorization
In item 0a, enter the character M or the word MODIFY to indicate a
modification to an existing Domain registration. Transfer of a name
from one organization to another is not considered to be a modification.
See "TRANSFERRING A DOMAIN NAME".
The Domain Template MODIFY option CAN NOT be used to change the Domain
name itself. If you wish to change the Domain you are using, file a
separate NEW DOMAIN template followed by a DELETE DOMAIN template when
you are ready to have the old name removed.
The Domain Template MODIFY option CAN NOT be used to change the contents
of either a Contact or Host record. Use the corresponding Contact
Template or Host Template to make these changes. See:
ftp://rs.internic.net/templates/contact-template.txt
ftp://rs.internic.net/templates/host-template.txt
If a Contact of the Domain has previously used the Contact Template to
specify the use of Pretty Good Privacy (PGP) or encrypted password, the
authentication scheme and information associated with it should be
listed in items 0b and 0c. These items contain the authorization
information for the sender of an update request and help determine if
the request is coming from a valid sender. These items are REQUIRED
when a domain is being modified.
Item 0b is the type of authentication scheme. It can have values
MAIL-FROM, CRYPT-PW, or PGP. Item 0c is the authorization information
for the selected authentication scheme. As shown by the table below,
items 0b and 0c are REQUIRED only when CRYPT-PW is the selected
authentication scheme.
The different items 0b and 0c combinations are:
If Item 0b is Then Item 0c is
MAIL-FROM Ignored. The FROM field in the mail header of
an update message will be checked to verify the
sender.
MAIL-FROM is the DEFAULT authentication scheme.
CRYPT-PW Cleartext password (the plain text of the encrypted
password).
PGP Ignored. The sender should sign the entire update
message with its secret PGP key and send it in
cleartext to the InterNIC.
Section 1 - Purpose of Registration
Briefly describe the purpose of the modification. If the sender
is not a currently listed Contact, explain your relationship to
the current Contacts and/or the organization holding the name.
Section 2 - Complete Domain Name
Insert the two-part name of the Domain name you wish to modify.
For example, EXAMPLE.COM. Item 2 is REQUIRED.
Section 3 - Organization Using the Domain Name
The Domain name is considered to be registered to an organization,
even if the organization is an individual. Therefore, any
significant change in the organization name or address should be
explained in Section 1. Transfer of a name from one organization
to another is not considered to be a modification. See instructions
in "TRANSFERRING A DOMAIN NAME".
Section 4, 5, 6 - Contacts
A Contact can only be changed by replacing with another individual
or role Contact. Replacement can be accomplished by placing the
handle of a Contact that is already registered in item "a" or by
registering a new Contact by completing items "b" through "l".
To modify the record of an existing Contact, use the Contact Template
available at:
ftp://rs.internic.net/templates/contact-template.txt
Section 7, 8 - Name Servers
When modifying the Name Server list, provide the COMPLETE LIST of
Name Servers. The same instructions apply as for creating a new
Domain. The Domain Template CAN NOT be used to change the name or
IP address of a Name Server that is already registered. To modify
the record of an existing Host, use the Host Template available at:
ftp://rs.internic.net/templates/host-template.txt
DELETING A DOMAIN NAME RECORD
A Domain name may be removed from the InterNIC database and hence from the
Root Servers under the following conditions:
- A request for deletion comes from an authorized source
- As part of a transfer to another organization
- Failure to provide name service for a 90-day period
- Failure to pay the registration or maintenance fee
If a request for deletion comes for the Administrative or Technical Contact,
and meets the security requirements, it will be processed. If the request
comes from the Internet Service Provider (ISP) currently providing name
service for the Domain name, the name will be placed on HOLD for 60 days
to give the organization a chance to find another provider.
If the request comes from none of the above, and does not meet any security
established for the Contacts, it will be returned for further explanation
of the relationship between the requester and holding organization. The
Administrative and Technical Contacts will be notified via email.
When a name is transferred from one organization to another, the InterNIC
will first delete the existing record and then process a new registration.
See instructions in "TRANSFERRING A DOMAIN NAME".
If an ISP removes name service or if the InterNIC detects lack of name
service through its lame delegation policy, the name will be placed on
HOLD. HOLD means that the Domain will be visible via WHOIS but will
not be active in the Root Servers, that is, it can not be used. The
organization holding the name will have up to 60 days to get name
service restored. If at the end of this time, active Name Servers have
not been provided, the name will be removed. See the lame delegation
policy draft available at:
ftp://rs.internic.net/policy/internic/internic-domain-5.txt
Notification of the deletion and the approximate time it will take effect
will be sent to:
- the requester
- the current Contacts
- the Technical Contact for the Domain in which the Primary Name Server
resides
Section 0 - Authorization
In item 0a, enter the character D or the word DELETE to indicate the
deletion of an existing Domain name registration.
If a Contact of the Domain has previously used the Contact Template to
specify the use of Pretty Good Privacy (PGP) or encrypted password, the
authentication scheme and information associated with it should be
listed in items 0b and 0c. These items contain the authorization
information for the sender of an update request and help determine if
the request is coming from a valid sender. These items are REQUIRED
when a domain is being deleted.
Item 0b is the type of authentication scheme. It can have values
MAIL-FROM, CRYPT-PW, or PGP. Item 0c is the authorization information
for the selected authentication scheme. As shown by the table below,
items 0b and 0c are REQUIRED only when CRYPT-PW is the selected
authentication scheme.
The different items 0b and 0c combinations are:
If Item 0b is Then Item 0c is
MAIL-FROM Ignored. The FROM field in the mail header of
an update message will be checked to verify the
sender.
MAIL-FROM is the DEFAULT authentication scheme.
CRYPT-PW Cleartext password (the plain text of the encrypted
password).
PGP Ignored. The sender should sign the entire update
message with its secret PGP key and send it in
cleartext to the InterNIC.
Section 1 - Purpose of Registration
Briefly describe the reason for the deletion. If the sender is not
a currently listed Contact, explain your relationship to the current
Contacts and/or the organization holding the name.
Section 2 - Complete Domain Name
Insert the two-part name of the Domain name you wish to have deleted.
For example, EXAMPLE.COM. Item 2 is REQUIRED.
Section 3 - Section 9
These Sections should be removed or left blank.
TRANSFERRING A DOMAIN NAME
A domain name should be transferred ONLY if the organization is changing.
Two separate templates are REQUIRED to transfer a Domain name. The
first template requests a DELETE of the Domain name by the current
Domain name holder. The second template requests a NEW Domain name
registration from the organization seeking to obtain the Domain name.
Whenever possible, these two templates should be sent in the same message.
The following procedures apply:
The Domain name Administrative Contact listed in the Domain name
record on file with InterNIC Registration Services MUST complete
Sections 0-2 of the Domain Template. Item 0a should reflect DELETE.
The subject line of the message should read "TRANSFER DOMAIN" followed
by the Domain name being transferred. If the current Contact no
longer has access to the Internet, a fax authorizing the transfer
may be sent to the InterNIC and the recipient.
Send the DELETE template to the person representing the organization
to which the name is to be transferred.
If the recipient of the Domain name does not have Internet access,
they can obtain an email account through the Internet Service Provider
(ISP) they have selected to support the Domain name.
The recipient of the Domain name should complete a different Domain
Template with item 0a reflecting NEW.
Append the second template to the email from the current Domain
holder and forward the joined templates as a single message to
HOSTMASTER@INTERNIC.NET.
Please note that the email headers from both parties MUST be intact
to provide evidence of appropriate authorization. If it is not clear
that the transfer is authorized by the current holder, the templates
WILL NOT be processed.