[root@localhost ~]# cat /etc/samba/smb.conf
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
#  http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
#
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
#  http://www.samba.org/samba/docs/Samba-Guide.pdf
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#---------------
# SELINUX NOTES:
#
# If you want to use the useradd/groupadd family of binaries please run:
# setsebool -P samba_domain_controller on
#
# If you want to share home directories via samba please run:
# setsebool -P samba_enable_home_dirs on
#
# If you create a new directory you want to share you should mark it as
# "samba-share_t" so that selinux will let you write into it.
# Make sure not to do that on system directories as they may already have
# been marked with othe SELinux labels.
#
# Use ls -ldZ /path to see which context a directory has
#
# Set labels only on directories you created!
# To set a label use the following: chcon -t samba_share_t /path
#
# If you need to share a system created directory you can use one of the
# following (read-only/read-write):
# setsebool -P samba_export_all_ro on
# or
# setsebool -P samba_export_all_rw on
#
# If you want to run scripts (preexec/root prexec/print command/...) please
# put them into the /var/lib/samba/scripts directory so that smbd will be
# allowed to run them.
# Make sure you COPY them and not MOVE them so that the right SELinux context
# is applied, to check all is ok use restorecon -R -v /var/lib/samba/scripts
#
#--------------
#
#======================= Global Settings =====================================

[global]

# ----------------------- Netwrok Related Options -------------------------
#
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
#
# server string is the equivalent of the NT Description field
#
# netbios name can be used to specify a server name not tied to the hostname
#
# Interfaces lets you configure Samba to use multiple interfaces
# If you have multiple network interfaces then you can list the ones
# you want to listen on (never omit localhost)
#
# Hosts Allow/Hosts Deny lets you restrict who can connect, and you can
# specifiy it as a per share option as well
#
        workgroup = MYGROUP
        server string = Samba Server Version %v

;       netbios name = MYSERVER

;       interfaces = lo eth0 192.168.12.2/24 192.168.13.2/24
;       hosts allow = 127. 192.168.12. 192.168.13.

# --------------------------- Logging Options -----------------------------
#
# Log File let you specify where to put logs and how to split them up.
#
# Max Log Size let you specify the max size log files should reach

        # logs split per machine
        log file = /var/log/samba/log.%m
        # max 50KB per log file, then rotate
        max log size = 50

# ----------------------- Standalone Server Options ------------------------
#
# Scurity can be set to user, share(deprecated) or server(deprecated)
#
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.

        security = user
        passdb backend = tdbsam

# ----------------------- Domain Members Options ------------------------
#
# Security must be set to domain or ads
#
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
#
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
#
# Use password server option only with security = server or if you can't
# use the DNS to locate Domain Controllers
# The argument list may include:
#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
#   password server = *

;       security = domain
;       passdb backend = tdbsam
;       realm = MY_REALM

;       password server = <NT-Server-Name>

# ----------------------- Domain Controller Options ------------------------
#
# Security must be set to user for domain controllers
#
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
#
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
#
# Domain Logons let Samba be a domain logon server for Windows workstations.
#
# Logon Scrpit let yuou specify a script to be run at login time on the client
# You need to provide it in a share called NETLOGON
#
# Logon Path let you specify where user profiles are stored (UNC path)
#
# Various scripts can be used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
#
;       security = user
;       passdb backend = tdbsam

;       domain master = yes
;       domain logons = yes

        # the login script name depends on the machine name
;       logon script = %m.bat
        # the login script name depends on the unix user used
;       logon script = %u.bat
;       logon path = \\%L\Profiles\%u
        # disables profiles support by specifing an empty path
;       logon path =         

;       add user script = /usr/sbin/useradd "%u" -n -g users
;       add group script = /usr/sbin/groupadd "%g"
;       add machine script = /usr/sbin/useradd -n -c "Workstation (%u)" -M -d /nohome -s /bin/false "%u"
;       delete user script = /usr/sbin/userdel "%u"
;       delete user from group script = /usr/sbin/userdel "%u" "%g"
;       delete group script = /usr/sbin/groupdel "%g"

# ----------------------- Browser Control Options ----------------------------
#
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
#
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
#
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
;       local master = no
;       os level = 33
;       preferred master = yes

#----------------------------- Name Resolution -------------------------------
# Windows Internet Name Serving Support Section:
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
#
# - WINS Support: Tells the NMBD component of Samba to enable it's WINS Server
#
# - WINS Server: Tells the NMBD components of Samba to be a WINS Client
#
# - WINS Proxy: Tells Samba to answer name resolution queries on
#   behalf of a non WINS capable client, for this to work there must be
#   at least one        WINS Server on the network. The default is NO.
#
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups.

;       wins support = yes
;       wins server = w.x.y.z
;       wins proxy = yes

;       dns proxy = yes

# --------------------------- Printing Options -----------------------------
#
# Load Printers let you load automatically the list of printers rather
# than setting them up individually
#
# Cups Options let you pass the cups libs custom options, setting it to raw
# for example will let you use drivers on your Windows clients
#
# Printcap Name let you specify an alternative printcap file
#
# You can choose a non default printing system using the Printing option

        load printers = yes
        cups options = raw

;       printcap name = /etc/printcap
        #obtain list of printers automatically on SystemV
;       printcap name = lpstat
;       printing = cups

# --------------------------- Filesystem Options ---------------------------
#
# The following options can be uncommented if the filesystem supports
# Extended Attributes and they are enabled (usually by the mount option
# user_xattr). Thess options will let the admin store the DOS attributes
# in an EA and make samba not mess with the permission bits.
#
# Note: these options can also be set just per share, setting them in global
# makes them the default for all shares

;       map archive = no
;       map hidden = no
;       map read only = no
;       map system = no
;       store dos attributes = yes

#============================ Share Definitions ==============================

[homes]
        comment = Home Directories
        browseable = no
        writable = yes
;       valid users = %S
;       valid users = MYDOMAIN\%S

[printers]
        comment = All Printers
        path = /var/spool/samba
        browseable = no
        guest ok = no
        writable = no
        printable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
;       [netlogon]
;       comment = Network Logon Service
;       path = /var/lib/samba/netlogon
;       guest ok = yes
;       writable = no
;       share modes = no

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;       [Profiles]
;       path = /var/lib/samba/profiles
;       browseable = no
;       guest ok = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;       [public]
;       comment = Public Stuff
;       path = /home/samba
;       public = yes
;       writable = yes
;       printable = no
;       write list = +staff

Ãû³Æ
samba - A Windows SMB/CIFS fileserver for UNIX

samba - ÔÚUNIXÉÏʵÏÖWindows SMB/CIFS ЭÒéµÄÎļþ·þÎñÆ÷

SYNOPSIS
´ó¸Ù

samba

DESCRIPTION
ÃèÊö

The samba software suite is a collection of programs that implements the
Server Message Block(commonly abbreviated as SMB) protocol for UNIX systems.
This protocol is sometimes also referred to as the Common Internet File
System (CIFS), LanManager or NetBIOS protocol.

sambaÌ×¼þÊÇÔÚUNIXϵͳÉÏʵÏÖ¡°·þÎñÆ÷ÐÅÏ¢¿é¡±(ͨ³£¼ò³ÆSMB)ЭÒéµÄÒ»×é³ÌÐò¡£Õâ¸öЭ
ÒéÓÐʱҲ³ÆΪ¡°Í¨Óû¥ÁªÍøÎļþϵͳ£¬LanManager»òNetBIOSЭÒ顱¡£

COMPONENTS
×é³É

The samba suite is made up of several components. Each component is described
in a separate manual page. It is strongly recommended that you read the
documentation that comes with samba and the manual pages of those components
that you use. If the manual pages aren clear enough then please send a
patch or bug report to samba-bugs@samba.org.

sambaÓɼ¸¸ö²¿¼þ×é³É¡£Ã¿¸ö²¿¼þÔÚһϵÁеÄÎĵµÖб»ÃèÊö¡£Ç¿ÁÒÍƼöÄãÔĶÁÕâЩsamba±¾
ÉíºÍÄãËùÓõÄÄÇЩ²¿¼þµÄÊÖ²áÖеÄÎĵµ¡£Èç¹ûÊֲ᲻¹»ÇåÎúÇëÏòÕâ¸öµØÖ··¢ËÍÒ»¸ö²¹¶¡»ò
Õß´íÎ󱨸棺samba-bugs@samba.org

¡¡
smbd

The smbd (8) daemon provides the file and print services to SMB clients, such
as Windows 95/98, Windows NT, Windows for Workgroups or LanManager. The
configuration file for this daemon is described in smb.conf (5).
smbd (8)ÊØ»¤³ÌÐòΪSMB¿Í»§£¬ÀýÈçWindows 95/98£¬Windows NT£¬Windows for
Workgroups»òÕßÊÇLanManager£¬ÌṩÁËÎļþºÍ´òÓ¡·þÎñ¡£ËüµÄÏàÓ¦ÅäÖÃÎļþÔÚsmb.conf
(5)ÖÐÃèÊö¡£
nmbd

The nmbd (8) daemon provides NetBIOS nameserving and browsing support. The
configuration file for this daemon is described in smb.conf (5).
nmbd (8)ÊØ»¤³ÌÐòÌṩNetBIOSÃû×Ö·þÎñºÍä¯ÀÀÖ§³Ö¡£ËüµÄÏàÓ¦ÅäÖÃÎļþÔÚsmb.conf (5)
¡¡
smbd

The smbd (8) daemon provides the file and print services to SMB clients, such
as Windows 95/98, Windows NT, Windows for Workgroups or LanManager. The
configuration file for this daemon is described in smb.conf (5).
smbd (8)ÊØ»¤³ÌÐòΪSMB¿Í»§£¬ÀýÈçWindows 95/98£¬Windows NT£¬Windows for
Workgroups»òÕßÊÇLanManager£¬ÌṩÁËÎļþºÍ´òÓ¡·þÎñ¡£ËüµÄÏàÓ¦ÅäÖÃÎļþÔÚsmb.conf
(5)ÖÐÃèÊö¡£

nmbd

The nmbd (8) daemon provides NetBIOS nameserving and browsing support. The
configuration file for this daemon is described in smb.conf (5).
nmbd (8)ÊØ»¤³ÌÐòÌṩNetBIOSÃû×Ö·þÎñºÍä¯ÀÀÖ§³Ö¡£ËüµÄÏàÓ¦ÅäÖÃÎļþÔÚsmb.conf (5)
testprns (1)¹¤¾ßÓÃÀ´²âÊÔÄãÔÚprintcapÎļþÖж¨ÒåºÃµÄ´òÓ¡»ú¡£

smbstatus

The smbstatus (1) utility allows you list current connections to the smbd (8)
server.
smbstatus (1)¹¤¾ßÓÃÀ´Áгöµ±Ç°ÔÚsmbd (8)·þÎñÆ÷ÉϵÄÁª½Ó¡£
nmblookup

the nmblookup (1) utility allows NetBIOS name queries to be made from the
UNIX machine.
nmblookup (1)¹¤¾ßÓÃÀ´ÏòUNIX»úÆ÷²éѯNetBIOSÃû×Ö¡£
make_smbcodepage

The make_smbcodepage (1) utility allows you to create SMB code page
definition files for your smbd (8) server.
make_smbcodepage (1)¹¤¾ßÓÃÀ´ÎªÄãµÄsmbd (8)·þÎñÆ÷½¨Á¢SMB´úÂëÒ³¶¨ÒåÎļþ¡£
smbpasswd

The smbpasswd (8) utility allows you to change SMB encrypted passwords on
samba and Windows NT(tm) servers.
¹¤¾ßÓÃÀ´ÔÚsambaºÍNT·þÎñÆ÷ÉϸıäSMB¼ÓÃÜ¿ÚÁî¡£

AVAILABILITY
ÓÐЧÐÔ

The samba software suite is licensed under the GNU Public License (GPL). A
copy of that license should have come with the package in the file COPYING.
You are encouraged to distribute copies of the samba suite, but please obey
the terms of this license.

sambaÌ×¼þÓÉGNU¹«¹²Ð­Òé±£»¤¡£ÔÚÈí¼þ°üµÄCOPYINGÎļþÖаüº¬ÁËÒ»·ÝЭÒéµÄ¸´±¾¡£Äã¿É
ÒÔÉ¢²¼Ì×¼þµÄ¿½±´£¬µ«Çë·þ´ÓЭÒéÌõ¿î¡£

The latest version of the samba suite can be obtained via anonymous ftp from
samba.org in the directory pub/samba/. It is also available on several mirror
sites worldwide.

sambaÌ×¼þµÄ×îа汾¿ÉÒÔͨ¹ýλÓÚsamba.orgµÄÄäÃûFTPÉϵÄ/pub/sambaĿ¼»ñµÃ£¬µ±È»
Ò²¿ÉÒÔÔںܶ໥ÁªÍøÉϵľµÏñÕ¾µãÖлñµÃ¡£

You may also find useful information about samba on the newsgroup
comp.protocols.smb and the samba mailing list. Details on how to join the
mailing list are given in the README file that comes with samba.

ÄãÒ²ÄÜÔÚcomp.protocols.smbÐÂÎÅ×éºÍsambaµÄÓʼþÁбíÉÏÕÒµ½Ïà¹ØµÄÓÐÓÃÐÅÏ¢¡£ÔÚsamba
µÄREADMEÎļþÖиø³öÁ˼ÓÈëÓʼþÁбíµÄÏêϸ×ÊÁÏ¡£

If you have access to a WWW viewer (such as Netscape or Mosaic) then you will
also find lots of useful information, including back issues of the samba
mailing list, at http://samba.org/samba/.

ÈçºÎÄãÄÜÓÃWWWä¯ÀÀÆ÷µÄ»°£¬ÔÚhttp://samba.org/samba/½«»áÕÒµ½°üÀ¨sambaÓʼþÁбíÎÊ
ÌâÔÚÄڵķdz£¶àµÄÓÐÓÃÐÅÏ¢¡£

VERSION
°æ±¾

This man page is correct for version 2.0 of the samba suite.

Õâ·ÝÊÖ²áÊÇÕë¶ÔsambaÌ×¼þ°æ±¾2.0µÄ¡£

CONTRIBUTIONS
Ͷ¸å

If you wish to contribute to the samba project, then I suggest you join the
samba mailing list at samba@samba.org. See the Web page at http://samba.org/li
stproc for details on how to do this.

Èç¹ûÄãÏëÏòsamba¼Æ»®Í¶¸åµÄ»°£¬½¨ÒéÄãµ½samba@samba.org¼ÓÈësambaµÄÓʼþÁÐ±í£¬Ïêϸ
½éÉÜÇë¿´ÔÚhttp://samba.org/listprocµÄÍøÒ³¡£

If you have patches to submit or bugs to report then you may mail them
directly to samba-bugs@samba.org. Note, however, that due to the enormous
popularity of this package the samba Team may take some time to respond to
mail. We prefer patches in diff -u format.

Èç¹ûÄãÒ»¸ö²¹¶¡ÐèÒªÌá½»»òÕßÒª±¨¸æÒ»¸ö´íÎóµÄ»°¿ÉÒÔÖ±½ÓÏòsamba-bugs@samba.org·¢ÐÅ
¡£×¢Ò⣬samba¿ª·¢×é¿ÉÒÔ»áÒòΪÕâ¸öÈí¼þ°üµÄѸËÙÁ÷ÐжøÐèÒª»¨·ÑÒ»¶¨µÄʱ¼äÀ´¶ÔÓʼþ
×÷³ö»ØÓ¦¡£ÎÒÃǸüÔ¸ÒâÔÚdiff -f¸ñʽÏÂÐÞ²¹ÎÊÌâ¡£

CREDITS
ÈÙÓþ

Contributors to the project are now too numerous to mention here but all
deserve the thanks of all samba users. To see a full list, look at
ftp://samba.org/pub/samba/alpha/change-log for the pre-CVS changes and at
ftp://samba.org/pub/samba/alpha/cvs.log for the contributors to samba
post-CVS. CVS is the Open Source source code control system used by the samba
Team to develop samba. The project would have been unmanageable without it.

ÔÚ´ËÌá¼°¶Ô¼Æ»®×÷³ö¹±Ï×µÄÈËʵÔÚÌ«¶àÁË£¬µ«ÊÇËùÓеÄsambaÓû§¶¼Ó¦¸Ã¸ÐлËûÃÇ¡£Òª¿´
Ò»·ÝÍêÕûµÄÁÐ±í£¬²éÕÒftp://samba.org/pub/samba/alpha/cvs.log¿ÉÒÔ»ñµÃ²¢·¢°æ±¾Ïµ
ͳԤÏÈÌṩµÄÒ»·Ýά»¤ÕßÃûµ¥£¬²¢ÔÚftp://samba.org/pub/samba/alpha/change-logÖÐÕÒ
µ½±ä¸üºóµÄÄÚÈÝ¡£CVSÊÇsamba¿ª·¢×鿪·¢sambaʱ²ÉÓõĿª·ÅÔ´´úÂë¿ØÖÆϵͳ£¬Ã»ÓÐÕâ¸ö
ϵͳ¼Æ»®½«ÎÞ·¨¹ÜÀí¡£

In addition, several commercial organizations now help fund the samba Team
with money and equipment. For details see the samba Web pages at
http://samba.org/samba/samba-thanks.html.

ÁíÍ⣬һЩÉÌÒµ×éÖ¯ÏÖÔÚÏòsamba¿ª·¢×éÌṩ×ʽðºÍÉ豸ÉϵİïÖú¡£ÏêϸÐÅÏ¢Çë¿´ÍøÒ³
http://samba.org/samba/samba-thanks.html

AUTHOR
×÷Õß

The original samba software and related utilities were created by Andrew
Tridgell samba-bugs@samba.org. samba is now developed by the samba Team as an
Open Source project similar to the way the Linux kernel is developed.

sambaÈí¼þºÍÏà¹Ø¹¤¾ß×î³õÓÉAndrew Tridgell samba-bugs@samba.org´´½¨¡£sambaÏÖÔÚÓÉ
¿ª·¢×é×÷ΪÀàËÆLinuxÄں˿ª·¢²ÉÓõĿª·ÅÔ´´úÂë¼Æ»®·½Ê½À´·¢Õ¹¡£

The original samba man pages were written by Karl Auer. The man page sources
were converted to YODL format (another excellent piece of Open Source
software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the
samba2.0 release by Jeremy Allison. samba-bugs@samba.org.

sambaÊÖ²áÒ³×î³õÓÉKarl Auer׫д¡£ËüµÄÔ´ÂëÒѱ»×ª»»³ÉYODL(Ò»ÖÖ¼«ºÃµÄ¿ª·ÅÔ´´úÂëÈí
¼þ£¬¿ÉÒÔÔÚftp://ftp.icce.rug.nl/pub/unix/´¦»ñµÃ)¸ñʽ²¢ÒÑÓÉJeremy Allison¸üе½
samba2.0°æ±¾¡£

ÐÅÏ¢À´Ô´£ºhttp://linux.sheup.com/linux/linux5331.htm

[root@localhost gaoxl]# yum search mysql
ÔØÈë²å¼þ: refresh-packagekit
================================ Matched: mysql ================================
libgda-mysql.i386 : MySQL provider for libgda
libgda-mysql-devel.i386 : MySQL provider for libgda pkgconfig file
mod_auth_mysql.i386 : Basic authentication for the Apache web server using a
                    : MySQL database
mysql-connector-java.i386 : Official JDBC driver for MySQL
pam_mysql.i386 : PAM module for auth UNIX users using MySQL data base
qt-mysql.i386 : MySQL driver for Qt's SQL classes
Io-language-mysql.i386 : Io mysql bindings
LinLog.i386 : A ham radio logbook for Linux
MySQL-python.i386 : Ò»¸öµ½ MySQL µÄ½çÃæ
apr-util-mysql.i386 : APR utility library MySQL DBD driver
bacula-director-common.i386 : Common Bacula Director files
bacula-director-mysql.i386 : Bacula Director with MySQL database support
bacula-storage-mysql.i386 : MySQL Bacula storage daemon files
bibus.noarch : Bibliographic and reference management software
bibus.i386 : Bibliographic and reference management software
bugzilla.noarch : Bug tracking system
bytefx-data-mysql.i386 : Mono µÄ MySQL Êý¾Ý¿âÁ¬½ÓÐÔ
cacti.noarch : An rrd based graphing tool
callweaver-mysql.i386 : MySQL support for CallWeaver
collectd-mysql.i386 : MySQL module for collectd
dbmail.i386 : The DBMail mail storage system
dbmail-mysql.i386 : The DBMail mail storage system
freeradius-dialupadmin.i386 : Web management for FreeRADIUS
freeradius-dialupadmin-mysql.i386 : MySQL component of the dialupadmin
                                  : FreeRADIUS Web management tool
freeradius-mysql.i386 : MySQL support for freeradius
gallery2.noarch : Customizable photo gallery web site
gnokii-smsd-mysql.i386 : MySQL support for Gnokii SMS daemon
gpsdrive.i386 : A GPS based navigation tool
innotop.noarch : A MySQL and InnoDB monitor program
libdbi-dbd-mysql.i386 : libdbi µÄ MySQL ²å¼þ
libnss-mysql.i386 : NSS library for MySQL
libpreludedb-mysql.i386 : Plugin to use prelude with a mysql database
lighttpd-mod_mysql_vhost.i386 : Virtual host module for lighttpd that uses a
                              : MySQL database
limph.noarch : A PHP5-compatible network host/service poller with web interface
lua-sql.i386 : Database connectivity for the Lua programming language
lua-sql-mysql.i386 : MySQL database connectivity for the Lua programming
                   : language
mantis.noarch : Web-based bugtracking system
moodss.i386 : Powerful modular monitoring graphical application
moomps.i386 : Powerful modular monitoring service
mysql++.i386 : C++ wrapper for the MySQL C API
mysql++-devel.i386 : MySQL++ developer files (headers, examples, etc.)
mysql++-manuals.i386 : MySQL++ user and reference manuals
mysql.i386 : MySQL ¿Í»§¶Ë³ÌÐòºÍ¹²Ïí¿â
mysql-administrator.i386 : GUI tools to manage mysql Databases
mysql-bench.i386 : MySQL ±ê×¼½Å±¾ºÍÊý¾Ý
mysql-connector-odbc.i386 : MySQL µÄ ODBC Çý¶¯³ÌÐò¡£
mysql-devel.i386 : Files for development of MySQL applications
mysql-gui-common.i386 : Common data shared among the MySQL GUI Suites
mysql-gui-tools.i386 : GUI tools to manage mysql Databases
mysql-libs.i386 : MySQL ¿Í»§¶ËËùÐèµÄ¹²Ïí¿â
mysql-proxy.i386 : A proxy for the MySQL Client/Server protocol
mysql-query-browser.i386 : A graphical tool for handling MySQL queries
mysql-server.i386 : MySQL ·þÎñÆ÷ºÍÏà¹ØµÄÎļþ
mysql-test.i386 : The test suite distributed with MySQL
mysqltuner.noarch : MySQL high performance tuning script
mytop.noarch : A top clone for MySQL
nagios-plugins-mysql.i386 : Nagios Plugin - check_mysql
ocaml-mysql.i386 : OCaml library for accessing MySQL databases
ocaml-mysql-devel.i386 : Development files for ocaml-mysql
openser.i386 : Open Source SIP Server
openser-mysql.i386 : MySQL Storage Support for the OpenSER
pdns-backend-mysql.i386 : MySQL backend for pdns
perl-Class-DBI-mysql.noarch : Extensions to Class::DBI for MySQL
perl-DBD-Mock.noarch : Mock database driver for testing
perl-DBD-MySQL.i386 : perl µÄ MySQL ½Ó¿Ú
perl-DBIx-DBSchema.noarch : Database-independent schema objects
perl-DateTime-Format-DBI.noarch : Find a parser class for a database connection
perl-DateTime-Format-MySQL.noarch : Parse and format MySQL dates and times
perl-Text-TabularDisplay.noarch : Display text in formatted table output
perl-Time-Piece-MySQL.noarch : MySQL-specific methods for Time::Piece
php-laconica.noarch : PHP tool for microblogging
php-mysql.i386 : ÓÃÓÚʹÓà MySQL Êý¾Ý¿âµÄ PHP ³ÌÐòµÄÄ£¿é
php-pdo.i386 : A database access abstraction module for PHP applications
php-pear-MDB2-Driver-mysql.noarch : MySQL MDB2 driver
php-pear-MDB2-Driver-mysqli.noarch : MySQL Improved MDB2 driver
phpMyAdmin.noarch : Web based MySQL browser written in php
proftpd-mysql.i386 : Module to add MySQL support to the ProFTPD FTP server
pure-ftpd.i386 : Lightweight, fast and secure FTP server
pyicq-t-mysql.noarch : MySQL backend for ICQ transport
python-openid.noarch : Python OpenID libraries
python-rdflib.i386 : Python library for working with RDF
python-sqlobject.noarch : SQLObject -Object-Relational Manager, aka database
                        : wrapper
python-storm.i386 : An object-relational mapper (ORM) for Python
python-storm-mysql.i386 : MySQL backend for python-storm
qt3-MySQL.i386 : MySQL drivers for Qt 3's SQL classes
rekall.i386 : A KDE database front-end application
rekall-mysql.i386 : Rekall MySQL driver
roundcubemail.noarch : Round Cube Webmail is a browser-based multilingual IMAP
                     : client
rsyslog.i386 : Enhanced system logging and kernel message trapping daemons
rsyslog-mysql.i386 : MySQL support for rsyslog
ruby-mysql.i386 : A Ruby interface to MySQL
rubygem-rails.noarch : Web-application framework
ser-mysql.i386 : MySQL Storage Support for the SIP Express Router
showimg-mysql.i386 : MySQL plugin for the Showimg image database
snort.i386 : Intrusion detection system
snort-bloat.i386 : Snort with Flexible Response
snort-mysql+flexresp.i386 : Snort with Flexible Response
snort-mysql.i386 : Snort with Flexible Response
ulogd-mysql.i386 : MySQL output plugin for ulogd
unixODBC.i386 : A complete ODBC driver manager for Linux
[root@localhost gaoxl]# yum install mysql-server
ÔØÈë²å¼þ: refresh-packagekit
ÉèÖð²×°½ø³Ì
·ÖÎö°²×°²ÎÊýµÄÓï·¨
½â¾öÒÀÀµÏà¹Ø
-->ÔËÐд¦Àí¼ì²é
---> °ü mysql-server.i386 0:5.0.51a-1.fc9 ÉèÖÃΪ Éý¼¶
--> ¹ý³ÌÒÀÀµ: mysql = 5.0.51a-1.fc9 ÒÀÀµÓÚ°ü: mysql-server
-->ÔËÐд¦Àí¼ì²é
---> °ü mysql.i386 0:5.0.51a-1.fc9 ÉèÖÃΪ Éý¼¶
--> Íê³ÉÒÀÀµÐÔ¼ì²é

ÒÀÀµÐÔ½â¾ö

================================================================================
 °ü                    ¼Ü¹¹           °æ±¾                    ²Ö¿â               ´óС  
================================================================================
ÕýÔÚ°²×°:
 mysql-server         i386         5.0.51a-1.fc9         fedora           9.8 M
ΪÒÀÀµ¶ø°²×°:
 mysql                i386         5.0.51a-1.fc9         fedora           2.9 M

Transaction Summary
================================================================================
Install      2 Package(s)        
Update       0 Package(s)        
Remove       0 Package(s)        

×ܹ²ÏÂÔØ´óС: 13 M
È·¶¨ÊÇÕâÑùÂð? [y/N]: y
ÏÂÔØÈí¼þ°ü:
(1/2): mysql-5.0.51a-1.fc9.i386.rpm                      | 656 kB     27:12    
http://download.fedoraproject.org/pub/fedora/linux/releases/9/Everything/i386/os/Packages/mysql-5.0.51a-1.fc9.i386.rpm: [Errno 4] Socket Error: timed out
³¢ÊÔÆäËû¾µÏñ.
(1/2): mysql-5.0.51a-1.fc9.i386.rpm                      | 2.9 MB     03:34    
(2/2): mysql-server-5.0.51a-1.fc9.i386.rpm               | 9.8 MB     15:27    
--------------------------------------------------------------------------------
Total                                           4.6 kB/s |  13 MB     46:39    
ÔËÐÐ rpm_check_debug
ÔËÐвâÊÔÊÂÎñ´¦Àí
´«Êä²âÊÔÍê³É
ÊÂÎñ´¦Àí²âÊԳɹ¦
ÔËÐÐÊÂÎñ´¦Àí
  ÕýÔÚ°²×°           : mysql                                             [1/2]
  ÕýÔÚ°²×°           : mysql-server                                      [2/2]

ÒÑ°²×°: mysql-server.i386 0:5.0.51a-1.fc9
ÒÀÀµ°²×°: mysql.i386 0:5.0.51a-1.fc9
¹§Ï²Äã!³É¹¦Íê³É£¡
[root@localhost gaoxl]# mysql-server
-bash: mysql-server: command not found
[root@localhost gaoxl]# mysqld
-bash: mysqld: command not found
[root@localhost gaoxl]# mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
[root@localhost gaoxl]# mysqladmin
mysqladmin  Ver 8.41 Distrib 5.0.51a, for redhat-linux-gnu on i386
Copyright (C) 2000-2006 MySQL AB
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL license

Administration program for the mysqld daemon.
Usage: mysqladmin [OPTIONS] command command....
  -c, --count=#       Number of iterations to make. This works with -i
                      (--sleep) only.
  -#, --debug[=name]  Output debug log. Often this is 'd:t:o,filename'.
  -f, --force         Don't ask for confirmation on drop database; with
                      multiple commands, continue even if an error occurs.
  -C, --compress      Use compression in server/client protocol.
  --character-sets-dir=name
                      Directory where character sets are.
  --default-character-set=name
                      Set the default character set.
  -?, --help          Display this help and exit.
  -h, --host=name     Connect to host.
  -p, --password[=name]
                      Password to use when connecting to server. If password is
                      not given it's asked from the tty.
  -P, --port=#        Port number to use for connection.
  --protocol=name     The protocol of connection (tcp,socket,pipe,memory).
  -r, --relative      Show difference between current and previous values when
                      used with -i. Currently works only with extended-status.
  -O, --set-variable=name
                      Change the value of a variable. Please note that this
                      option is deprecated; you can set variables directly with
                      --variable-name=value.
  -s, --silent        Silently exit if one can't connect to server.
  -S, --socket=name   Socket file to use for connection.
  -i, --sleep=#       Execute commands again and again with a sleep between.
  --ssl               Enable SSL for connection (automatically enabled with
                      other flags). Disable with --skip-ssl.
  --ssl-ca=name       CA file in PEM format (check OpenSSL docs, implies
                      --ssl).
  --ssl-capath=name   CA directory (check OpenSSL docs, implies --ssl).
  --ssl-cert=name     X509 cert in PEM format (implies --ssl).
  --ssl-cipher=name   SSL cipher to use (implies --ssl).
  --ssl-key=name      X509 key in PEM format (implies --ssl).
  --ssl-verify-server-cert
                      Verify server's "Common Name" in its cert against
                      hostname used when connecting. This option is disabled by
                      default.
  -u, --user=name     User for login if not current user.
  -v, --verbose       Write more information.
  -V, --version       Output version information and exit.
  -E, --vertical      Print output vertically. Is similar to --relative, but
                      prints output vertically.
  -w, --wait[=#]      Wait and retry if connection is down.
  --connect_timeout=#
  --shutdown_timeout=#

Variables (--variable-name=value)
and boolean options {FALSE|TRUE}  Value (after reading options)
--------------------------------- -----------------------------
count                             0
force                             FALSE
compress                          FALSE
character-sets-dir                (No default value)
default-character-set             (No default value)
host                              (No default value)
port                              0
relative                          FALSE
socket                            (No default value)
sleep                             0
ssl                               FALSE
ssl-ca                            (No default value)
ssl-capath                        (No default value)
ssl-cert                          (No default value)
ssl-cipher                        (No default value)
ssl-key                           (No default value)
ssl-verify-server-cert            FALSE
user                              (No default value)
verbose                           FALSE
vertical                          FALSE
connect_timeout                   43200
shutdown_timeout                  3600

Default options are read from the following files in the given order:
/etc/my.cnf ~/.my.cnf /etc/my.cnf
The following groups are read: mysqladmin client
The following options may be given as the first argument:
--print-defaults        Print the program argument list and exit
--no-defaults           Don't read default options from any options file
--defaults-file=#       Only read default options from the given file #
--defaults-extra-file=# Read this file after the global files are read

Where command is a one or more of: (Commands may be shortened)
  create databasename   Create a new database
  debug                 Instruct server to write debug information to log
  drop databasename     Delete a database and all its tables
  extended-status       Gives an extended status message from the server
  flush-hosts           Flush all cached hosts
  flush-logs            Flush all logs
  flush-status          Clear status variables
  flush-tables          Flush all tables
  flush-threads         Flush the thread cache
  flush-privileges      Reload grant tables (same as reload)
  kill id,id,...        Kill mysql threads
  password new-password Change old password to new-password, MySQL 4.1 hashing.
  old-password new-password Change old password to new-password in old format.

  ping                  Check if mysqld is alive
  processlist           Show list of active threads in server
  reload                Reload grant tables
  refresh               Flush all tables and close and open logfiles
  shutdown              Take server down
  status                Gives a short status message from the server
  start-slave           Start slave
  stop-slave            Stop slave
  variables             Prints variables available
  version               Get version info from server
[root@localhost gaoxl]# mysqladmin start
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' exists!
[root@localhost gaoxl]# mysqld
-bash: mysqld: command not found
[root@localhost gaoxl]# mysql -u root -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
[root@localhost gaoxl]#
[root@localhost gaoxl]# service mysqld start
³õʼ»¯ MySQL Êý¾Ý¿â£º Installing MySQL system tables...
ERROR: 1062  Duplicate entry 'localhost-' for key 1
081116 11:52:03 [ERROR] Aborting

081116 11:52:03 [Note] /usr/libexec/mysqld: Shutdown complete

Installation of system tables failed!

Examine the logs in /var/lib/mysql for more information.
You can try to start the mysqld daemon with:
/usr/libexec/mysqld --skip-grant &
and use the command line tool
/usr/bin/mysql to connect to the mysql
database and look at the grant tables:

shell> /usr/bin/mysql -u root mysql
mysql> show tables

Try 'mysqld --help' if you have problems with paths. Using --log
gives you a log in /var/lib/mysql that may be helpful.

The latest information about MySQL is available on the web at
http://www.mysql.com
Please consult the MySQL manual section: 'Problems running mysql_install_db',
and the manual section that describes problems on your OS.
Another information source is the MySQL email archive.
Please check all of the above before mailing us!
And if you do mail us, you MUST use the /usr/bin/mysqlbug script!
[ʧ°Ü]

[root@localhost gaoxl]# cd /var/lib/mysql

[root@localhost mysql]# ls -l
×Ü¼Æ 8
drwx------ 2 mysql mysql 4096 11-16 11:52 mysql
drwx------ 2 mysql mysql 4096 11-16 11:52 test

[root@localhost mysql]# cd mysql

[root@localhost mysql]# ls
columns_priv.frm   help_relation.MYI  time_zone_leap_second.frm
columns_priv.MYD   help_topic.frm     time_zone_leap_second.MYD
columns_priv.MYI   help_topic.MYD     time_zone_leap_second.MYI
db.frm             help_topic.MYI     time_zone.MYD
db.MYD             host.frm           time_zone.MYI
db.MYI             host.MYD           time_zone_name.frm
func.frm           host.MYI           time_zone_name.MYD
func.MYD           proc.frm           time_zone_name.MYI
func.MYI           proc.MYD           time_zone_transition.frm
help_category.frm  proc.MYI           time_zone_transition.MYD
help_category.MYD  procs_priv.frm     time_zone_transition.MYI
help_category.MYI  procs_priv.MYD     time_zone_transition_type.frm
help_keyword.frm   procs_priv.MYI     time_zone_transition_type.MYD
help_keyword.MYD   tables_priv.frm    time_zone_transition_type.MYI
help_keyword.MYI   tables_priv.MYD    user.frm
help_relation.frm  tables_priv.MYI    user.MYD
help_relation.MYD  time_zone.frm      user.MYI

[root@localhost mysql]# /usr/libexec/mysqld --skip-grant &
[1] 18540
[root@localhost mysql]# InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
081116 11:54:57  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
081116 11:54:57  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
081116 11:54:57  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
081116 11:54:58  InnoDB: Started; log sequence number 0 0
081116 11:54:58 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.51a'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution

[root@localhost mysql]# mysql
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.0.51a Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show tables
    -> ;
ERROR 1046 (3D000): No database selected
mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| test               |
+--------------------+
3 rows in set (0.02 sec)

mysql> use mysql
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> show tables
    -> ;
+---------------------------+
| Tables_in_mysql           |
+---------------------------+
| columns_priv              |
| db                        |
| func                      |
| help_category             |
| help_keyword              |
| help_relation             |
| help_topic                |
| host                      |
| proc                      |
| procs_priv                |
| tables_priv               |
| time_zone                 |
| time_zone_leap_second     |
| time_zone_name            |
| time_zone_transition      |
| time_zone_transition_type |
| user                      |
+---------------------------+
17 rows in set (0.00 sec)

mysql>

Network Working Group                                         M. Lottor
Request For Comments:  1033                           SRI International
                                                          November 1987

                 DOMAIN ADMINISTRATORS OPERATIONS GUIDE

STATUS OF THIS MEMO

   This RFC provides guidelines for domain administrators in operating a
   domain server and maintaining their portion of the hierarchical
   database.  Familiarity with the domain system is assumed.
   Distribution of this memo is unlimited.

ACKNOWLEDGMENTS

   This memo is a formatted collection of notes and excerpts from the
   references listed at the end of this document.  Of particular mention
   are Paul Mockapetris and Kevin Dunlap.

INTRODUCTION

   A domain server requires a few files to get started.  It will
   normally have some number of boot/startup files (also known as the
   "safety belt" files).  One section will contain a list of possible
   root servers that the server will use to find the up-to-date list of
   root servers.  Another section will list the zone files to be loaded
   into the server for your local domain information.  A zone file
   typically contains all the data for a particular domain.  This guide
   describes the data formats that can be used in zone files and
   suggested parameters to use for certain fields.  If you are
   attempting to do anything advanced or tricky, consult the appropriate
   domain RFC's for more details.

   Note:  Each implementation of domain software may require different
   files.  Zone files are standardized but some servers may require
   other startup files.  See the appropriate documentation that comes
   with your software.  See the appendix for some specific examples.

ZONES

   A zone defines the contents of a contiguous section of the domain
   space, usually bounded by administrative boundaries.  There will
   typically be a separate data file for each zone.  The data contained
   in a zone file is composed of entries called Resource Records (RRs).

   You may only put data in your domain server that you are
   authoritative for.  You must not add entries for domains other than
   your own (except for the special case of "glue records").

   A domain server will probably read a file on start-up that lists the
   zones it should load into its database.  The format of this file is
   not standardized and is different for most domain server
   implementations.  For each zone it will normally contain the domain
   name of the zone and the file name that contains the data to load for
   the zone.

ROOT SERVERS

   A resolver will need to find the root servers when it first starts.
   When the resolver boots, it will typically read a list of possible
   root servers from a file.

   The resolver will cycle through the list trying to contact each one.
   When it finds a root server, it will ask it for the current list of
   root servers.  It will then discard the list of root servers it read
   from the data file and replace it with the current list it received.

   Root servers will not change very often.  You can get the names of
   current root servers from the NIC.

   FTP the file NETINFO:ROOT-SERVERS.TXT or send a mail request to
   NIC@SRI-NIC.ARPA.

   As of this date (June 1987) they are:

           SRI-NIC.ARPA       10.0.0.51    26.0.0.73
           C.ISI.EDU          10.0.0.52
           BRL-AOS.ARPA       192.5.25.82  192.5.22.82   128.20.1.2
           A.ISI.EDU          26.3.0.103

RESOURCE RECORDS

   Records in the zone data files are called resource records (RRs).
   They are specified in RFC-883 and RFC-973.  An RR has a standard
   format as shown:

           <name>   [<ttl>]   [<class>]   <type>   <data>

   The record is divided into fields which are separated by white space.

      <name>

         The name field defines what domain name applies to the given

         RR.  In some cases the name field can be left blank and it will
         default to the name field of the previous RR.

      <ttl>

         TTL stands for Time To Live.  It specifies how long a domain
         resolver should cache the RR before it throws it out and asks a
         domain server again.  See the section on TTL's.  If you leave
         the TTL field blank it will default to the minimum time
         specified in the SOA record (described later).

      <class>

         The class field specifies the protocol group.  If left blank it
         will default to the last class specified.

      <type>

         The type field specifies what type of data is in the RR.  See
         the section on types.

      <data>

         The data field is defined differently for each type and class
         of data.  Popular RR data formats are described later.

   The domain system does not guarantee to preserve the order of
   resource records.  Listing RRs (such as multiple address records) in
   a certain order does not guarantee they will be used in that order.

   Case is preserved in names and data fields when loaded into the name
   server.  All comparisons and lookups in the name server are case
   insensitive.

   Parenthesis ("(",")") are used to group data that crosses a line
   boundary.

   A semicolon (";") starts a comment; the remainder of the line is
   ignored.

   The asterisk ("*") is used for wildcarding.

   The at-sign ("@") denotes the current default domain name.

NAMES

   A domain name is a sequence of labels separated by dots.

   Domain names in the zone files can be one of two types, either
   absolute or relative.  An absolute name is the fully qualified domain
   name and is terminated with a period.  A relative name does not
   terminate with a period, and the current default domain is appended
   to it.  The default domain is usually the name of the domain that was
   specified in the boot file that loads each zone.

   The domain system allows a label to contain any 8-bit character.
   Although the domain system has no restrictions, other protocols such
   as SMTP do have name restrictions.  Because of other protocol
   restrictions, only the following characters are recommended for use
   in a host name (besides the dot separator):

           "A-Z", "a-z", "0-9", dash and underscore

TTL's  (Time To Live)

   It is important that TTLs are set to appropriate values.  The TTL is
   the time (in seconds) that a resolver will use the data it got from
   your server before it asks your server again.  If you set the value
   too low, your server will get loaded down with lots of repeat
   requests.  If you set it too high, then information you change will
   not get distributed in a reasonable amount of time.  If you leave the
   TTL field blank, it will default to what is specified in the SOA
   record for the zone.

   Most host information does not change much over long time periods.  A
   good way to set up your TTLs would be to set them at a high value,
   and then lower the value if you know a change will be coming soon.
   You might set most TTLs to anywhere between a day (86400) and a week
   (604800).  Then, if you know some data will be changing in the near
   future, set the TTL for that RR down to a lower value (an hour to a
   day) until the change takes place, and then put it back up to its
   previous value.

   Also, all RRs with the same name, class, and type should have the
   same TTL value.

CLASSES

   The domain system was designed to be protocol independent.  The class
   field is used to identify the protocol group that each RR is in.

   The class of interest to people using TCP/IP software is the class

   "Internet".  Its standard designation is "IN".

   A zone file should only contain RRs of the same class.

TYPES

   There are many defined RR types.  For a complete list, see the domain
   specification RFCs.  Here is a list of current commonly used types.
   The data for each type is described in the data section.

                Designation                Description
              ==========================================
               SOA                 Start Of Authority
               NS                  Name Server

               A                   Internet Address
               CNAME               Canonical Name (nickname pointer)
               HINFO               Host Information
               WKS                 Well Known Services

               MX                  Mail Exchanger

               PTR                 Pointer

SOA  (Start Of Authority)

           <name>  [<ttl>]  [<class>]  SOA  <origin>  <person>  (
                           <serial>
                           <refresh>
                           <retry>
                           <expire>
                           <minimum> )

   The Start Of Authority record designates the start of a zone.  The
   zone ends at the next SOA record.

   <name> is the name of the zone.

   <origin> is the name of the host on which the master zone file
   resides.

   <person> is a mailbox for the person responsible for the zone.  It is
   formatted like a mailing address but the at-sign that normally
   separates the user from the host name is replaced with a dot.

   <serial> is the version number of the zone file.  It should be
   incremented anytime a change is made to data in the zone.

   <refresh> is how long, in seconds, a secondary name server is to
   check with the primary name server to see if an update is needed.  A
   good value here would be one hour (3600).

   <retry> is how long, in seconds, a secondary name server is to retry
   after a failure to check for a refresh.  A good value here would be
   10 minutes (600).

   <expire> is the upper limit, in seconds, that a secondary name server
   is to use the data before it expires for lack of getting a refresh.
   You want this to be rather large, and a nice value is 3600000, about
   42 days.

   <minimum> is the minimum number of seconds to be used for TTL values
   in RRs.  A minimum of at least a day is a good value here (86400).

   There should only be one SOA record per zone.  A sample SOA record
   would look something like:

           @   IN   SOA   SRI-NIC.ARPA.   HOSTMASTER.SRI-NIC.ARPA. (
                           45         ;serial
                           3600       ;refresh
                           600        ;retry
                           3600000    ;expire
                           86400 )    ;minimum

NS  (Name Server)

           <domain>   [<ttl>] [<class>]   NS   <server>

   The NS record lists the name of a machine that provides domain
   service for a particular domain.  The name associated with the RR is
   the domain name and the data portion is the name of a host that
   provides the service.  If machines SRI-NIC.ARPA and C.ISI.EDU provide
   name lookup service for the domain COM then the following entries
   would be used:

           COM.    NS      SRI-NIC.ARPA.
                   NS      C.ISI.EDU.

   Note that the machines providing name service do not have to live in
   the named domain.  There should be one NS record for each server for
   a domain.  Also note that the name "COM" defaults for the second NS
   record.

   NS records for a domain exist in both the zone that delegates the
   domain, and in the domain itself.

GLUE RECORDS

   If the name server host for a particular domain is itself inside the
   domain, then a 'glue' record will be needed.  A glue record is an A
   (address) RR that specifies the address of the server.  Glue records
   are only needed in the server delegating the domain, not in the
   domain itself.  If for example the name server for domain SRI.COM was
   KL.SRI.COM, then the NS record would look like this, but you will
   also need to have the following A record.

           SRI.COM.  NS
           KL.SRI.COM.  KL.SRI.COM.  A 10.1.0.2.

A  (Address)

           <host>   [<ttl>] [<class>]   A   <address>

   The data for an A record is an internet address in dotted decimal
   form.  A sample A record might look like:

           SRI-NIC.ARPA.           A       10.0.0.51

   There should be one A record for each address of a host.

CNAME ( Canonical Name)

           <nickname>   [<ttl>] [<class>]   CNAME   <host>

   The CNAME record is used for nicknames.  The name associated with the
   RR is the nickname.  The data portion is the official name.  For
   example, a machine named SRI-NIC.ARPA may want to have the nickname
   NIC.ARPA.  In that case, the following RR would be used:

           NIC.ARPA.       CNAME   SRI-NIC.ARPA.

   There must not be any other RRs associated with a nickname of the
   same class.

   Nicknames are also useful when a host changes it's name.  In that
   case, it is usually a good idea to have a CNAME pointer so that
   people still using the old name will get to the right place.

HINFO (Host Info)

           <host>   [<ttl>] [<class>]   HINFO   <hardware>   <software>

   The HINFO record gives information about a particular host.  The data
   is two strings separated by whitespace.  The first string is a
   hardware description and the second is software.  The hardware is
   usually a manufacturer name followed by a dash and model designation.
   The software string is usually the name of the operating system.

   Official HINFO types can be found in the latest Assigned Numbers RFC,
   the latest of which is RFC-1010.  The Hardware type is called the
   Machine name and the Software type is called the System name.

   Some sample HINFO records:

           SRI-NIC.ARPA.           HINFO   DEC-2060 TOPS20
           UCBARPA.Berkeley.EDU.   HINFO   VAX-11/780 UNIX

WKS (Well Known Services)

           <host> [<ttl>] [<class>] WKS <address> <protocol> <services>

   The WKS record is used to list Well Known Services a host provides.
   WKS's are defined to be services on port numbers below 256.  The WKS
   record lists what services are available at a certain address using a
   certain protocol.  The common protocols are TCP or UDP.  A sample WKS
   record for a host offering the same services on all address would
   look like:

   Official protocol names can be found in the latest Assigned Numbers
   RFC, the latest of which is RFC-1010.

           SRI-NIC.ARPA.   WKS  10.0.0.51  TCP  TELNET FTP SMTP
                           WKS  10.0.0.51  UDP  TIME
                           WKS  26.0.0.73  TCP  TELNET FTP SMTP
                           WKS  26.0.0.73  UDP  TIME

MX (Mail Exchanger)  (See RFC-974 for more details.)

           <name>   [<ttl>] [<class>]   MX   <preference>   <host>

   MX records specify where mail for a domain name should be delivered.
   There may be multiple MX records for a particular name.  The
   preference value specifies the order a mailer should try multiple MX
   records when delivering mail.  Zero is the highest preference.
   Multiple records for the same name may have the same preference.

   A host BAR.FOO.COM may want its mail to be delivered to the host
   PO.FOO.COM and would then use the MX record:

           BAR.FOO.COM.    MX      10      PO.FOO.COM.

   A host BAZ.FOO.COM may want its mail to be delivered to one of three
   different machines, in the following order:

           BAZ.FOO.COM.    MX      10      PO1.FOO.COM.
                           MX      20      PO2.FOO.COM.
                           MX      30      PO3.FOO.COM.

   An entire domain of hosts not connected to the Internet may want
   their mail to go through a mail gateway that knows how to deliver
   mail to them.  If they would like mail addressed to any host in the
   domain FOO.COM to go through the mail gateway they might use:

           FOO.COM.        MX       10     RELAY.CS.NET.
           *.FOO.COM.      MX       20     RELAY.CS.NET.

   Note that you can specify a wildcard in the MX record to match on
   anything in FOO.COM, but that it won't match a plain FOO.COM.

IN-ADDR.ARPA

   The structure of names in the domain system is set up in a
   hierarchical way such that the address of a name can be found by
   tracing down the domain tree contacting a server for each label of
   the name.  Because of this 'indexing' based on name, there is no easy
   way to translate a host address back into its host name.

   In order to do the reverse translation easily, a domain was created
   that uses hosts' addresses as part of a name that then points to the
   data for that host.  In this way, there is now an 'index' to hosts'
   RRs based on their address.  This address mapping domain is called
   IN-ADDR.ARPA.  Within that domain are subdomains for each network,
   based on network number.  Also, for consistency and natural
   groupings, the 4 octets of a host number are reversed.

   For example, the ARPANET is net 10.  That means there is a domain
   called 10.IN-ADDR.ARPA.  Within this domain there is a PTR RR at
   51.0.0.10.IN-ADDR that points to the RRs for the host SRI-NIC.ARPA
   (who's address is 10.0.0.51).  Since the NIC is also on the MILNET
   (Net 26, address 26.0.0.73), there is also a PTR RR at 73.0.0.26.IN-
   ADDR.ARPA that points to the same RR's for SRI-NIC.ARPA.  The format
   of these special pointers is defined below along with the examples
   for the NIC.

PTR

           <special-name>   [<ttl>] [<class>]   PTR   <name>

   The PTR record is used to let special names point to some other
   location in the domain tree.  They are mainly used in the IN-
   ADDR.ARPA records for translation of addresses to names.  PTR's
   should use official names and not aliases.

   For example, host SRI-NIC.ARPA with addresses 10.0.0.51 and 26.0.0.73
   would have the following records in the respective zone files for net
   10 and net 26:

           51.0.0.10.IN-ADDR.ARPA.  PTR   SRI-NIC.ARPA.
           73.0.0.26.IN-ADDR.ARPA.  PTR   SRI-NIC.ARPA.

GATEWAY PTR's

   The IN-ADDR tree is also used to locate gateways on a particular
   network.  Gateways have the same kind of PTR RRs as hosts (as above)
   but in addition they have other PTRs used to locate them by network
   number alone.  These records have only 1, 2, or 3 octets as part of
   the name depending on whether they are class A, B, or C networks,
   respectively.

   Lets take the SRI-CSL gateway for example.  It connects 3 different
   networks, one class A, one class B and one class C.  It will have the
   standard RR's for a host in the CSL.SRI.COM zone:

           GW.CSL.SRI.COM.    A    10.2.0.2
                              A    128.18.1.1
                              A    192.12.33.2

   Also, in 3 different zones (one for each network), it will have one
   of the following number to name translation pointers:

           2.0.2.10.IN-ADDR.ARPA.      PTR   GW.CSL.SRI.COM.
           1.1.18.128.IN-ADDR.ARPA.    PTR   GW.CSL.SRI.COM.
           1.33.12.192.IN-ADDR.ARPA.   PTR   GW.CSL.SRI.COM.

   In addition, in each of the same 3 zones will be one of the following
   gateway location pointers:

           10.IN-ADDR.ARPA.            PTR   GW.CSL.SRI.COM.
           18.128.IN-ADDR.ARPA.        PTR   GW.CSL.SRI.COM.
           33.12.192.IN-ADDR.ARPA.     PTR   GW.CSL.SRI.COM.

INSTRUCTIONS

   Adding a subdomain.

      To add a new subdomain to your domain:

         Setup the other domain server and/or the new zone file.

         Add an NS record for each server of the new domain to the zone
         file of the parent domain.

         Add any necessary glue RRs.

   Adding a host.

      To add a new host to your zone files:

         Edit the appropriate zone file for the domain the host is in.

         Add an entry for each address of the host.

         Optionally add CNAME, HINFO, WKS, and MX records.

         Add the reverse IN-ADDR entry for each host address in the
         appropriate zone files for each network the host in on.

   Deleting a host.

      To delete a host from the zone files:

         Remove all the hosts' resource records from the zone file of
         the domain the host is in.

         Remove all the hosts' PTR records from the IN-ADDR zone files
         for each network the host was on.

   Adding gateways.

         Follow instructions for adding a host.

         Add the gateway location PTR records for each network the
         gateway is on.

   Deleting gateways.

         Follow instructions for deleting a host.

         Also delete the gateway location PTR records for each network

         the gateway was on.

COMPLAINTS

   These are the suggested steps you should take if you are having
   problems that you believe are caused by someone else's name server:

   1.  Complain privately to the responsible person for the domain.  You
   can find their mailing address in the SOA record for the domain.

   2.  Complain publicly to the responsible person for the domain.

   3.  Ask the NIC for the administrative person responsible for the
   domain.  Complain.  You can also find domain contacts on the NIC in
   the file NETINFO:DOMAIN-CONTACTS.TXT

   4.  Complain to the parent domain authorities.

   5.  Ask the parent authorities to excommunicate the domain.

EXAMPLE DOMAIN SERVER DATABASE FILES

   The following examples show how zone files are set up for a typical
   organization.  SRI will be used as the example organization.  SRI has
   decided to divided their domain SRI.COM into a few subdomains, one
   for each group that wants one.  The subdomains are CSL and ISTC.

   Note the following interesting items:

      There are both hosts and domains under SRI.COM.

      CSL.SRI.COM is both a domain name and a host name.

      All the domains are serviced by the same pair of domain servers.

      All hosts at SRI are on net 128.18 except hosts in the CSL domain
      which are on net 192.12.33.  Note that a domain does not have to
      correspond to a physical network.

      The examples do not necessarily correspond to actual data in use
      by the SRI domain.

                       SRI Domain Organization

                               +-------+
                               |  COM  |
                               +-------+
                                   |
                               +-------+
                               |  SRI  |
                               +-------+
                                   |
                        +----------++-----------+
                        |           |           |
                    +-------+    +------+   +-------+
                    |  CSL  |    | ISTC |   | Hosts |
                    +-------+    +------+   +-------+
                        |           |
                    +-------+    +-------+
                    | Hosts |    | Hosts |
                    +-------+    +-------+

   [File "CONFIG.CMD".  Since bootstrap files are not standardized, this
   file is presented using a pseudo configuration file syntax.]

   load root server list             from file ROOT.SERVERS
   load zone SRI.COM.                from file SRI.ZONE
   load zone CSL.SRI.COM.            from file CSL.ZONE
   load zone ISTC.SRI.COM.           from file ISTC.ZONE
   load zone 18.128.IN-ADDR.ARPA.    from file SRINET.ZONE
   load zone 33.12.192.IN-ADDR.ARPA. from file SRI-CSL-NET.ZONE

   [File "ROOT.SERVERS".  Again, the format of this file is not
   standardized.]

   ;list of possible root servers
   SRI-NIC.ARPA       10.0.0.51    26.0.0.73
   C.ISI.EDU          10.0.0.52
   BRL-AOS.ARPA       192.5.25.82  192.5.22.82   128.20.1.2
   A.ISI.EDU          26.3.0.103

   [File "SRI.ZONE"]

   SRI.COM.        IN      SOA     KL.SRI.COM. DLE.STRIPE.SRI.COM. (
                                   870407  ;serial
                                   1800    ;refresh every 30 minutes
                                   600     ;retry every 10 minutes
                                   604800  ;expire after a week
                                   86400   ;default of an hour
                                   )

   SRI.COM.        NS      KL.SRI.COM.
                   NS      STRIPE.SRI.COM.
                   MX      10      KL.SRI.COM.

   ;SRI.COM hosts

   KL              A       10.1.0.2
                   A       128.18.10.6
                   MX      10      KL.SRI.COM.

   STRIPE          A       10.4.0.2
   STRIPE          A       128.18.10.4
                   MX      10      STRIPE.SRI.COM.

   NIC             CNAME   SRI-NIC.ARPA.

   Blackjack       A       128.18.2.1
                   HINFO   VAX-11/780      UNIX
                   WKS     128.18.2.1      TCP TELNET FTP

   CSL             A       192.12.33.2
                   HINFO   FOONLY-F4       TOPS20
                   WKS     192.12.33.2     TCP TELNET FTP SMTP FINGER
                   MX      10      CSL.SRI.COM.

   [File "CSL.ZONE"]

   CSL.SRI.COM.    IN      SOA     KL.SRI.COM. DLE.STRIPE.SRI.COM. (
                                   870330  ;serial
                                   1800    ;refresh every 30 minutes
                                   600     ;retry every 10 minutes
                                   604800  ;expire after a week
                                   86400   ;default of a day
                                   )

   CSL.SRI.COM.    NS              KL.SRI.COM.
                   NS              STRIPE.SRI.COM.
                   A               192.12.33.2

   ;CSL.SRI.COM hosts

   A               CNAME   CSL.SRI.COM.
   B               A       192.12.33.3
                   HINFO   FOONLY-F4       TOPS20
                   WKS     192.12.33.3     TCP TELNET FTP SMTP
   GW              A       10.2.0.2
                   A       192.12.33.1
                   A       128.18.1.1
                   HINFO   PDP-11/23       MOS
   SMELLY          A       192.12.33.4
                   HINFO   IMAGEN          IMAGEN
   SQUIRREL        A       192.12.33.5
                   HINFO   XEROX-1100      INTERLISP
   VENUS           A       192.12.33.7
                   HINFO   SYMBOLICS-3600  LISPM
   HELIUM          A       192.12.33.30
                   HINFO   SUN-3/160       UNIX
   ARGON           A       192.12.33.31
                   HINFO   SUN-3/75        UNIX
   RADON           A       192.12.33.32
                   HINFO   SUN-3/75        UNIX

   [File "ISTC.ZONE"]

   ISTC.SRI.COM.   IN  SOA     KL.SRI.COM. roemers.JOYCE.ISTC.SRI.COM. (
                               870406      ;serial
                               1800        ;refresh every 30 minutes
                               600         ;retry every 10 minutes
                               604800      ;expire after a week
                               86400       ;default of a day
                               )

   ISTC.SRI.COM.   NS              KL.SRI.COM.
                   NS              STRIPE.SRI.COM.
                   MX              10      SPAM.ISTC.SRI.COM.

   ; ISTC hosts

   joyce           A       128.18.4.2
                   HINFO   VAX-11/750 UNIX
   bozo            A       128.18.0.6
                   HINFO   SUN UNIX
   sundae          A       128.18.0.11
                   HINFO   SUN UNIX
   tsca            A       128.18.0.201
                   A       10.3.0.2
                   HINFO   VAX-11/750 UNIX
                   MX      10  TSCA.ISTC.SRI.COM.
   tsc             CNAME   tsca
   prmh            A       128.18.0.203
                   A       10.2.0.51
                   HINFO   PDP-11/44 UNIX
   spam            A       128.18.4.3
                   A       10.2.0.107
                   HINFO   VAX-11/780 UNIX
                   MX      10  SPAM.ISTC.SRI.COM.

   [File "SRINET.ZONE"]

   18.128.IN-ADDR.ARPA.    IN  SOA  KL.SRI.COM  DLE.STRIPE.SRI.COM. (
                               870406  ;serial
                               1800    ;refresh every 30 minutes
                               600     ;retry every 10 minutes
                               604800  ;expire after a week
                               86400   ;default of a day
                               )

   18.128.IN-ADDR.ARPA.    NS      KL.SRI.COM.
                           NS      STRIPE.SRI.COM.
                           PTR     GW.CSL.SRI.COM.

   ; SRINET [128.18.0.0] Address Translations

   ; SRI.COM Hosts
   1.2.18.128.IN-ADDR.ARPA.        PTR     Blackjack.SRI.COM.

   ; ISTC.SRI.COM Hosts
   2.4.18.128.IN-ADDR.ARPA.        PTR     joyce.ISTC.SRI.COM.
   6.0.18.128.IN-ADDR.ARPA.        PTR     bozo.ISTC.SRI.COM.
   11.0.18.128.IN-ADDR.ARPA.       PTR     sundae.ISTC.SRI.COM.
   201.0.18.128.IN-ADDR.ARPA.      PTR     tsca.ISTC.SRI.COM.
   203.0.18.128.IN-ADDR.ARPA.      PTR     prmh.ISTC.SRI.COM.
   3.4.18.128.IN-ADDR.ARPA.        PTR     spam.ISTC.SRI.COM.

   ; CSL.SRI.COM Hosts
   1.1.18.128.IN-ADDR.ARPA.        PTR     GW.CSL.SRI.COM.

   [File "SRI-CSL-NET.ZONE"]

   33.12.192.IN-ADDR.ARPA. IN  SOA KL.SRI.COM  DLE.STRIPE.SRI.COM. (
                               870404  ;serial
                               1800    ;refresh every 30 minutes
                               600     ;retry every 10 minutes
                               604800  ;expire after a week
                               86400   ;default of a day
                               )

   33.12.192.IN-ADDR.ARPA. NS      KL.SRI.COM.
                           NS      STRIPE.SRI.COM.
                           PTR     GW.CSL.SRI.COM.

   ; SRI-CSL-NET [192.12.33.0] Address Translations

   ; SRI.COM Hosts
   2.33.12.192.IN-ADDR.ARPA.       PTR     CSL.SRI.COM.

   ; CSL.SRI.COM Hosts
   1.33.12.192.IN-ADDR.ARPA.       PTR     GW.CSL.SRI.COM.
   3.33.12.192.IN-ADDR.ARPA.       PTR     B.CSL.SRI.COM.
   4.33.12.192.IN-ADDR.ARPA.       PTR     SMELLY.CSL.SRI.COM.
   5.33.12.192.IN-ADDR.ARPA.       PTR     SQUIRREL.CSL.SRI.COM.
   7.33.12.192.IN-ADDR.ARPA.       PTR     VENUS.CSL.SRI.COM.
   30.33.12.192.IN-ADDR.ARPA.      PTR     HELIUM.CSL.SRI.COM.
   31.33.12.192.IN-ADDR.ARPA.      PTR     ARGON.CSL.SRI.COM.
   32.33.12.192.IN-ADDR.ARPA.      PTR     RADON.CSL.SRI.COM.

APPENDIX

   BIND (Berkeley Internet Name Domain server) distributed with 4.3 BSD
   UNIX

   This section describes two BIND implementation specific files; the
   boot file and the cache file.  BIND has other options, files, and
   specifications that are not described here.  See the Name Server
   Operations Guide for BIND for details.

   The boot file for BIND is usually called "named.boot".  This
   corresponds to file "CONFIG.CMD" in the example section.

           --------------------------------------------------------
           cache         .                         named.ca
           primary       SRI.COM                   SRI.ZONE
           primary       CSL.SRI.COM               CSL.ZONE
           primary       ISTC.SRI.COM              ISTC.ZONE
           primary       18.128.IN-ADDR.ARPA       SRINET.ZONE
           primary       33.12.192.IN-ADDR.ARPA    SRI-CSL-NET.ZONE
           --------------------------------------------------------

   The cache file for BIND is usually called "named.ca".  This
   corresponds to file "ROOT.SERVERS" in the example section.

           -------------------------------------------------
           ;list of possible root servers
           .       1          IN   NS   SRI-NIC.ARPA.
                                   NS   C.ISI.EDU.
                                   NS   BRL-AOS.ARPA.
                                   NS   C.ISI.EDU.
           ;and their addresses
           SRI-NIC.ARPA.           A    10.0.0.51
                                   A    26.0.0.73
           C.ISI.EDU.              A    10.0.0.52
           BRL-AOS.ARPA.           A    192.5.25.82
                                   A    192.5.22.82
                                   A    128.20.1.2
           A.ISI.EDU.              A    26.3.0.103
           -------------------------------------------------

REFERENCES

   [1]  Dunlap, K., "Name Server Operations Guide for BIND", CSRG,
        Department of Electrical Engineering and Computer Sciences,
        University of California, Berkeley, California.

   [2]  Partridge, C., "Mail Routing and the Domain System", RFC-974,
        CSNET CIC BBN Laboratories, January 1986.

   [3]  Mockapetris, P., "Domains Names - Concepts and Facilities",
        RFC-1034, USC/Information Sciences Institute, November 1987.

   [4]  Mockapetris, P., "Domain Names - Implementations Specification",
        RFC-1035, USC/Information Sciences Institute, November 1987.

Comment on RFC 1033