"It is not expected that most web browsers would support these schemes for generic web use. It would instead be used for particular applications using HTTP such

"It is not expected that most web browsers would support these schemes for generic web use. It would instead be used for particular applications using HTTP such as specific web APIs. These APIs would be defined to require the use of this specification. In this situation, the end user's web browser might not do the SRV lookup when it browsed to the portal web pages, but the HTTP calls that the portal made out to other sites to generate the content would use this mechanism. As such architectures become more common, DNS SRV would allow many servers that are just providing an API to run on ports other than 80 even though main portal sites may still be running on the well known ports. Eventually, web browsers may end up supporting these SRV lookups, as the implementation is trivial and has very little downside." My thoughts: 1. This would be very advantageous in cases like a K8s cluster, where if you want to use just DNS for service discovery, you still need an ingress listening on port 80 or 443, with nginx rules defined to route each service to a mapped port. A more general DNS method would eliminate the need of an ingress to route traffic. 2. We should be using this for all requests. It's more than a little ridiculous that it's 2022 and we have 65,535 different ports to use, but we can only use 1 of them (443) because we can't get the industry to fix its old designs.