Oddly, this time, I was able to load Google (but not other sites). Why might that be? That makes it seem more like a
DNS issue than anything else.
Code:
charles@zed:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:24:8c:04:01:e2
inet addr:65.43.209.162 Bcast:65.43.255.255 Mask:255.255.0.0
inet6 addr: fe80::224:8cff:fe04:1e2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3674731 errors:0 dropped:0 overruns:0 frame:0
TX packets:3129901 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3172444359 (3.1 GB) TX bytes:550073505 (550.0 MB)
Interrupt:18
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11996 errors:0 dropped:0 overruns:0 frame:0
TX packets:11996 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:599948 (599.9 KB) TX bytes:599948 (599.9 KB)
charles@zed:~$ ping google.com
PING google.com (74.125.45.100) 56(84) bytes of data.
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=1 ttl=245 time=39.6 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=2 ttl=245 time=39.8 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=3 ttl=245 time=38.4 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=4 ttl=245 time=40.3 ms
^C
--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3014ms
rtt min/avg/max/mdev = 38.408/39.574/40.347/0.715 ms
charles@zed:~$ ping cnn.com
PING cnn.com (157.166.226.26) 56(84) bytes of data.
^C
--- cnn.com ping statistics ---
103 packets transmitted, 0 received, 100% packet loss, time 102173ms
