I'll find a workaround. I need to do a crude form of WS load balancing in a situation where the amount of load would make an AWS Network LB cost prohibitive.
I figured if I could get a load-balanced WS server to redirect to the final host, I'd be good to go. I may instead require the clients to ask an HTTP API for the final WS URI. I don't think DNS load balancing would be a great fit. But this is all out of scope for http4k of course.