Dustin Lovell wrote:
Certain browsers hitting our web application don't like having two A-records handed to them (I'm still in the process of figuring out why),
Yeah, you really need to dig into that further, since we have *hundreds*
of multi-A-record names, and we've never run into any browser problems
because of it.
Misdiagnosis perhaps?
Now, it _is_ true that some browsers take a noticeably -- and thus
perhaps unacceptably -- long time to fail over from one address to
another, when given a multi-A-record DNS response and the first address,
or the first _n_ addresses, are unreachable. But if all of the addresses
are reachable, I'm not aware of any browsers that have an issue with
multi-A-record DNS responses _per_se_. They are extremely common.
- Kevin
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
