Subject: Re: [vserver] Re: New guy needs a little help
From: Matt Paine <matt@mattsoftware.com>
Date: Wed, 10 Sep 2008 11:47:48 +1000

Hi Caleb

Sounds like a name resolution problem rather than a routing problem


Try coping the /etc/resolv.conf file from the host into the guest and 
give it another shot :)

Matt.



Caleb Call wrote:
> sorry, it sent by mistake...so let me finish.
>
>
> Hopefully I'm not asking something that's already covered (I'm sure I 
> am) but I've looked all over and I can't seem to find any help.  So I 
> built my first vserver.  My Host is a Centos 5 box (5.2) and my guest 
> is the same (Centos 5.2).  I've got it up and running, I've been able 
> to install everything I need on my guest (httpd, mysql, php, etc) 
> using vyum so it can act as a web server.  My problem lies in once 
> I've in my vserver, I can't get out of the machine (ping, etc) using 
> names.  This would leave me to believe DNS is not working properly.  
> My first thought was to check what my /etc/resolv.conf had in it.  The 
> file doesn't exist, so I created it, added my nameservers but it still 
> can't lokup hosts.  I can ping by IP and it gets out fine.  What am I 
> missing?  Do I need to create a default route?  I don't know if I have 
> my interfaces configured properly even.  I followed the wiki page to a 
> "T" using yum to install everything.
>
>
> HELP!
>
> Thanks,
> Caleb
>
>
> On Tue, Sep 9, 2008 at 7:35 PM, Caleb Call <caleb@macjunk.net 
> <mailto:caleb@macjunk.net>> wrote:
>
>     Hopefully I'm not asking something that's already covered (I'm
>     sure I am) but I've looked all over and I can't seem to find any
>     help.  So I built my first vserver.  My Host is a Centos 5 box
>     (5.2) and my guest is the same (Centos 5.2).  I've got it up and
>     running, I've been able to install everything I need on my guest
>     (httpd, mysql, php, etc) using vyum so it can act as a web
>     server.  My problem lies in once I've in my vserver, I can't get
>     out of the machine (ping, etc) using names.  This would leave me
>     to believe DNS is not working properly.  My first thought was to
>     check what my /et
>
>