4 ms·
I dont get why people keep trying to make SRV happen. It seems like an extra layer of indirection that doesn't solve any real problems and just adds complicati
by bawolff 4y ago
I dont get why people keep trying to make SRV happen.
It seems like an extra layer of indirection that doesn't solve any real problems and just adds complication.
Edit: i guess up until recently where ECH provided more of a rationale.
- teddyh 4y agoIt (either SRV or HTTPS/SVCB) solves two significant problems: It makes web serving as robust as SMTP, with official fallback servers listed in the DNS. This makes most uses of CDNs or DDoS protection services unnecessary, as you can just spin up N different servers and list them all in the DNS. No need to centralize everything behind Cloudflare or Google. It also solves the “apex delegation” problem; i.e. the problem of having to hard-code the IP address or addresses of a service at the apex domain name (i.e. on example.com instead of on www.example.com), without even having a CNAME, making you having to change that IP address on all domains using that web service whenever that service changes it IP address. (So-called “ALIAS” DNS records are fake; they are an ugly hack which does the aforementioned changing of IP addresses automatically.) These two are what I personally consider the most important ones, but there are more: https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-11#section-1.1 https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-...
- bawolff 4y ago> It makes web serving as robust as SMTP, with official fallback servers listed in the DNS. This makes most uses of CDNs or DDoS protection services unnecessary, as you can just spin up N different servers and list them all in the DNS. No need to centralize everything behind Cloudflare or Google. There are lots of load balancing solutions that are really well developed. I think most people use cloudflare because its really easy, and (the probably misguided notion) that shaving a few ms via georeplication is worth it . And for some users, fear of a volumetric DoS that just totally saturates the network link. I feel like the type of people who would be content with the load balancing offered by SRV are probably already using load balancing on some other layer, e.g. LVS or HAproxy.
- marcosdumay 4y agoThe problem CDNs solve can simply not be solved at protocol-level load balancing. And yes, when people talk about DDoS mitigation, they are talking about a volumetric DoS that saturates their network link.
- somat 4y agotcp[1] added an additional address segment, what is called the "port". in a perfect world this would not exists and it would be a single unified address(the ip address) all the way down[2], but this was before the ip6 post address scarcity future and the port was seen as the way to allow each host to deliver many services. The SRV record was the way invented to expose ports to the dns system. like how A records expose addresses to dns. But sadly this too was in the future. so the interim method used was to have services running on commonly agreed ports, the well known ports. And so here we are stuck with ports, those will never go away, and stuck with the "well known ports", at least we have a mechanism to name ports. if only more programs would get with the act. 1. yes yes udp exists and has ports, I know, feel free to fill in TCP/UDP whenever you see TCP, if that makes you happy. 2. the narrow waist is an amazingly useful phenomenon, everything being addressed the same gives you great flexibility... And... I have just seen the light, the skies opened up, an angel spoke. you are right. ignore ports completely(or at least as much as you can) and give each service it's own ip6 address. not sarcasm, but genuine enlightenment. I already do this for dns servers, dns servers hate to run off port 53, while there are ways to change the port nobody is happy about it, it is less pain to give each one it's own address and bind to that. (Q: why do you run multiple dns severs on one box? A: because I run unbound and nsd)