Op solved a problem and your comment is "I wouldn't have solved the problem".

>legacy IP

lol

It's a nice solution for sure, but a problem by choice. You could just have an AAAA record for the domain in addition to the A record, and as GP pointed out, resolve SSH sessions via the IPv6. If the user wants SSH to work with IPv4 for whatever reason—I see the point that there may be some web visitors without IPv6 still, but devs?—they could pay a small extra for a dedicated IPv4 address.

▲

michaelt 5 hours ago | parent | next [-]

Products targeted at developers like to get a foothold in large corporations "by stealth" - let the developers experience what a great product it is first, before they have to do the approval paperwork.

With this IPv4 trick, if your employer or university only provides IPv4 you can use the product anyway.

▲

lifthrasiir 6 hours ago | parent | prev [-]

They could buy a dedicated IPv4 address, but that address still has to be tunneled through [EDIT:] IPv6 networks if that dev has no access to [EDIT:] IPv4 networks. Thus DX still suffers. [ADDENDUM: I mistakenly swapped "IPv4" and "IPv6" there. See comments.]

▲

9dev 6 hours ago | parent [-]

I'm not sure I understand your point; if exe.dev operates a dedicated IP solely so a specific mythical IPv6-less developer can connect to a specific server, then there's no tunnelling involved at all.

	▲	lifthrasiir 6 hours ago \| parent [-]
		Oops, I think I mixed up two sentences in the middle. A fixed comment is available. But I also probably misinterpreted what you were saying: > they could pay a small extra for a dedicated IPv4 address. Did you mean that the dedicated IPv4 address to connect via SSH? Then my objection doesn't apply.