FUNET servers

### MANY NAMES OF FUNET SERVICES

## ``Beloved Child Has Many Names''

### This proverb is also fitting with FUNET servers

FUNET machines giving services to users have many names. Their "staff" will always be reachable via ``nic.funet.fi'', but otherwise consider using philosophy: ``Name by Function'', thus FTP from ftp.funet.fi.

We have the following public servers:

ARCHIE.FUNET.FI
  telnet, and login: archie, or use archie-clients.
DUA.FUNET.FI
  Public X.500 directory service query interface is on this machine at account ``dua'' (no password required)
FTP.FUNET.FI
  Via Anonymous FTP; HTMLed README gives access also to local search engine
GOPHER.FUNET.FI
  Via Gopher-clients (effectively phased out)
INFO.FUNET.FI
  telnet, and login: info Interactive clients to other services for those who don't yet have their own. Select what service you want to use (www, gopher, ..)
IRC.FUNET.FI
  IRC network server, no direct client access -- use your local server, or ask irc@irc.funet.fi about connecting your local server (Finland only!)
LISTSERV.FUNET.FI
  A global distributed mailinglist service managed by LSoft's LISTSERV. Send your requests to listserv@listserv.funet.fi
NEWS.FUNET.FI / NEWS2.FUNET.FI
  A set of servers used to feed USENET newsgroups to FUNET members.
NIC.FUNET.FI
  Original machine, management staff, main mailer, file-delivering mailserver, and X.500 interface logins: dua, fred
WWW.FUNET.FI
  World Wide Web-hypermedia server. Use WWW clients
WWW-CACHE.FUNET.FI port 8000
  FUNET has a cacheing WWW-server at abovementioned address. Do note that it is limited to FUNET members -- contact webmaster@www.funet.fi for more info
NWI.FUNET.FI
  Nordic Web Index
Mainari.FUNET.FI
  White Pages of selected FUNET member sites
ALEX.FUNET.FI
  Global filesystem for all anonymous ftp sites with caching (experimental)

Not all of them are on separate machines, but which physical machine runs which service is subject to more or less sudden change if we see it necessary. (And get more hardware..) Therefore always try to use names of services instead of machines...

All will be well when you use ``name by function'' assumption, and have a working network address lookup mechanism.