Sprint is doing something odd with DNS queries. More than odd, it's disturbing.
Anyone using Sprint's Wireless Network card, try this experiment. Open a terminal and do a host lookup on slasdot.org. Tell host or nslookup to use a non-public IP, or an IP you know is not running DNS. Use the verbose output. You'll find that the server you indicated "responded" with information.
For example, on OSX or Linux do this:
host -v slashdot.org 192.0.0.1
fortune: cpu time/usefulness ratio too high -- core dumped.