On Sun, 4 Nov 2001 12:26:08 -0000 "Tim Sellar" <[EMAIL PROTECTED]> wrote:
> It sounds like you are running your nameserver on the hosting server. In > this situation you do not need to execute a bind_addvs command. The > bind_addvs command essentially adds an entry into vsd.conf on the name > server, which would normally be a separate machine. In your case an entry > for the virtual server already exists in vsd.conf - so no need to add > another (in fact two entries for one virtual server will cause problems). > > Also, with freeevsd 1.4.9 the Quota entry is re-used by mod_bind to provide > a limit on the number of domains a virtual server may add. This causes a > problem when the name server is held upon a hosting server on which disk > quotas are being used and has been resolved in 1.4.10. So, remove the second > entry for teste, set the Quota on the first entry to 35 and you should be > OK. Yes, I have a nameserver running in the hosting server. So, I do it what you say: 1) Remove the second entry for test 2) Ser the quota in first entry 3) Just run the command " vsdadm bind_add hostserver.com test potato.net 200.xxx.xxx.248 [EMAIL PROTECTED] " Well, now I get the error: --------------------------------------- " error: -ERR Cannot determine whether I am primary or secondary " My vsd.conf is: <VirtualServer test> IP 200.xxx.xxx.242 StartUID 1000 Users 200 Status active Quota 30 MaxVD 5 Skel rh7 Partition 0 HostingServer xxxxxxxxxxxxx.com PrimaryNS 200.xxx.xxx.240 SecondaryNS 200.xxx.xxx.241 </VirtualServer> Some idea ??? Thanks -- Ana Paula <[EMAIL PROTECTED]> ------------------------- The freeVSD Support List -------------------------- Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support Archives: http://freevsd.org/support/mail-archives/freevsd-support -----------------------------------------------------------------------------
