Name Server Operations Guide for BIND Release 4.9.5 : Files : About Hesiod, and HS-class Resource Records
Previous: About ``secure zones''
Next: Sample Files

6.8. About Hesiod, and HS-class Resource Records

Hesiod, developed by MIT Project Athena, is an information service built upon BIND. Its intent is similar to that of Sun's NIS: to furnish information about users, groups, network-accessible file systems, printcaps, and mail service throughout an installation. Aside from its use of BIND rather than separate server code another important difference between Hesiod and NIS is that Hesiod is not intended to deal with passwords and authentication, but only with data that are not security sensitive. Hesiod servers can be implemented by adding resource records to BIND servers; or they can be implemented as separate servers separately administered.

To learn about and obtain Hesiod make an anonymous FTP connection to host ATHENA-DIST.MIT.EDU and retrieve the compressed tar file /pub/ATHENA/hesiod.tar.Z. You will not need the named and resolver library portions of the distribution because their functionality has already been integrated into BIND as of 4.9. To learn how Hesiod functions as part of the Athena computing environment obtain the paper /pub/ATHENA/usenix/athena-changes.PS from the above FTP server host. There is also a tar file of sample Hesiod resource files.

Whether one should use Hesiod class is open to question, since the same services can probably be provided with class IN, type TXT and type CNAME records. In either case, the code and documents for Hesiod will suggest how to set up and use the service.

Note that while BIND includes support for HS-class queries, the zone transfer logic for non-IN-class zones is still experimental.


Name Server Operations Guide for BIND Release 4.9.5 : Files : About Hesiod, and HS-class Resource Records
Previous: About ``secure zones''
Next: Sample Files