Midori Unable to Resolve Hostnames

[DouglasBush]

This is quite annoying... Everything on the PI is set up to use automatic DHCP resolution. I had been doing this for 9 months at work. I just took the PI home, and now the network doesn't seem to work.

For the last 9 months I'd been using a Pi B, and I simply popped the Newbs I'd been developed software on into a new B+. I have noticed differences in how the piTFT is behaving compared to the B. (I did not verify that DNS was working on the B+ when it was at work.)

My kernel was recently fully updated (1 month ago) before getting at this. I was working with the piTFT.

At this time I'm able to use tightVNC to talk to the PI. It seems fine, but occasionally seems to pause, then continue. (Like its struggling to resolve something. It never used to do that.)

This is what I get on the command line on the PI.

Code: Select all

pi@raspberrypi ~ $ cat /etc/hostname
raspberrypi
pi@raspberrypi ~ $ ifconfig -a
eth0      Link encap:Ethernet  HWaddr b8:27:eb:23:c8:74  
          inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1031 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1253 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:50274 (49.0 KiB)  TX bytes:196304 (191.7 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

pi@raspberrypi ~ $ cat /etc/resolv.conf
nameserver 192.168.0.1
pi@raspberrypi ~ $ sudo cat /etc/network/interfaces
auto lo

iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
pi@raspberrypi ~ $ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0

Here's what my Windows PC is saying;

Code: Select all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Monster
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Intel(R) 82579V Gigabit Network Connection
   Physical Address. . . . . . . . . : 54-04-A6-48-BC-15
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d01b:803b:f5cb:b31c%12(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.0.104(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, November 08, 2014 8:23:22 AM
   Lease Expires . . . . . . . . . . : Tuesday, December 15, 2150 6:10:38 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 257164454
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-CC-A2-32-54-04-A6-48-BC-15
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{181251E0-4F9A-4F55-9A07-4F9543CD19CD}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:3472:32f:5e47:1fc0(Preferred) 
   Link-local IPv6 Address . . . . . : fe80::3472:32f:5e47:1fc0%10(Preferred) 
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

[DougieLawson]

sudo sh -c 'echo "nameserver 8.8.8.8" >> /etc/resolv.conf'

Edit: idiot error, used cat instead of echo.

[DouglasBush]

cat: nameserver 8.8.8.8: No such file or directory

[DouglasBush]

I could "sudo vi /etc/resolv.conf" and add the line you suggested. That still did nothing unless I need to somehow refresh the use of that file.

[DirkS]

I could "sudo vi /etc/resolv.conf" and add the line you suggested. That still did nothing unless I need to somehow refresh the use of that file.

Reboot is the easiest way to refresh.

[DouglasBush]

The file is overwritten when that happens.

[DirkS]

The file is overwritten when that happens.

When is which file overwritten and is that relevant?

[DouglasBush]

DougieLawson: That worked... it added the line, but it has no effect. And a reboot also wipes it. Either way, ping 8.8.8.8 doesn't work.

[DougieLawson]

In that case you need to look at your other network definitions.

Start with a route -n command to see what your gateway machine is defined as.
Can you ping the gateway ping -c3 192.168.ggg.ggg
Can you ping Google's DNS ping -c3 8.8.8.8
Can you resolve host names to IP addresses? ping -c3 google.com

Do the settings (gateway, DNS, etc.) on your Pi look the same as your laptop?

[DouglasBush]

Everything looks the same as my desktop PC. Its all in my first post. My desktop can ping 192.168.0.1, while the PI cannot.

On the PI, ping google.com says unknown host google.com. On my desktop it works just fine.

[DouglasBush]

I have determined who the f**k up fairy is, and I will not name names as I may incriminate myself.

There was a binding conflict on the ip address.