From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Authoritative Name Server
Date: Wed, 16 Sep 2009 15:31:28 -0400 [thread overview]
Message-ID: <fe41879c0909161231q5f1cd5a6r4083aca9e18cbda1@mail.gmail.com> (raw)
I'm trying to setup an authoritative name server for a domain
in Plan 9. Not all of the available ndb(6) directives for this task
are documented, so I have some questions:
The secondary name servers all run BIND on UNIX, and I need
to do zone transfers to them, from Plan 9. Will simple zone
transfers (given the -n flag to ndb/dns) suffice, or does the
outgoing ndb file somehow need to be reformatted for BIND?
If I have subdomains for the domain I'm managing, do those
subdomains get their own dom=... blocks? If so, do I need to
specify soa=, dnsslave=, ns=, etc. for each subdomain entry,
or will the specifications for the main domain satisfy?
(E.g.:
dom=example.com soa=
serial=2009150901
refresh=10800 retry=3600 ttl=86400 expire=2592000
ip=x.x.x.x
ns=ns1.example.com
ns=myexample.com
ns=yaexample.com
dnsslave=myexample.com
dnsslave=yaexample.com
dom=mail.example.com soa=
mx=... pref=1
mx=... pref=5
...
dom=sub.mail.example.com cname=mail.example.com
here, does the mail.example.com block need to also have ns=,
refresh=, and the other entries found in the example.com block?)
In zone transfers, is everything that is included by /lib/ndb/local sent,
or can one specify what (or which file) to send? For these purposes,
I'm keeping the whole domain configuration in a separate file:
/lib/ndb/zone
Thanks,
ak
next reply other threads:[~2009-09-16 19:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 19:31 Akshat Kumar [this message]
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
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=fe41879c0909161231q5f1cd5a6r4083aca9e18cbda1@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).