I don't think you need to worry about the non-authoritative answer part. I think that just means it sent back a cached value rather than continuing to search for the server that actually knows for sure. It saves on network traffic, but also means DNS changes can take a while to propagate throughout the net.
The request timeout would suggest you've got a DNS server configured that was not reachable. Perhaps it's a temporary problem where the server went down. Normally, there are two DNS servers setup, and occasionally 3. If you don't have a secondary, or if one of the servers you have setup is bad, perhaps you should update your network setup:
My Network Places -> Properties
Local Area Connection -> Properties (Assuming you're connected through a LAN)
Internet Protocol (TCP/IP) -> Properties
Set Preferred DNS server and Alternate DNS server (these values will depend on your ISP, so ask them, or use DHCP on your gateway device and it should fetch these values for you).
If want you more DNS info, you can use nslookup interactively:
nslookup
> set d2 (show full debugging info)
> outpost2.net
... (lots of info)
I'm not too sure what you'd do with that info, but it might be interesting to take a quick peak. Like what server replied, and how long it's answer is supposed to be good for.