What you are describing is basically how CDN (Content Delivery Networks) work.
The DNS aspect is not exactly as you suggest, but the DNS server returns different IP addresses depending on where the requester is. This ensures that the returned address is relatively close (in network terms) to the requester.
The IP address in returned isn't directly associated with the actual server that will deliver the content, but with a device called a load balancer. This device divides it's incoming requests between a pool of servers that actually service the request. It also monitors the health of the pool of servers and will stop sending requests should any fail. (It can also act in a hot spare mode, where all traffic is sent to one server until it fails, at which point the load balancer will switch to a second server).
The closest you can get with just basic DNS is to have multiple IP addresses mapped to the same domain name, in this case the DNS server uses what is known as "round-robin" balancing, this means that is works through the list of IP addresses in order for each request. This means that traffic will be balanced across all the IP addresses but still sent if one is dowm