View previous topic :: View next topic |
Author |
Message |
Vryali n00b
Joined: 11 Apr 2007 Posts: 4
|
Posted: Wed Apr 11, 2007 6:59 am Post subject: Not resolving DNS after chroot, resolv.conf copied |
|
|
Moving through the installation steps everything works properly (as best I can tell) up until i chroot. Prior to chroot I'm able to ping fine (by domain name), the contents of resolv.conf before and after the chroot command are:
Code: | # Generated by dhcpcd for interface eth0
search XXXXXX.com // I just replaced my company name with Xs
nameserver 192.168.20.10
nameserver 192.168.20.12
|
I am copying the file properly, at the very least post-chroot it reads the same anyway. It can ping, both before and after, said nameservers (which are correct), but doesn't appear to be using them properly after the chroot? Not very good with linux yet, though I hope this is something simple so I can keep on trucking, trying to ping on my windows machine and add the IPs to /etc/hosts for now to continue with the installation =) |
|
Back to top |
|
|
gentoome Tux's lil' helper
Joined: 18 Jul 2005 Posts: 78
|
Posted: Wed Apr 11, 2007 9:36 am Post subject: |
|
|
Could you be a little more specific as to the steps you go through ? Maybe copy/paste the commands and the output ?
John |
|
Back to top |
|
|
Vryali n00b
Joined: 11 Apr 2007 Posts: 4
|
Posted: Wed Apr 11, 2007 10:25 am Post subject: |
|
|
Following the installation steps gets me up to the point where I do:
6.a
Code: |
# mount -t proc none /mnt/gentoo/proc
# mount -o bind /dev /mnt/gentoo/dev
# chroot /mnt/gentoo /bin/bash
# env-update
>> Regenerating /etc/ld.so.cache...
# source /etc/profile
# export PS1="(chroot) $PS1" |
I've retyped the text as my laptop shows it below on the following things:
Code: | (chroot) livecd / # ping www.google.com
ping: unknown host www.google.com
(chroot) livecd / # cat /etc/resolv.conf
# Generated by dhcpcd for interface eth0
search XXXX.com
nameserver 192.168.20.10
nameserver 192.168.20.12
(chroot) livecd / # emerge --sync
Notice: (-3, 'Temporary failure in name resolution' )
>>> Starting rsync with rsync://rsync.gentoo.org/gentoo-portage...
>>> Checking server timestamp ...
rsync: getaddrinfo: rsync.gentoo.org 873: Temporary failure in name resolution
rsync error: error in socket IO (code 10) at clientserver.c(107) [receiver=2.6.8]
>>> Retrying... |
Here it does 3 retrys and fails out. If I echo "134.68.220.97 rsync.gentoo.org" >> /etc/hosts it works fine. I'm actually trying to get through the installation like that for now, 2nd try, as the first hung up trying to get the kernel, but we'll see how ti goes.
If that isn't enough information, I have zero idea of what else you could possibly want, please let me know specifically, I apologize for any noobness, but I'm not overly familiar with all this =/ |
|
Back to top |
|
|
jseymour Apprentice
Joined: 23 Jun 2006 Posts: 202 Location: Gainesville Florida
|
|
Back to top |
|
|
Vryali n00b
Joined: 11 Apr 2007 Posts: 4
|
Posted: Wed Apr 11, 2007 10:46 am Post subject: |
|
|
Copy pasted from the installation steps, this is what I did...
Code: | (The "-L" option is needed to make sure we don't copy a symbolic link)
# cp -L /etc/resolv.conf /mnt/gentoo/etc/resolv.conf
|
I did a cat of the file in my last post as well, the /mnt/gentoo/etc/resolv.conf and /etc/resolv.conf are identical in content. |
|
Back to top |
|
|
gentoome Tux's lil' helper
Joined: 18 Jul 2005 Posts: 78
|
Posted: Wed Apr 11, 2007 1:55 pm Post subject: |
|
|
OK, as far as I can see, you're not doing anything wrong. Could you try adding "option debug" on a new line in your /mnt/gentoo/etc/resolv.conf ? I think we need a little more info. BTW, what version of the livecd are you using ? what stage ?
John |
|
Back to top |
|
|
Vryali n00b
Joined: 11 Apr 2007 Posts: 4
|
|
Back to top |
|
|
desultory Bodhisattva
Joined: 04 Nov 2005 Posts: 9410
|
Posted: Wed Nov 21, 2007 10:09 am Post subject: |
|
|
Moved from Installing Gentoo to Duplicate Threads as this problem appears to have already been discussed and though the underlying cause was not determined a work around was found. |
|
Back to top |
|
|
|