CERNIC-012
----------
CERNIC-012 Shuang Zhu, szhu@net.edu.cn
CERNIC-010, 006 1995
Registration Document 1996,1997
Amended: 20011220
China Education and Research Network Information Center
Procedures for the registration of EDU.CN domain
1.0 Introduction
----------------
This document describes the new format of domain registration
submission and includes a new registration template. There are some
changes to the response method and some items of maintanence purposes
such as "mnt-by:", "remarks:", "notify:" are removed for some reason.
It is strongly recommended that you read this document entirely prior
to filling out your registration template and submitting it to CERNIC.
Since the registration mechanism is semiautomated, even small syntax
errors will result in your registration not being processed.
1.1 Prerequisite
----------------
You should have got official IP address from CERNIC, or other service
providers and have established physical and IP network connection with
CERNET before you send us your domain registration requests.
2.0 Registration Procedure
--------------------------
The registration procedure is broken down into two steps, namely:
1) filling in the registration form
2) submitting the registration form to auto-dbm@net.edu.cn
The first step will entail obtaining the CERNIC Domain registration
form (included at the end of this document) and supplying values for
all mandatory fields. Note that latest version of templates are in
http://www.nic.edu.cn/RS/templates/index.html
The template will be scanned for syntax errors and, if none are
found, the appropriate changes will be immediately made. Note that all
updates are logged within CERNIC to insure that erroneous or malicious
updates can be detected and corrected.
After submitting your template via email, you should receive back a
response in 2 days. If any errors were detected in your submission,
no changes will be made to the CERNIC registration database and you will
be informed to submit your application again. If non-fatal errors
are detected, the database software will flag the errors as 'warnings'
and return your template. Note however that warnings are only advisory
and your registration request will be accepted in the database (perhaps
with some modifications as noted in the warning message(s)). It is
recommended that in future submissions you correct the specific problems
which generated the warnings prior to submitting a new update. If no
errors or warnings are detected in your template, a notifying message
will be returned to you and your regional network center ( in case your
email address is unreachable ).
If you believe your submission was rejected erroneously or you
have any questions regarding your submission, please contact CERNIC
at HOSTMASTER@NET.EDU.CN.
3.0 Registration Template Format
--------------------------------
The following sections detail the specific tags and values which
should be present on your registration submission. Please note that
the registration procedure is semi-automated and even small deviations
from the syntax which will be provided below can result in your requests
being refused or generating warning messages. If you have any questions,
feel free to contact CERNIC at your convenience.
3.1 Domain Details
-------------------
The tags and values provided in this section make up the 'domain'
object in the CERNIC registration database. This information corresponds
to the actual network you are registering, which is official IP network
number applied from CERNIC.
domain:
Status: mandatory, only one line allowed
Please complete with a full-qulified domain name which is actually
subdomain of EDU.CN. See also cernic-002 for more subdomain details.
Example:
domain: TSINGHUA.EDU.CN
inetnum:
Status: mandatory, only one line allowed
The inetnum attribute contains the range of IP address space this
object gives information on. The syntax of this attribute can be
as the following:
inetnum: 192.87.160.0 - 192.87.167.255
Please note that there should be a space before and after "-" ,
also note that in the dotted quad notation of IP addresses, all
trailing zeros must be present.
netname:
Status: mandatory, only one line allowed
Please complete with an appropriate network name for the network to be
numbered which is short and meaningful. The `netname' is used mainly
for administrative purposes like consistency checking of the Internet
Registry. You will most likely not see this name appear anywhere, but
on forms like this. The network name should be written in less than
25 capital alphanumeric characters only. Please do not use
punctuation, special characters or a prefix or suffix of 'NET', 'LAN',
etc (unless they are part of your orgnization name). Example:
netname: JSUST-CN
orgname:
Status: mandatory, only one line allowed
Please complete with the organization (university, institute) name.
Example:
orgname: Tsinghua University
Note that the following street, city, province, and postalcode items
make up the full postal address of the person.
street:
Status: mandatory, only one line allowed
please specify the organization's postal address, may contain Road,
Street, District, etc. An example:
street: #100, Xue Yuan Nan Lu Road, Haidian District
city:
Status: mandatory, only one line allowed
please specify the city (or county) name. Example: for Foshan City,
city: Foshan
province:
Status: mandatory, only one line allowed
Please give the two letter province code ( see also Appendix A )
which is appropriate for the education and research community. If
your network is cross the provinces, please base the code on where
administrative contact works, Please see Appendix A of this
document if you do not know the appropriate code for your province.
Example: Jiangsu Province
province: JS
postalcode:
Status: mandatory, only one line allowed
Provide the orgnization's postal code. Example:
postalcode: 100084
c-orgname:
Status: mandatory, only one line allowed
Please complete with the organization (university, institute) name,
specified in CHINESE hanzi characters. Example:
c-orgname: 清华大学
Note that the following c-street, c-city, c-province items must
specify in CHINESE hanzi characters corresponding to street, city,
province items stated above.
c-street:
Status: mandatory, only one line allowed
please specify the organization's Postal address, may contain Road,
Street, District, etc in CHINESE hanzi Characters. An example:
c-street: 海淀区学院南路100号
c-city:
Status: mandatory, only one line allowed
please specify the city (or county) name. Example: Foshan City
c-city: 佛山
c-province:
Status: mandatory, only one line allowed
Please give the province name in Chinese Hanzi Characters (see also
Appendix A). An example: Jiangsu Province
c-province: 江苏
admin-c:
Status: mandatory, only one line allowed
Please complete with the name or NIC handle (prefered) of the person
who is the administrative contact for the domain. The NIC handle
(if known) is preferred. This person must be someone who is physically
located at the site of the network. Please do not use formal titles
like `Dr' or `Prof.' or `Sir'. Please specify as in the example below.
Example:
admin-c: YL20-CER
admin-c: Yingdong Li // if he has not such a nic-hdl
tech-c:
Status: mandatory, only one line allowed
Please give the name of technical contact person (or NIC handle as
mentioned above). NOTE: please give names for both the administrative
AND the technical contact. If different names are not appropriate,
then the same name for both contacts is fine.
Example:
tech-c: YL20-CER
tech-c: Yingdong Li // if he has not such a nic-hdl
nserver:
Status: mandatory, multiple lines allowed
The nserver attribute contains the fully qualified domain name of the
machine that runs DNS system for your domain (called domain name server).
There should be 2 domain name servers ( one is primary, the other is
secondary ) at least. If there are multiple name servers for this domain,
they should all be specified on different lines. Only one hostname is
allowed per line. An example:
nserver: dns1.tsinghua.edu.cn
nserver: dns2.tsinghua.edu.cn
changed:
Status: mandatory, only one line allowed
The changed field contains information on who last changed this
object, and when this change was made. The format is an RFC 822
electronic mail address of the person who made the change, and the
date of change in YYYYMMDD format. Multiple lines are allowed and
shows the update history of an object. An example:
changed: szhu@net.edu.cn 19950113
source:
Status: mandatory, only one line allowed, fixed value
The source contains a source of information. For the CERNIC database,
the value should always be "CERNIC". This field is used to combine
and exchange information between various database sources around
the world. Fixed value:
source: CERNIC
3.2 Contact Person Details
--------------------------
person:
Status: mandatory, only one line allowed
The person attribute contains the full name (first, last) as specified
as a technical or administrative contact in another object. The name
must be written identically to those given in the tech-c and admin-c
attribute of for example the domain object (but must NOT be the NIC
handle). Again here, official titles like 'Dr', 'Prof' or 'Sir' should
not be used. An example:
person: Shuang Zhu
c-name:
Status: mandatory, only one line allowed
The c-name attribute contains the full name. please spell the person
name in CHINESE Hanzi Characters. <姓><名>, An example:
c-name: 朱爽
nic-hdl:
Status: mandatory, only one line allowed
The nic-hdl attribute contains the officially assigned CERNIC handle
for this person. NIC handles are unique identifiers assigned and used
by the registries to unambiguously refer to Internet people. CERNIC
handles consists of 3 parts: <prefix><index><postfix> (see also
cernic-005). If a person does not yet have a handle, please specify
the value as ASSIGN, An example:
nic-hdl: SZ1-CER
orgname:
Status: optional, only one line allowed
Please complete with the organization (university, institute) name.
Example:
orgname: Tsinghua University
Note that the following street, city, province, and postalcode items
make up the full postal address of the person.
street:
Status: optional, only one line allowed
please specify the organization's postal address, may contain Road,
Street, District, etc. An example:
street: 100# , Xue Yuan Nan Lu Road, Haidian District
city:
Status: optional, only one line allowed
please specify the city (or county) name. Example: for Foshan City,
city: Foshan
province:
Status: optional, only one line allowed
Please give the two letter province code ( see also Appendix A )
which is appropriate for the education and research community. If
your network is cross the provinces, please base the code on where
administrative contact works, Please see Appendix A of this
document if you do not know the appropriate code for your province.
Example: Jiangsu Province
province: JS
postalcode:
Status: optional, only one line allowed
Provide the orgnization's postal code. Example
postalcode: 100084
c-orgname:
Status: optional, only one line allowed
Please complete with the organization (university, institute) name,
specified in CHINESE hanzi characters. Example:
c-orgname: 清华大学
Note that the following c-street, c-city, c-province items must
specify in CHINESE hanzi characters corresponding to street, city,
province items stated above.
c-street:
Status: optional, only one line allowed
please specify the organization's street address, may contain Road,
Street, District, etc. in CHINESE hanzi characters. An example:
c-street: 海淀区学院南路100号
c-city:
Status: optional, only one line allowed
please specify the city (or county) name. Example: Foshan City
c-city: 佛山
c-province:
Status: optional, only one line allowed
Please give the province name in Chinese Hanzi Characters (see also
Appendix A). An example: Jiangsu Province
c-province: 江苏
e-mail:
Status: mandatory, only one line allowed
The e-mail attribute contains the electronic mail address for this
person if applicable. This should be a valid RFC 822 electronic mail
address, preferably in full domain syntax. An example:
e-mail: szhu@net.edu.cn
phone:
Status: mandatory, only one line allowed
The phone attribute contains the telephone number for this person. It
has the following format: +<country code>-<area code>-<phone number>.
The <phone number> can be split with dashes to denote exchange and
subscriber number. Most countries should drop a leading zero when
specifying their area code. Multiple phone numbers should be specified
in order of preference on different lines. An extension reachable only
through an operator can be specified by adding "ext." and the phone
extension to the phone number. An example:
phone: +86-10-6278-5931
fax-no:
Status: optional, only one line allowed
The fax-no attribute contains the telefax number for this person. It
has the same format as the phone number explained above. An example:
fax-no: +86-10-6278-5933
changed:
Status: mandatory, only one line allowed
The changed field contains information on who last changed this
object, and when this change was made. The format is an RFC 822
electronic mail address of the person who made the change, and the
date of change in YYYYMMDD format. Multiple lines are allowed and
shows the update history of an object. An example:
changed: we@tsinghua.edu.cn 19950113
source:
Status: mandatory, only one line allowed, fixed value
The source contains a source of information. For the CERNIC database,
the value should always be "CERNIC". This field is used to combine
and exchange information between various database sources around
the world. Fixed value:
source: CERNIC
3.3 Host details
----------------
host:
Status: mandatory, only one line allowed
The host attribute contains the full name as specified as a host in
another object. The name must be written identically to those given in
the nserver attribute of for example the domain object.
An example:
host: dns1.tsinghua.edu.cn
ipnum:
Status: mandatory, only one line allowed
The ip attribute contains IP number of the host. The value must be an
internet official number. An example:
ipnum: 166.111.250.6
changed:
Status: mandatory, only one line allowed
The changed field contains information on who last changed this
object, and when this change was made. The format is an RFC 822
electronic mail address of the person who made the change, and the
date of change in YYYYMMDD format. Multiple lines are allowed and
shows the update history of an object. An example:
changed: we@tsinghua.edu.cn 19950113
source:
Status: mandatory, only one line allowed, fixed value
The source contains a source of information. For the CERNIC database,
the value should always be "CERNIC". This field is used to combine
and exchange information between various database sources around the
world. Fixed value:
source: CERNIC
4.0 Conclusions
---------------
Use of the new registration submission should allow the education
and research community to keep the CERNIC registration database more
practical. If you have any questions or comments, please feel free
to contact CERNIC, HOSTMASTER@NET.EDU.CN at your convenience.
5.0 Example
-----------
domain: tsinghua.edu.cn
inetnum: 166.111.0.0 - 166.111.255.255
netname: TSINGHUA-CN
orgname: Tsinghua University
street: Qinghua Yuan, Haidian District
city: Beijing
province: BJ
postalcode: 100084
c-orgname: 清华大学
c-street: 海淀区清华园
c-city: 北京市
c-province: 北京
admin-c: SZ1-CER
tech-c: SZ1-CER
nserver: dns1.tsinghua.edu.cn
nserver: dns2.tsinghua.edu.cn
changed: szhu@net.edu.cn 19950113
source: CERNIC
person: Shuang Zhu
c-name: 朱爽
nic-hdl: SZ1-CER
orgname: Tsinghua University
street: Qinghua Yuan, Haidian District
city: Beijing
province: BJ
postalcode: 100084
c-orgname: 清华大学
c-street: 海淀区清华园
c-city: 北京
c-province: 北京
phone: +86-10-6278-5931
fax-no: +86-10-6278-5933
e-mail: szhu@net.edu.cn
changed: szhu@net.edu.cn 19950113
source: CERNIC
host: dns1.tsinghua.edu.cn
ipnum: 166.111.250.6
changed: szhu@net.edu.cn 19950113
source: CERNIC
host: dns2.tsinghua.edu.cn
ipnum: 166.111.1.6
changed: szhu@net.edu.cn 19950113
source: CERNIC
6.0 Blank Template
------------------
Please fill out the template on the next page and submit to:
auto-dbm@net.edu.cn
The results of your registration will be emailed back to you and your
regional network center ( in case your email address is unreachable ).
- - - - - - - - - - - - - Cut Here - - - - - - - - - - - - -
domain:
netname:
inetnum:
orgname:
street:
city:
province:
postalcode:
c-orgname:
c-street:
c-city:
c-province:
admin-c:
tech-c:
nserver:
nserver:
changed:
source: CERNIC
person:
c-name:
nic-hdl:
orgname:
street:
city:
province:
postalcode:
c-orgname:
c-street:
c-city:
c-province:
phone:
fax-no:
e-mail:
changed:
source: CERNIC
host:
ipnum:
changed:
source: CERNIC
- - - - - - - - - - - - - Cut Here - - - - - - - - - - - - -
Appendix A
----------
Here is a list for the province attribute 2-char code and the c-province
attribute Chinese Hanzi Characters for the Provinces ( Zones, Cities )
in China.
Note: these codes are only used mainly for administrative purposes in
CERNIC Registry Database. You will most likely not see this code appear
anywhere, but on CERNIC forms like this.
____________________________________
| NAME | province | c-province|
|-------------|----------|-----------|
| Anhui | AH | 安徽 |
| Beijing | BJ | 北京 |
| Chongqing | CQ | 重庆 |
| Fujian | FJ | 福建 |
| Guangdong | GD | 广东 |
| Gansu | GS | 甘肃 |
| Guangxi | GX | 广西 |
| Guizhou | GZ | 贵州 |
| Henan | HA | 河南 |
| Hubei | HB | 湖北 |
| Hebei | HE | 河北 |
| Hainan | HI | 海南 |
| Hongkong | HK | 香港 |
| Heilongjiang| HL | 黑龙江 |
| Hunan | HN | 湖南 |
| Jilin | JL | 吉林 |
| Jiangsu | JS | 江苏 |
| Jiangxi | JX | 江西 |
| Liaoning | LN | 辽宁 |
| Macau | MO | 澳门 |
| Neimenggu | NM | 内蒙古 |
| Ningxia | NX | 宁夏 |
| Qinghai | QH | 青海 |
| Sichuan | SC | 四川 |
| Shandong | SD | 山东 |
| Shanghai | SH | 上海 |
| Shaanxi | SN | 陕西 |
| Shanxi | SX | 山西 |
| Tianjin | TJ | 天津 |
| Taiwan | TW | 台湾 |
| Xinjiang | XJ | ** |
| Xizhang | XZ | ** |
| Yunnan | YN | 云南 |
| Zhejiang | ZJ | 浙江 |
|_____________|__________|___________|
