From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <35e1ba3ae1b9f7c427c2823732cd64f0@coraid.com>
References: <fe41879c0909161231q5f1cd5a6r4083aca9e18cbda1@mail.gmail.com>
	<35e1ba3ae1b9f7c427c2823732cd64f0@coraid.com>
Date: Wed, 16 Sep 2009 18:47:17 -0400
Message-ID: <fe41879c0909161547i4a0846b0qdfe89b8a106799ab@mail.gmail.com>
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [9fans] Authoritative Name Server
Topicbox-Message-UUID: 6f2aacfe-ead5-11e9-9d60-3106f5b1d025

I've got the basic setup going, and have tested it for appropriate
information using ndb/dnsquery in Plan 9 (on the same computer
that is running `ndb/dns -rns`).

> looks like it should work.  if you should need an bind-comptable
> zone file (and i do), contrib quanstro/ndbtozone is a program that
> converts ndb format to dns format.  it tosses out-of-balliwick stuff
> and ndb tuples that have no bearing on dns.

However, when I test the name server using:

dig @ns1.nanosouffle.net nanosouffle.net axfr

I get partial data back, but the transfer fails with:
;; Warning: Message parser reports malformed message packet.
; Transfer failed.

Does this indicate that I should use your ndbtozone program?
How do you automate the process of converting to dns format
and then sending the data, when doing a zone transfer?
My secondary nameservers are running BIND on UNIX.


Thanks,
ak