5 ms·
But - if we had SRV records for http(s), things like geo load balancing would be super simple, no need for anycast / weird CNAME chains. The client would get a
by mugsie 5y ago
But - if we had SRV records for http(s), things like geo load balancing would be super simple, no need for anycast / weird CNAME chains.
The client would get a list of hosts, with attached priorities, and weights.
- andix 5y agoDo you have any further information on this topic, some blog post or something that explains how this would work?
- pvtmert 5y agobasically normal A response (whether or not coming from a cname) doesn't define any weights or priority. just order may be changed by the server according to clients' geoip, you just need to adjust weights/priority in the srv record so, a client can fallback next-nearest server
- jlgaddis 5y agoI don't have a specific URL for you (other than for the authoritative source, the DNS RFCs) but a good example would be how clients in an Active Directory environment find a Domain Controller to log on to -- I'm sure there's plenty of documentation and examples of that on the web! Hint: This same method (SRV RRs and priorities/weights) so that a client communicates with a Domain Controller down the hall, instead of another one halfway across the country. Then, just imagine that it's a web browser connecting to a web server, instead of a workstation connecting to a DC.