> >> > 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
