The highest incentive, and the optimal strategy, is for content *owners*
to manage this, not *consumers*.
http://lmgtfy.com/?q=content+distribution+network
- Kevin
Tech W. wrote:
Hello,
We have been facing this problem, sometime the original server was down, but
Bind didn't know it, and still answered clients with the dead IP.
Or sometime an external domain name has two or more IPs, accessing to part of
them is fast, but accessing to another part is slow.
So, do you think is there a resolving way for Bind which can implement the
features:
1. check the popular domains' original IPs (like google's, yahoo's, aol's etc),
and exclude the dead IPs from its cache.
2. for the popular domains, testing the access speed to each of their IPs and
answers the fast IPs to local clients.
Thanks for any suggestion.
Regards,
Wah.
__________________________________________________________________________________
See what's on at the movies in your area. Find out now:
http://au.movies.yahoo.com/session-times/
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
