[207] in Hesiod
Re: Strange Lame delegation
daemon@ATHENA.MIT.EDU (dean@hi.com)
Tue Jun 28 18:24:05 1994
From: dean@hi.com
To: Greg Wohletz <greg@duke.cs.unlv.edu>
Cc: Todd.Miller@cs.colorado.edu, paul@vix.com, gshapiro@wpi.edu,
hesiod@MIT.EDU
In-Reply-To: Your message of "Tue, 28 Jun 94 13:04:01 EDT."
<9406282005.AA14407@MIT.EDU>
Date: Tue, 28 Jun 94 18:26:19 EDT
Hmm. I seem to recall that root nameservers would support HS class "real
soon now" a while ago. Did this happpen?
What I did in the past to get around this was to use IN class records
instead of HS class records. This is real easy to do, only about 3
lines of code comprising a total of 6 characters need to change in
the library. It does not require a change to clients. Oh, and of
course, the nameserver maps should have things like
dean.passwd IN TXT "..."
instead of
dean.passwd HS TXT "..."
The hesiod maps are stored in IN class subdomains, so you must work it into
your subdomain naming scheme, but that is easy. (eg passwd.hs.hi.com) I think
the other reason for inventing the HS class was a concern about performance.
But in practice, I have never observed performance problems due to hesiod
records (by their mere existance), and I don't really think that another
class makes a significant difference as long as you keep your hesiod records
in their own subdomain. And you avoid having to stuff your .ca file with
HS root nameservers. It just works.
If you want, I can post diffs to the MIT hesiod library.
--Dean
=++=+=+=+++==++=+=+=+++==++=+=+=+++==++=+=+=+++==++=+=+=+++==++=+=+=+++=
Dean Anderson Dean@hi.com
Project Leader, System Administration
Hitachi Computer Products
