Domain Name System (DNS)
The EECS department maintains the DNS tables for most networks in Soda and Cory halls. The majority of requests for changes to DNS should be made via the online System Registration and Update forms. For unusual DNS requests, contact hostmaster@eecs.
DHCP clients will automatically be provided with the correct addresses for DNS servers.
See also:
Network Information Service (NIS)
The department maintains a large NIS domain, which provides a centralized password database as well as a variety of automounter maps. System administrators can use this infrastructure to control access to machines and filesystems.
See also:
- IDSG NIS Services
- How do I change my shell?
- How do I configure my machine to be part of the department’s NIS domain?
- How do I export my home directory to a machine or group of machines?
- How do I set my NIS password?
- How do I control login access to my machine using NIS?
Dynamic Host Configuration Protocol (DHCP)
Dynamic Host Configuration Protocol allows clients to request an IP address and other related network settings when they start up, rather than being configured with this information statically. This service provides a number of benefits:
- More efficient use of limited IP address space.
- Easier portability of systems from network to network.
- Easier system administration if changes are made to back-end systems (such as DNS servers).
DHCP clients in EECS are identified by the hardware MAC address of their ethernet card. The DHCP server will not assign addresses to hosts which are unknown to it. To notify the DHCP server about your host, you’ll need to register it.
The DHCP server can be configured to assign a fixed hostname to a particuliar client, if that client needs to be consistently resolvable on the network. We encourage all clients to use DHCP on networks where DHCP is available.
Directory Services
The deparmental directory server is a unix LDAP (Lightweight Directory Access Protocol) server. All IRIS Account holders have records in the LDAP server, which contain the standard office and telephone contact information, as well as username and group information. Applications are increasingly being integrated with LDAP directory services, such as: Jabber, our Sympa mailing list server, and the Repo service. We expect to see other services, such as NIS or Windows authentication, integrated with the departmental LDAP server in the future as we move towards centralized single sign-on.
All IRIS account holders can create and manage their own LDAP groups with the Regroup application. See this IRIS News article for details.
As of January 2014, LDAP no longer contains a separate password. All password authentication is handed off to Windows Active Directory. See this IRIS News item for details.
See also:
- How do I get an EECS account?
- How do I set my LDAP/e-mail password?
- Regroup: Create and Manage LDAP Groups
File Transfer Protocol (FTP)
ftp.eecs.berkeley.edu is a world-accessible, read-only, anonymous FTParchive. This ftp service is maintained primarily for historical purposes, distributing software and data from pre-http days. At this time, we strongly encourage the use of personal web pages, Project Web Sites, or the EECS Technical Memorandum Seriesto publish data. There is no advantage of ftp over http at this time.
However, if you are maintaining one of these historical archives, members of the department can modify the contents of directories over which they have the appropriate permissions, by doing the following:
- Make a secure login to ftp-write.eecs.berkeley.edu (using either ssh or kerberized telnet).
- The root filesystem for ftp.eecs is found at /project/eecs/ftp, so copy your files to /project/eecs/ftp/[path-to-your-directory-on-ftp.eecs].
If you would like space on ftp.eecs.berkeley.edu, please contact the IRIS Helpdesk. Note that this service is limited to members of the EECS department.
See also:
Windows Internet Name Service (WINS)
WINS service is a simple name server that dynamically maps NetBIOS names (used by Windows machines) to IP addresses.
See also:
Network Time Protocol (NTP)
Network Time Protocol allows hosts to synchronize their clocks with a trusted time source, over the network.
If for any reason a UNIX system needs to run its own NTP service, see the SWWtemplates for Cory Hall and Soda Hall.
Windows clients in the EECS domain are automatically synchronized.
See also: