I’m guessing the older app lacked the ability to utilize DNS round robin, which is kinda puzzling as it has been around a long time.
From: J- P Sent: Saturday, January 31, 2015 3:03 PM To: NT Subject: RE: [NTSysADM] DNS round robin & apps thx for the clarification, The reason this came about is because some of the apps we use specifically allow you to enter a primamry url and a secondary url to connect to the server , and this new one did not have that option. thx again -------------------------------------------------------------------------------- Subject: Re: [NTSysADM] DNS round robin & apps From: [email protected] Date: Sat, 31 Jan 2015 14:54:25 -0800 To: [email protected] When a given app requests an address of DNS all records matching that request are returned. It is up to the app which one is used, and in what order, and up to DNS to shuffle the order of return. On Jan 31, 2015, at 14:13, "J- P" <[email protected]> wrote: hi all I have a question regarding secondary A records for redundancy using an App This article seems to say that web browsers will retry a second ip if one fails to res;pond and that it is the OS & or the browser that allows this to happen. http://webmasters.stackexchange.com/questions/10927/using-multiple-a-records-for-my-domain-do-web-browsers-ever-try-more-than-one Client has a timesheet system that is web based but also has a proprietary app written by the software vendor, so my question is When it comes to apps does the OS or the app do the round robin?
