nginx can definitely do this and divide/redirect traffic by conditions specified all the way up to the application layer (as a 'reverse' proxy).
However, I'm feeling this is an XY Problem, and that OP really doesn't want to be writing their own 'filter' or 'proxy'. Furthermore, it doesn't seem OP has the hardware resources (nor the financial resources or C-level backing) to do things properly.
Perhaps if OP would state a bit more about their infrastructure, traffic patterns (how does traffic arrive to the box), DNS setup (from the external and internal sides) and what they're trying to achieve overall, the network people here may be able to help them come up with a solution that isn't overly insecure, and doesn't compromise traffic destined for other services.
You do not want to promise something that you can't deliver, especially in an environment where you've got no backing whatsoever to make it so.
In reply to Re^3: Networking with IO::Socket
by stevieb
in thread Networking with IO::Socket
by TheVend
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |