Nathan Rawling <[EMAIL PROTECTED]> writes: > On 20 Nov 2001, Derek Atkins wrote:
>> MIT uses Hesiod, which is based on DNS. The management is via a >> database that writes out the DNS file. This way users can be migrated >> -- the mail apps look up the POServer in Hesiod to find out which Mail >> Server to contact. > How much code-modification was required to add this support to the > mailreaders? Don't use Hesiod, not for this. Just use CNAMEs. Then you don't have to modify a single line of code. We have a pobox.stanford.edu subdomain, and every single user has a username.pobox.stanford.edu DNS CNAME for their mail server. The zone files are all generated automatically from a database. There's really no reason to use Hesiod rather than CNAMEs unless you have to inform the clients of protocol as well as server. windlord:~> host rra.pobox.stanford.edu rra.pobox.stanford.edu CNAME popserver2.stanford.edu popserver2.stanford.edu A 171.64.14.68 -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
