Dashmundo wrote...
Me too.
Computer nerds: is this something to be concerned about, or is the fact that a Google program directs all of us towards a Google server expected?
Not a networking guy but works in the industry.
A Domain Name Server (DNS) is something that's fairly prevalent on the 'net. While not strictly necessary, it is highly important because you won't want to type "http://173.203.38.48" to come here. (Interestingly, this resolves differently at my workplace. Bioware has multiple IPs for its social.bioware.com site...)
Each time you type in a new, uncache readable address, your PC will attempt to resolve against a DNS; obviously if there's one central DNS it'll be overwhelmed and a single point of failure. As such, DNS servers are commonly emplaced both regionally and locally, typically with Domain Name authorities (whose responsibility it is to update the entries), but also with ISP (and corporate internals, but that's a separate story). As such, the closest, logically most responsive DNS is not Google's, but your ISP's. Unless you play at Google's Data Center. In which case use theirs.

Of course if your ISP cheats, and/ or has a poor server as your DNS, it... will suck. If your ISP is a major player in your area and is known for reliability, there is no real reason that Google's DNS will respond faster (because it's still likely to be physically further, and requests will take longer. Even at lightspeed, it takes time).
On a note on DNS settings. Generally, your modem/ cable box/ router is configured to pull DNS settings from your ISP automatically. If you know a DNS that is very stable and static (i.e., IP does not change), manually setting the DNS won't be a big issue. The key thing here is that the DNS should be able to respond quickly to requests, but that is something you can't tell because it depends on the server loading. DNS requests are designed to be lightweight but when several million requests hit at one time, it's going to load.