Am I right in thinking that Google public DNS simply does not cycle the multiple records on a round-robin host. There have been a few threads on this (i.e. google "round robin 8.8.8.8")
If this is true, is it a stretch to see this impacting traffic patterns on a host whose traffic is almost 100% mobile devices, more so than other, standard websites using round robin?
We've seen this issue with a client who has mostly mobile end devices and they're (very) not happy.
Currently Google will serve out an IPv4 list in the same order they are given it, so if the Authoritative server does round robin, and there is a short TTL, then you can (kind of) force Google to.
However, (IMHO) relying on the weird co-incidence that Google serves addresses in the same order they are received is not good practice.
_______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
