From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ndb/dns as a slave
Date: Sat, 22 Aug 2009 22:05:18 -0400 [thread overview]
Message-ID: <1c8399d5c90c463d24904073f50899e1@quanstro.net> (raw)
In-Reply-To: <9ab217670908221524u837fbf1o59820bf83e84f916@mail.gmail.com>
> >> > I assume your master DNS is served from bind, then you
> >> > can use the zonefresh program in my contrib to build an
> >> > ndb compatible ndb file for your local dns to serve.
> >>
> >> Actually, I'm using ndb/dns for both. I seem to recall reading that
> >> ndb supports zone transfers by looking for large packets in udp53 (or
> >> something). I suppose if this isn't possible, periodically pulling
> >> /lib/ndb/local from the other machine and sending refresh to /net/dns
> >> could work. (Just kind of wondering what the standard procedure is :))
> >
> > in that case, why wouldn't you use plan 9 methods, rather
> > than rely on goofy dns stuff?
>
> Because I rarely actually use Plan 9 and I'm not sure what the
> proposed methodology for doing this is.
if you're not normally using plan 9, i'm not sure why you'd be using
plan 9 for dns.
i think i would just have a script running on the slave that
import(1)'s the master and checks to see if the mater's ndb
file is newer. to simply things, i would break out the zone
into its own ndb file.
to be run from cron. this requires a shared user account
between the systems: (untested)
#!/bin/rc
# refreshzone
master=master.example.com
zf=example.com
import -E ssl $master /n/master
if(test /n/master/lib/ndb/$zf -nt /lib/ndb/$zf)
cp -x /n/master/lib/ndb/$zf /lib/ndb
- erik
prev parent reply other threads:[~2009-08-23 2:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-22 3:05 Devon H. O'Dell
2009-08-22 11:08 ` Steve Simon
2009-08-22 13:32 ` Devon H. O'Dell
2009-08-22 13:54 ` Devon H. O'Dell
2009-08-22 14:40 ` lucio
2009-08-22 14:47 ` Devon H. O'Dell
2009-08-22 20:05 ` erik quanstrom
2009-08-22 22:24 ` Devon H. O'Dell
2009-08-23 2:05 ` erik quanstrom [this message]
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=1c8399d5c90c463d24904073f50899e1@quanstro.net \
--to=quanstro@quanstro.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).