You are not logged in.
Yours dosen't look quite right compared to mine . . .
search blah.blah.com
nameserver 10.1.1.3
nameserver 10.1.1.4
That's all I have. Not that the comments make a difference . . . are you still running dhcpcd by chance?
Offline
are you still running dhcpcd by chance?
Well, I can't actually boot it up at the moment to double check, but I did do the old 'pacman -R dhcpcd' as a first step and it did return success.
I've been holding off on making changes to get it to work just in case you wanted something checked out in the process. If I should just go ahead and dig into it, let me know. I think I'd restore the original /etc/rc.d/network file and let it error out due to the non-existence of dhcpcd; hoping it would boot anyway.
Thanks,
--J
Offline
Yeah I would get your setup restored. Let me work on this a little bit more. It seems to work for me. Restore your network file. I'll try to work with the dhclient package maintainer to see if he wants to incorporate this.
Offline
If anyone's keeping score... I'm back to the basic dhclient config (un-patched /sbin/dhclient-script, /etc/rc.d/network edited for change from dhcpcd to dhclient and a /etc/dhclient.conf that has an append for nameservers. All seems to be fine at this point. If you'd like me to test future revs of that patch, just let me know when you have one to try.
Either way, thanks for you guys' help. I'm learning a lot about ArchLinux/Linux, which is what I was looking for.
I'm going to give it a few hours before I post my next newbie question just to give everyone a break
--Jeff
Offline
;-)
Offline
My /etc/dhclient.conf looks that:
supersede domain-name "localhost";
prepend domain-name-servers 212.59.0.1, 212.59.0.2;
Offline
I'd like to use dnsmasq as a DNS cache so I need to prepend it to /etc/resolv.conf. The solution proposed here is quite messy. Is there any easier workaround ?
Offline
My /etc/dhclient.conf looks that:
supersede domain-name "localhost";
prepend domain-name-servers 212.59.0.1, 212.59.0.2;
That's not messy.
Offline
Rokas wrote:My /etc/dhclient.conf looks that:
supersede domain-name "localhost";
prepend domain-name-servers 212.59.0.1, 212.59.0.2;That's not messy.
I have the dhclient package installed (manually) but /etc/dhclient.conf doesn't exists. In all distributions I've tried so far a full dhclient.conf is provided as an example. So I thought it wasn't the case.
But I just tried what you pasted here and didn't worked. I created a /etc/dhclient.conf with this single line:
prepend domain-name-servers 127.0.0.1;
When I booted up, and /etc/resolv.comf was like this:
[ktk@ktk7 ~]$ cat /etc/resolv.conf
# Generated by dhcpcd for interface eth0
search rjo.virtua.com.br
nameserver 192.168.15.1
I did a 'sudo dhclient' and got the same IP again, but /etc/resolv.conf got a bit messed up, like this:
search rjo.virtua.com.br
nameserver 127.0.0.1
nameserver 192.168.15.1
How can make my system use dhclient INSTEAD of dhcpcd automatically ? Thanks in advance
Offline
i had nearly the same problem using dhcpcd, i found an article in the wiki:
If you use DHCP and you do not want your DNS servers automatically assigned every time you start your network, be sure to use the "-C" option in DHCPCD_ARGS in /etc/conf.d/dhcpcd (used by /etc/rc.d/network). This prevents dhcpcd from rewriting your /etc/resolv.conf every time:
DHCPCD_ARGS="-C resolv.conf -q"
http://wiki.archlinux.org/index.php/Con … nfigure_IP
i hope this helps
Offline