Can using a bare domain as server address (i.e. using example.com not www.example.com) make DNS based load balancing harder in some manner?
Load balancing examples:
- Round robin DNS load balancing.
- Split Horizon DNS Server, that is, giving different responses (IP addresses) based on the client address.
- A planned feature of Amazon Route 53: "In the future, we plan to add additional integration features such as the ability to route your customers to the closest EC2 region."
Background: Sometimes when people argue one should include www in the server address, instead of using a bare domain name as server address, they mention problems related to load balancing and bare domains. But they don't seem to specify what are those problems.