svcadm(1M)을 검색하려면 섹션에서 1M 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
domainname(8)
System Administration Commands domainname(8)
NAME
domainname - set or display name of the current domain
SYNOPSIS
domainname [name-of-domain]
DESCRIPTION
Without an argument, domainname displays the name of the current domain
name used in RPC exchanges, usually referred to as the NIS domain name.
This name typically encompasses a group of hosts or passwd entries
under the same administration. The domainname command is used by vari‐
ous components of Solaris to resolve names for entries such as are
found in passwd, hosts and aliases. By default, naming services such as
NIS use domainname to resolve names.
With the "Name Service Management" rbac(7) profile, you can permanently
set the name of the domain with the following command:
% domainname nisdomain.example.com
If not yet enabled, the nis/domain service is enabled.
A user with the {PRIV_SYS_ADMIN} privilege can temporarily set the
domain name using:
# domainname -t nisdomain.example.com
but it will reset to the default when the system next boots.
The domain name for various naming services can also be set by other
means. DNS ignores the domain name set by domainname and LDAP uses it
as a last resort.
The sendmail(8) daemon, as shipped with Solaris, and the sendmail
implementation provided by sendmail.org (formerly referred to as
"Berkeley 8.x sendmail") both attempt to determine a local host's fully
qualified host name at startup and both pursue follow-up actions if the
initial search fails. It is in these follow-up actions that the two
implementations differ.
Both implementations use a standard Solaris or UNIX system call to
determine its fully qualified host name at startup, following the name
service priorities specified in nsswitch.conf(5). To this point, the
Solaris and sendmail.org versions behave identically.
If the request for a fully qualified host name fails, the sendmail.org
sendmail sleeps for 60 seconds, tries again, and, upon continuing fail‐
ure, resorts to a short name. The Solaris version of sendmail makes the
same initial request, but then, following initial failure, calls
domainname. If successful, the sleep is avoided.
On a Solaris machine, if you run the sendmail.org version of sendmail,
you get the startup behavior (omitting the domainname call) described
above. If you run the Solaris sendmail, the domainname call is made if
needed.
If the Solaris sendmail cannot determine the fully qualified host name,
use check-hostname(8) as a troubleshooting aid. This script can offer
guidance as to appropriate corrective action.
FILES
o /etc/defaultdomain
o /etc/nsswitch.conf
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE TYPEAT‐
TRIBUTE VALUE _ Availabilitysystem/core-os
SEE ALSO
svcs(1), aliases(5), defaultdomain(5), hosts(5), nsswitch.conf(5),
passwd(5), attributes(7), rbac(7), privileges(7), smf(7), check-host‐
name(8), hostconfig(8), named(8), sendmail(8), svcadm(8), svccfg(8),
ypinit(8)
NOTES
The domainname service is managed by the service management facility,
smf(7), under the service identifier:
svc:/system/identity:domain
Administrative actions on this service, such as enabling, disabling, or
requesting restart, can be performed using svcadm(8). The service's
status can be queried using the svcs(1) command.
Oracle Solaris 11.4 3 Nov 2021 domainname(8)