Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
 Post subject: DNS Resolving Broken
PostPosted: Sat Oct 16, 2010 3:41 pm 
Offline
Newbie

Joined: Sat Oct 16, 2010 3:32 pm
Posts: 2
Hello,

I'm using Arch Linux on a Linode 512. My network configuration was working fine recently, but, not now.

I did do a Linode resize recently, but I don't believe this caused the problem as I'd been able to do package installs up until a couple days ago. I mention this because someone seemed to have an identical problem to this caused by a resize, but it sounds like it was a problem with the resize and SELinux playing nicely together: http://www.linode.com/forums/viewtopic.php?t=5818

Here's the contents of /etc/resolv.conf:
Code:
8.8.8.8
8.8.4.4


Name lookups are broken, however, I can access the Internet just fine by IP address -
Code:
$ ping google.com
ping: unknown host google.com
$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=8.18 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=8.56 ms
^C
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 8.187/8.376/8.566/0.210 ms


Anyone have any pointers? The following is some general networking information from my server (specific machine IP addresses removed) -
Code:
$ ifconfig
eth0      Link encap:Ethernet  HWaddr FE:FD:45:A4:DD:19
          inet addr:69.164.221.X  Bcast:69.164.221.255  Mask:255.255.255.0
          inet6 addr: fe80::fcfd:45ff:fea4:dd19/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:60260 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23681 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:54781503 (52.2 Mb)  TX bytes:52366406 (49.9 Mb)
          Interrupt:28

eth0:0    Link encap:Ethernet  HWaddr FE:FD:45:A4:DD:19
          inet addr:69.164.222.X  Bcast:69.164.222.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:28

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:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:282 (282.0 b)  TX bytes:282 (282.0 b)

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.8.0.1  P-t-P:10.8.0.2  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  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:100
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.8.0.2        0.0.0.0         255.255.255.255 UH    0      0        0 tun0
10.8.0.0        10.8.0.2        255.255.255.0   UG    0      0        0 tun0
69.164.221.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
69.164.222.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         69.164.221.1    0.0.0.0         UG    0      0        0 eth0


Top
   
 Post subject:
PostPosted: Sat Oct 16, 2010 4:10 pm 
Offline
Senior Member
User avatar

Joined: Tue Nov 24, 2009 1:59 pm
Posts: 362
Code:
nameserver 8.8.8.8
nameserver 8.8.4.4


Read 'man resolv.conf' >.<.
Also, why using Google's DNS instead of Linode's local ones, that are in same building as you are?

_________________
rsk, providing useless advice on the Internet since 2005.


Top
   
 Post subject:
PostPosted: Sat Oct 16, 2010 4:35 pm 
Offline
Newbie

Joined: Sat Oct 16, 2010 3:32 pm
Posts: 2
rsk wrote:
Code:
nameserver 8.8.8.8
nameserver 8.8.4.4


Read 'man resolv.conf' >.<.
Also, why using Google's DNS instead of Linode's local ones, that are in same building as you are?
Oh, man, stupid mistake on my part >.< I knew it was something simple. Thanks.

I had Linode's servers in there, but was fiddling with making the OpenVPN configuration bridged instead of tunneled and as a side-effect the dhcp client ended up clobbering my resolv.conf. Put Google's in there quickly since I knew the IP addresses.


Top
   
 Post subject:
PostPosted: Sun Oct 17, 2010 1:17 am 
Offline
Senior Member

Joined: Sun Oct 30, 2005 7:52 pm
Posts: 97
aaronfitz wrote:
dhcp client ended up clobbering my resolv.conf


Switching to static configuration will solve that, see http://library.linode.com/networking/co ... nterfaces/

--
Travis


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group