3 ms·
SRV support seems to have been (unfairly, I think) rejected by HTTP vendors and standard bodies. There is a new standard, however, in the works: https://datatr
by teddyh 5y ago
SRV support seems to have been (unfairly, I think) rejected by HTTP vendors and standard bodies. There is a new standard, however, in the works:
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-08 https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-...
https://github.com/MikeBishop/dns-alt-svc https://github.com/MikeBishop/dns-alt-svc
This one might have a larger chance of being accepted, since it provides some things which HTTP standard bodies and HTTP client vendors want. It doesn’t (at this stage, anyway) provide for the load-balancing “weight” field from the SRV record, but it does support MX-style priority numbers, and also port numbers. Very interesting, to say the least.