From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Authoritative Name Server
Date: Wed, 16 Sep 2009 16:03:37 -0400 [thread overview]
Message-ID: <35e1ba3ae1b9f7c427c2823732cd64f0@coraid.com> (raw)
In-Reply-To: <fe41879c0909161231q5f1cd5a6r4083aca9e18cbda1@mail.gmail.com>
> 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?
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.
> 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?
this depends entirely if you want to have the subdomains
as seperate zones or not. dns is really wierd. imagine if
you could have "/" in a file name. then x/y could be either
the directory x containing file y or just the file named x/y.
replace "/" with "." and that's how dns zones work.
i wouldn't bother breaking up the zones if there's no
particular adminstative reason to do so.
- erik
next prev parent reply other threads:[~2009-09-16 20:03 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 [this message]
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=35e1ba3ae1b9f7c427c2823732cd64f0@coraid.com \
--to=quanstro@coraid.com \
--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).