By injecting responses for server1.yourco.com, server2.yourco.com, you could MITM someone's backend servers without leaving any traces, which is an even more se

By injecting responses for server1.yourco.com, server2.yourco.com, you could MITM someone's backend servers without leaving any traces, which is an even more serious concern if they're terminating TLS at the NGINX server, which is a very common use case. DJB has been warning against non-randomized port numbers for DNS resolvers for more than 15 years.[1] This is not a new issue. NGINX's response here is quite disheartening. 1. https://cr.yp.to/djbdns/forgery.html https://cr.yp.to/djbdns/forgery.html