Sure, I'm quite aware that there are many such tricks in use. I may even have helped
to commit one or two of them in my former life. But the architecture of name
resolution for IPv6 is as I described - if there are multiple AAAA records,
you get multiple answers and the host gets to choose.
Brian
"David R. Conrad" wrote:
>
> Brian,
>
> > DNS doesn't make a choice. If there are multiple addresses,
> > it returns all of them. The host makes the choice.
>
> Let me introduce you to today's current crop of DNS-based load balancing
> "solutions". For example, from
> http://www.resonate.com/products/global_dispatch/faqs.php3:
>
> How does Global Dispatch relate to DNS architectures?
>
> Global Dispatch is an authoritative DNS solution- meaning that it integrates
> into a DNS architecture- but actually replaces existing 'dumb' authoritative
> DNS capabilities. The Global Dispatch scheduler sits behind an existing
> authoritative DNS server, such as BIND or Microsoft's DNS server. Global
> Dispatch resolves a virtual hostname into the IP address of a physical POP.
> When a client's local DNS server makes an address resolution request for a
> virtual hostname, Global Dispatch responds with the IP address of the most
> available physical POP based on latency and load information it receives from
> agents installed at each POP.
>
> Rgds,
> -drc
