Talk:Round-robin DNS

I request an expert discuss the issue of PTR records in the context of round-robin techniques. What are the standards, what are the best practices and what are the pros & cons. I could give my opinion, or I could do the research and write a paper on the issue, but neither of those approaches are acceptable to the wikipedia philosophy in my understanding. —Preceding unsigned comment added by 129.97.15.226 (talk) 16:27, 29 October 2010 (UTC)

Chicken or egg? http://www.webopedia.com/TERM/R/Round_Robin_DNS.html

This is actually a really great page (and in response to the webopedia ref, I bet they simply copied wikipedia's version - they are allowed to). I think "multiple A records" should be included in the text somewhere, that's what rr dns is all about imho. informedbanker —Preceding unsigned comment added by Informedbanker (talk • contribs) 13:34, 6 September 2007 (UTC)


 * ✅. I agree that someone should mention "multiple A records" in this text, so I did. --DavidCary (talk) 18:44, 10 January 2020 (UTC)

"Some desktop clients do try alternate addresses after a connection timeout of 30–45 seconds." -- I think that including a nearly exact amount of time the client is going to wait for a timeout to happen is not sensible here. The service to which the request is made may have a completely different timeout depending on so many parameters that it's probably not even worth listing here. I suggest we remove that part: "Some desktop clients do try alternate addresses after a connection." --Alexis Wilke (talk) 00:22, 18 September 2018 (UTC)


 * I agree that it seems unlikely that every client has a timeout in this range, and I didn't see any references for that sentence, so I added a reference and changed the sentence to match what that reference states -- "Some desktop clients do try alternate addresses after a connection timeout of up to 30 seconds." That reference only tested web browsers -- is there any *other* kind of desktop client that should be mentioned? --DavidCary (talk) 18:44, 10 January 2020 (UTC)