PDA

View Full Version : DNS woes after changing router


Zut
2006-02-22, 04:23 PM CST
Not long ago I got a new router (netgear dg632 el-cheapo thing) after my old one got fried, and after that time my Linux box started experiencing problems.

I cant use yum at all since it cant connect to any repositories and firefox cant access any pages, although I can still use local servies (like ssh), and I can still ping any server, e.g...

[root@fifi ~]# ping bbc.co.uk
PING bbc.co.uk (212.58.224.131) 56(84) bytes of data.
64 bytes from bbc.co.uk (212.58.224.131): icmp_seq=0 ttl=114 time=37.4 ms
64 bytes from bbc.co.uk (212.58.224.131): icmp_seq=1 ttl=114 time=36.5 ms
64 bytes from bbc.co.uk (212.58.224.131): icmp_seq=2 ttl=114 time=36.7 ms
64 bytes from bbc.co.uk (212.58.224.131): icmp_seq=3 ttl=114 time=37.4 ms
64 bytes from bbc.co.uk (212.58.224.131): icmp_seq=4 ttl=114 time=36.7 ms

--- bbc.co.uk ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4016ms
rtt min/avg/max/mdev = 36.538/37.004/37.496/0.423 ms, pipe 2

I assume this means a DNS problem (im no expert). I was able to 'fix' the problem by activating the NetworkManager service, and setting a static IP address (something I found while googling), but I dont like having a static IP address. It doesn't seem like a proper solution to me and after all it worked perfectly well with DHCP before I got the new router, and no settings have been changed.

Does anyone have any suggestions?

Thanks :)

Edit: Sorry! Im running Fedora Core 4, kernel 2.6.14-1.1644_FC4 on a Via Epia M2 12000. Ive not installed anything special network wise.

foobar47
2006-02-23, 06:01 AM CST
What is your /etc/resolv.conf file ?

Zut
2006-02-23, 05:05 PM CST
Thanks for the reply...

My /etc/resolv.conf is set by the NetworkManager service...

; generated by NetworkManager, do not edit!

; Use a local caching nameserver controlled by NetworkManager



nameserver 127.0.0.1

Before that it just had a single line for my router, 192.168.0.1.

Thanks again :)

crick136
2006-03-11, 01:08 AM CST
the reason it works now is because NetworkManager has set up a caching nameserver on ur box, where before your computer relied on your router to supply it with a nameserver, now your computer is your nameserver. its fine to leave it like this. but if you want to let dhcp handle your ip address and settings, then you'll need to make sure your router is configured with your ISP's nameservers (this is done automatically if your router gets its WAN ip address via DHCP. after that just make sure your computer's /etc/resolv.conf has a nameserver line with your router's LAN ip address.