TCP connection hijacking relies on this ability to perform a man-in-the-middleForging IP addresses is easy in one direction. But 1. receiving the packets that are sent back and 2. shutting up the real destination aren't as easy, but those are also necessary to successfully engage in non-trivial communication.
but no one does because DNSsec is not deployed (and there are questions
of how deployable it is).
If you use SSL there is no need for the DNS replies to be 100% reliable anyway as forging DNS information just becomes a very elaborate DoS attack.
SSL is not a general solution. Consider UDP-based applications or routing protocols such as OSPF -- neither of which is helped one iota by SSL. Ran