Re:The world in which IPv6 was a good design
by efreak on Friday August 11, 2017 @04:22PM
(#14993809)
On another note, I have long wished for something like specifying protocol port numbers in a DNS record. Ever since I ran my first ircd on a shared hosting server, and continuing to today with multiple httpds (nginx, znc, etc) and ircds (ZNC, bitlbee) and such on a single IP.
Not for any technical reasons, though--I'm just lazy, and specifying port numbers is annoying.
Re:The world in which IPv6 was a good design
by jsjohnst on Friday August 11, 2017 @10:21AM
(#14989899)
Maybe it's early and I've not drank enough coffee yet, but what benefit would this provide? You'll be in effect doubling the DNS lookups needed to connect to a website adding latency to time to first byte, with seemingly zero benefit.
Re:The world in which IPv6 was a good design
by JdeBP on Friday August 11, 2017 @12:47PM
(#14991735)
As I pointed out at https://news.ycombinator.com/item?id=14721416 , the claim of "doubling the DNS lookups" simply does not hold water if actually analysed.
Re:The world in which IPv6 was a good design
by apenwarr on Friday August 11, 2017 @12:58PM
(#14991877)
The main benefit would be the ability to offer public Internet-facing services through a NAT, even a carrier-grade NAT that lumps multiple ISP customers behind a single IP address. (You would need some kind of cooperation from the NAT to be able to allow incoming connections on a port range.)
JdeBP's post provides a good answer about the SRV records. The short version is a single DNS packet can contain both A/AAAA and SRV responses.
That could be extended to the server side if we used something like SRV records instead of defaulting to port 80/443.