[136] in Hesiod
Re: Unable to get Hesiod compiled under NeXT NextStep3.0
daemon@ATHENA.MIT.EDU (Haisong Cai)
Mon May 3 10:09:37 1993
To: mar@Athena.MIT.EDU
Cc: hesiod@Athena.MIT.EDU
Date: Mon, 03 May 1993 10:05:59 -0400
From: "Haisong Cai" <haisong@eng.umd.edu>
In message "Re: Unable to get Hesiod compiled under NeXT NextStep3.0 "
Mark Rosenstein wrote:
>Is that the hesiod library itself, or the modified named that you were
>trying to get running on a Next? The library should be brought up to
>date, and I would gladly accept patches. The nameserver that's
>included there is ancient, and probably should no longer be
>distributed. The bind folks are beta testing bind 4.9 now, and I
>think it already has built-in support for hesiod. Has anyone checked
>this out?
> -Mark
---------
It's Hesiod library itself. All I want is to be able to let my Mexts query
the Hesiod records which servered by Sun.
Speaking to Sun, I have another question would like to ask. Here we are
extensivly using Hesiod to server vaious network records. Things like passwd,
mail server, amd maps, etc. For the time being, we configured so that DNS
server answers both name queries as well as Hesiods'. Now, my question, is it
possible to seperate regular DNS and Hesiod name server so that client can
query different server for different services? I have tried, for example, to
configurate client's conf/named.boot file, but it seems that Hesiod query also
be ignored. What do you do over MIT?
Thanks for your response on both preious and future ones.
-----------------------------------------------------------------------------
Haisong Cai, Computer Systems Specialist
Institute for Systems Research
University of Maryland at College Park
haisong@src.umd.edu // uunet!glue.umd.edu!haisong
