The VS owner can use vsdadm if freeVSD has been installed into the virtual
servers. Doing this at the moment requires some manual work but will be
carried out automagically in 1.4.8 (release 14th May). Allowing VS owners
access to name servers via vsdadm also necessitates the use of OpenSSL
certificates to provide authentication, so a new module mod_ca has been
written to manage a simple certificate authority. Presently mod_bind
functionality is best used through VSDClient. The WebAdmin scripts contain
examples of using mod_bind functionality but the relevant sections are
disabled as they still refer to the old package name of mod_webdns - the
necessary changes are pending.
Tim
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Free VSD
> Sent: 30 April 2001 09:30
> To: [EMAIL PROTECTED]
> Subject: re: mod_bind
>
>
> YEs, good question. The vs owner is not supposed to be able to
> "vsdadm". How to get that around?
>
> I am trying to get the WebAdmin nameserver part work though
>
>
>
>
>
>
> vsdadm doesn't seem to be assesible from within the VS?
>
>
> Zen
>
>
> ----- Original Message -----
> From: "Nick Burrett" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, April 03, 2001 9:22 PM
> Subject: Re: mod_bind
>
>
>
> "Zen Woo" <[EMAIL PROTECTED]> writes:
>
>
> > Okay, I did this:
> >
> > /usr/sbin/vsdadm vs_create localhost vsone XXX.XXX.XXX.XXX
> vsone.net 500
> 500
> > /usr/sbin/vsdadm bind_addvs dns.networkns.net vsone XXX.XXX.XXX.XXX 500
> > /usr/sbin/vsd-vsbatch.pl
> > /usr/sbin/vsdadm quota_vsset localhost vsone 500M
> > /usr/sbin/vsdadm vs_enable localhost vsone
> >
> > Now what? How do I add a domain to the NS from within the VS?
>
>
> Run vsdadm from within the VS. Use bind_add.
>
>
> > Please advise.
> >
> > Zen
>
>
>
>
> --
>
> _______________________________________________
> Get your free email from www.kittymail.com
>
> Powered by Outblaze
