Louis A. Mamakos wrote:
> > cvsup IN CNAME cvsup1.freebsd.org.
> > cvsup IN CNAME cvsup2.freebsd.org.
> > cvsup IN CNAME cvsup3.freebsd.org.
> > cvsup IN CNAME cvsup4.freebsd.org.
> > cvsup IN CNAME cvsup5.freebsd.org.
> > cvsup IN CNAME cvsup6.freebsd.org.
> > cvsup IN CNAME cvsup7.freebsd.org.
> > cvsup IN CNAME cvsup8.freebsd.org.
>
> This is wrong two ways.
>
> First, the data associated with a CNAME is supposed to be the
> cannonical name of a host, and not another domain name with only
> a CNAME resource record.
??? Are all cvsupX.freebsd.org also CNAME's?
> Second, a domain name can at most a single CNAME record associated
> with it, and other other record types. BIND will (should) barf on a
> zone file containing the example you listed.
It does not. It will round-robin over the CNAME's.
> > If you simply put "cvsup.freebsd.org" into your supfile you'll get
> > randomly one of them. This should spread the load fairly well. If
> > you want a special one then simply put "cvsupX.freebsd.org" into
> > you supfile.
>
> You could play some DNS games to get this effect, though it's not
> clear what the randomness of the list of resource records is supposed
> to be. Certain the DNS protocol doesn't define any randomness.
But bind does.
> > I don't see any appearant reson (short of network connectivity) that
> > one *needs* to get always the *same* server.
>
> See previous mesasge from John regarding doing two successive updates
> where the servers are not synchronized with the same version files.
Who cvsup's regurlary more than once or twice a day? Committers AFAIK
do cvs directly.
> Is this really a problem that demands solutions this complicated? The
> solution isn't necessarily a technological one; a simple email message
> reminding people of other servers might be sufficient :-)
Yea, then all swamp cvsup8.freebsd.org and John has to send another
message that there are still cvsup[2-7].freebsd.org idling around.
Just kidding... But you get the point?
--
Andre
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
