unsubscribe%20freevsd-support

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Steve Searles
Sent: Tuesday, September 18, 2001 6:52 PM
To: '[EMAIL PROTECTED]'
Subject: RE: mod_bind, Silly question

That is IT !!!!! Thanks Tim


Steve 


 -----Original Message-----
From:   [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]  On Behalf Of Tim Sellar
Sent:   Tuesday, September 18, 2001 4:38 PM
To:     [EMAIL PROTECTED]
Subject:        RE: mod_bind, Silly question

Hmmm. I believe that referring to your nameserver by IP address within
vsd.conf causes problems when using mod_bind and that you should instead
be
referring to them by their fqdn. This is a problem which has been
resolved
as of freevsd-1.4.10-1.

Tim

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Searles
> Sent: 18 September 2001 19:47
> To: '[EMAIL PROTECTED]'
> Subject: RE: mod_bind, Silly question
>
>
> It is still doing it, vsd.conf was set up correctly.  I have had this
> working once on a box where the nameserver and the host server
> were the same
> box, however I was trying to use a sepertate box for the nameservers
this
> time.  I tried reverting to the nameserver local to the
> hostserver now I get
> 2 errors if I play with quota settings I can get it to say
> "Cannot determine
> if I am primary or secondary" Or it will say "Err - Quota exceeded. "
I
> don't know what I have fudged up but I can not manage to get
> working what I
> had working.  Also when I use the "vsdadm bind_addvs " It creates
another
> entry in /etc/vsd.conf.  Does anyone know what that is all about?
>
>
> Steve
>
>
>  -----Original Message-----
> From:         [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]  On Behalf Of Nigel Marett
> Sent: Tuesday, September 18, 2001 9:19 AM
> To:   [EMAIL PROTECTED]
> Subject:      Re: mod_bind, Silly question
>
> Hi Steve,
>
> Please check your vsd.conf (/etc/vsd/vsd.conf;
> /usr/local/etc/vsd/vsd.conf)
>
> When running mod_bind it should look somthing like this:
>
> <Global>
> UIDRange 1000 60000
> UIDAllocChunk 100
> PrimaryNS <IP of your primary NS>   <------
> SecondaryNS <IP of your secondary>   <-----
> Skel freevsd-skel-1_4_9-1rh6
> ErrorLog /var/log/vsd.log
> BWBurst 0bps
> BWLimit 0bps
> </Global>
>
> # Virtual server account details
> <VirtualServer bogus.idaya.co.uk>
> IP 299.000.000.1
> StartUID 0
> Users 0
> Status active
> Quota 0
> MaxVD 0
> MaxIP 0
> Skel freevsd-skel-1_4_9-1rh6
> Partition 0
> CertificateAuthorityServer bogus.idaya.co.uk
> PrimaryNS <IP of your primary>
> SecondaryNS <IP of your secondary>
> </VirtualServer>
>
> ----------snip------------------
>
> In my experence the error message you are recieveing happens when
> mod_bind
> basicly cannot determine if it is running on the primary or
> secondary NS (as
>
> it says) and usually is beacause you have your pri and sec IP's
> set to other
>
> NS's.
>
> If there are no problems with your vsd.conf, could you please
> provide more
> information.
> ie:
> are you running your primary NS on your vsd server or on another
> standalone
> box?
>
>
> HTH,
>
> cheers,
>
> Nigel.
>
> On Tuesday 18 September 2001  1:56 pm, you wrote:
> > Whenever I use my web admin modules to configure nameservers in a VS
I
> > recieve the following message
> >
> > Add to Primary NS :
> >
> > -ERR Cannot determine whether I am primary or secondary
> >
> > I had this working with just 1 nameserver now I have 2 for this
> project, I
> > belive my screw up is in the "vsdadm bind_addvs" command as follows
> >
> > [root@hostsrv01 /etc]# vsdadm bind_addvs ?
> > syntax: bind_addvs <ns> <vs> <ip> <max domains> [<pri ns>] [<sec
ns>]
> >
> > What does it want for the <pri ns> and <sec ns>??? Ip addresses of
> > nameservers or fqdn?  HELP!!!
> >
> > Thanks is advance
> >
> > Steve
> >
> > ------------------------- 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
> >
> ------------------------------------------------------------------
> ---------
> >--
> ------------------------- 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
> ------------------------------------------------------------------
> ----------
> -
> ------------------------- 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
> ------------------------------------------------------------------
> -----------

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

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

Reply via email to