DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23501>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23501

[mod_rewrite] incorrect load balancing solution

           Summary: [mod_rewrite] incorrect load balancing solution
           Product: Apache httpd-2.0
           Version: 2.0.47
          Platform: All
               URL: http://httpd.apache.org/docs-2.0/misc/rewriteguide.html
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Documentation
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


The rewrite guide incorrect gives an example using BIND syntax that's been
deprecated for awhile now. Both 2.0 and 1.3 documentation has the same problem.

The example is for:

Load Balancing
Description:
    Suppose we want to load balance the traffic to www.foo.com over
www[0-5].foo.com (a total of 6 servers). How can this be done?

The solution goes on to list multiple cnames for the same label:
www    IN  CNAME   www0.foo.com.
       IN  CNAME   www1.foo.com.
       IN  CNAME   www2.foo.com.
       IN  CNAME   www3.foo.com.
       IN  CNAME   www4.foo.com.
       IN  CNAME   www5.foo.com.
       IN  CNAME   www6.foo.com.

This is incorrect, according to RFC 2181 (and other DNS RFCs):
"There may be only one such canonical name for any one alias."
BIND 8 (and prior versions) could be made to work with multiple cnames, but BIND
9 no longer supports it at all.

The correct implementation uses multiple A records for the label, like so:
www   IN  A       1.2.3.1
      IN  A       1.2.3.2
      IN  A       1.2.3.3
      IN  A       1.2.3.4
      IN  A       1.2.3.5
      IN  A       1.2.3.6

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to