Bind8 and Hesiod under Ultrix

[Simon Burge]

Folks,

I'm having problems getting bind8 under Ultrix to talk hesiod to another
bind4 server.  This is for a DNS setup behind a firewall and not
connected to the 'net.  For a caching nameserver under bind4, I simply
had:

	.  {ttl}  HS NS  {master}
	.  {ttl}  IN HS  {master}

	{master} {ttl} IN A {ipaddress}

in the named.cache file.  Under bind8, I've got a "root.cache" with:

	.  {ttl}  IN HS  {master}

	{master} {ttl} IN A {ipaddress}

and a "root.cache.hs" with:

	.  {ttl}  NS HS  {master}

With just this, I get:

	Jul 23 16:00:44 fred named[880]: sysquery: no addrs found for root NS ({master})

in syslog when querying something that should exist in hesiod.  Adding:

	{master} {ttl} IN A {ipaddress}

I get:

	Jul 23 16:06:09 fred named[938]: root.cache.hs: Line 15: wrong class: IN.
	Jul 23 16:06:09 fred named[938]: root.cache.hs:15: Database error (IN)
	Jul 23 16:06:09 fred named[938]: hint zone "" (HS) rejected due to errors (serial 0)

in syslog.  Finally, adding

	{master} {ttl} HS A {ipaddress}

seems to work ok.  However, the ipaddress of master isn't in the hesiod
class, so this seems wrong to me.  I've not been able to find any
examples of setting up hesiod under bind8 with a web search - is this
really the right way to do this?



Getting bind8 compiled under Ultrix was a whole 'nother story
altogether, and I'm still not sure I've got it 100% right yet.  I'll
package it up when I'm done and send something to bind-workers.

Simon.