DHCP not doing it's job after fresh install

ixtow · 2007-11-02 21:40:04

Clipped from: http://archlinux.org/static/docs/arch-install-guide.txt

/etc/resolv.conf

   Use this file to manually setup your nameserver(s) that you want to
   use. It should basically look like this:

search domain.tld
nameserver 192.168.0.1
nameserver 192.168.0.2

   Replace domain.tld and the ip addresses with your settings. The
   so-called search domain specifies the default domain that is appended
   to unqualified hostnames automatically. By setting this, a ping myhost
   will effectively become a ping myhost.domain.tld with the above
   values. These settings usually aren't mighty important, though, and
   most people should leave them alone for now. If you use DHCP, this
   file will be replaced with the correct values automatically when
   networking is started, meaning you can and should happily ignore this
   file.

"If you use DHCP, this file will be replaced with the correct values automatically when networking is started..."

Problem is, my resolv.conf does not get populated.

Yes, DHCP is up and running, adapter is functioning. ifconfig shows me all relevant data, including the IP it pulled from my router. But resolv.conf is empty. Can't ping anything (as expected).

Oddly enough, everything works when I boot from the CD....

Last edited by ixtow (2007-11-02 21:43:12)

ixtow · 2007-11-04 14:05:02

[bump]

Should I just assume that I'm not smart enough to use arch?

sykesm · 2007-11-04 15:03:23

maybe permissions. the following is my resolve.conf

[sykesm@plamuk etc]$ ls -l resolv.conf
-rw-r--r-- 1 root root 91 2007-11-02 14:26 resolv.conf

[sykesm@plamuk etc]$ more resolv.conf
# Generated by dhcpcd for interface eth0
nameserver 194.168.4.100
nameserver 194.168.8.100

ibendiben · 2007-11-04 15:14:55

"If you use DHCP, this file will be replaced with the correct values automatically when networking is started..."
If your network doesn't start I assume the file remains the same... Check if your network starts correctly, well it doesn't obviously, but check what error messages it gives you. Post some entries of your wireless config files too...

ixtow · 2007-11-04 15:57:26

Networking does start up.

If I log in as root and type ifconfig, it shows me eth0 is up, and it has an IP assigned that fits the range that the DHCP server issues. If I change the range of IPs issued in the DHCP server, and then restart networking, I get a new ip that suits the new range....

But resolv.conf is still empty.

Nothing stands out in any of the relevant logs.

I am not using WiFi.... yet. Have to get the wired connection working first. When I do, I want it to just latch onto any old wifi signal it can find automatically. But that's another thread....

I'll check the permissions when I get back in touch with the machine. The file is set to whatever the latest install CD does.... Haven't touched it.

sykesm · 2007-11-04 18:19:32

if you know the ip address of dns servers, vi the resolve.conf file, type them in as above, and see if things respond as expected.

ixtow · 2007-11-04 18:48:48

I don't have the DNS info. I'm counting on DHCP to tell me. :-)

Lone_Wolf · 2007-11-04 20:08:34

post your rc.conf, also look in /var/logs/everything.log to see what messages network/dhcp give.

Ruckus · 2007-11-04 20:11:34

I dont think it overwrites my resolv.conf either, I had to add my router's IP manually, so my router just always forwards all DNS requests to the ISP's name server.

ixtow · 2007-11-06 15:52:10

The permissions were 777, which shouldn't have been an issue really.... but after switching to what is shown above, it works.

Thanks guys!

Last edited by ixtow (2007-11-06 15:52:40)

soloport · 2008-12-16 06:34:11

Old thread, but I found it looking for resolution to same or similar issue. In my case, whatever I tried (/etc/rc.d/network restart, deliberately setting resolv.conf, re-booting, etc.) ended up with an empty /etc/resolv.conf -- very frustrating.

Even though pacman said dhcpcd was up-to-date, the solution was: pacman -S dhcpcd

What seemed to break it was kernel upgrade (only package / change since it was previously working).

FFR

Arch Linux

#1 2007-11-02 21:40:04

DHCP not doing it's job after fresh install

#2 2007-11-04 14:05:02

Re: DHCP not doing it's job after fresh install

#3 2007-11-04 15:03:23

Re: DHCP not doing it's job after fresh install

#4 2007-11-04 15:14:55

Re: DHCP not doing it's job after fresh install

#5 2007-11-04 15:57:26

Re: DHCP not doing it's job after fresh install

#6 2007-11-04 18:19:32

Re: DHCP not doing it's job after fresh install

#7 2007-11-04 18:48:48

Re: DHCP not doing it's job after fresh install

#8 2007-11-04 20:08:34

Re: DHCP not doing it's job after fresh install

#9 2007-11-04 20:11:34

Re: DHCP not doing it's job after fresh install

#10 2007-11-06 15:52:10

Re: DHCP not doing it's job after fresh install

#11 2008-12-16 06:34:11

Re: DHCP not doing it's job after fresh install

Board footer