This happens a lot, and it is almost always due to something badly set up in the networking area, usually a problem with DNS and/or IPV6.
Originally Posted by Gwilliams1205
...I have read about disabling ipv6...
That's certainly a good idea, but you may have to disable it in more than one place. You have probably disabled the use of v6 for 'normal' networking, but, if you have an ipv6 address for your first nameserver, you will still have the problem.
Check /etc/resolv.conf; there should be at least one nameserver there. you should also try pinging that nameserver; any ping time above 200 mS would be a worry. (It might also be set to a local address, eg, your modem/router, which should give a sub-10mS ping time, but raises the question as to whether the nameserver it connects to is fast or not).
Have a quick look at /etc/nsswitch.conf; ensure that the line 'hosts' seems sensible. Whatever is in there, the various sources for look ups will be evaluated one by one. If the first is slow or non-existant, look ups will proceed by trying the first, waiting until it seems clear that this service will not answer, and then trying the subsequent one.
The obvious upshot of this is that everything can get slow if the early services in the list are slow and its not always obvious that its a long delay and then data transfer at a reasonable rate, rather than a slow rate of data transfer from the start.
You should also try dig. So, if you type
you'll get the time that it took to resolve that name. Now google is probably a bad example, because you've probably used it recently and so it may be cached. So try something more obscure, that you haven't used recently, twice, and check whether the first lookup is slower than the second, as it will be if there is caching involved.