From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Authoritative Name Server
Date: Wed, 16 Sep 2009 18:47:17 -0400 [thread overview]
Message-ID: <fe41879c0909161547i4a0846b0qdfe89b8a106799ab@mail.gmail.com> (raw)
In-Reply-To: <35e1ba3ae1b9f7c427c2823732cd64f0@coraid.com>
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
next prev parent reply other threads:[~2009-09-16 22:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 19:31 Akshat Kumar
2009-09-16 20:03 ` erik quanstrom
2009-09-16 20:37 ` Akshat Kumar
2009-09-16 20:51 ` erik quanstrom
2009-09-16 22:47 ` Akshat Kumar [this message]
2009-09-16 23:02 ` Akshat Kumar
2009-09-16 23:05 ` erik quanstrom
2009-09-16 23:25 ` Lyndon Nerenberg - VE6BBM/VE7TFX
2009-09-16 23:37 ` Akshat Kumar
2009-09-16 23:40 ` erik quanstrom
2009-09-16 23:58 ` Akshat Kumar
2009-09-16 23:47 ` Lyndon Nerenberg - VE6BBM/VE7TFX
2009-09-16 23:52 ` Akshat Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe41879c0909161547i4a0846b0qdfe89b8a106799ab@mail.gmail.com \
--to=akumar@mail.nanosouffle.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).