OpenVZ Forum - RDF feed
type: channel
items: Re: Can't resolve host address within container [SOLVED]
items: Re: Can't resolve host address within container

Re: Can't resolve host address within container [SOLVED]
type: item
description: Hi all, First of all, I apologyze for my poor english I am a total newbie and I am desperated. I've installed openVZ in a centOS 5.6, I can work with containers but i can't resolve any internet address within containers. I just can ping, but when I make a wget, I always receive a wget: unable to resolve host address "google.com" message. I've read lots of forums and messages, but I've found no solution. I'm not an expert in linux, nor networks. I create the containers as follows: vzctl create 101 --ostemplate fedora-14-x86_64 vzctl set 101 --ipadd 192.168.1.101 vzctl set 101 --nameserver 62.14.4.64 --nameserver 62.14.4.65 My /etc/sysctl.conf file: # Kernel sysctl configuration file for Red Hat Linux # # For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and # sysctl.conf(5) for more details. # Controls IP packet forwarding net.ipv4.ip_forward = 1 net.ipv4.conf.default.forwarding = 1 net.ipv4.conf.all.forwarding = 1 net.ipv4.conf.default.proxy_arp = 0 # Controls source route verification net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 # Do not accept source routing net.ipv4.conf.default.accept_source_route = 0 net.ipv4.conf.default.send_redirects = 1 net.ipv4.conf.all.send_redirects = 0 # Controls the System Request debugging functionality of the kernel kernel.sysrq = 1 # Controls whether core dumps will append the PID to the core filename # Useful for debugging multi-threaded applications kernel.core_uses_pid = 1 # Controls the use of TCP syncookies net.ipv4.tcp_syncookies = 1 # Controls the maximum size of a message, in bytes kernel.msgmnb = 65536 # Controls the default maxmimum size of a mesage queue kernel.msgmax = 65536 # Controls the maximum shared segment size, in bytes kernel.shmmax = 68719476736 # Controls the maximum number of shared memory segments, in pages kernel.shmall = 4294967296 My /etc/resolv.conf file: nameserver 62.14.4.64 nameserver 62.14.4.65 Result of ifconfig: eth0 Link encap:Ethernet HWaddr 00:1E:90:E5:B8:22 ine…
creator: plotinus
date: 2011-06-11T13:22:01-00:00

Re: Can't resolve host address within container
type: item
description: Hi, Try to set resolvers for the container as : nameserver 8.8.8.8 nameserver 208.67.222.222 nameserver 208.68.222.222 Then try to wget...... It should work for you
creator: Kristian0911
date: 2011-06-13T05:40:00-00:00

Re: Can't resolve host address within container
type: item
description: Thank you for your answer! But it doesn't work, "unable to resolve host address" again. Aaagghhh!!!
creator: plotinus
date: 2011-06-13T07:40:09-00:00

Re: Can't resolve host address within container
type: item
description: Hi, Your container has a "private" IPv4 Address and should reach a official IPv4, see OpenVZ Wiki http://wiki.openvz.org/Using_NAT_for_container_with_private_ IPs#How_to_provide_access_for_container_to_Internet Bye, Thorsten
creator: curx
date: 2011-06-13T11:56:34-00:00

Re: Can't resolve host address within container
type: item
description: Thank you, Thorsten, I will study it and test it. I'll say you if it goes or not (I hope yes).
creator: plotinus
date: 2011-06-13T12:17:12-00:00

Re: Can't resolve host address within container
type: item
description: iptables crashed, but I'm thinking... I want to virtualize some web sites and to reach the containers (my web sites) thru the internet: I want to see my website using the browser, say writing h_t_t_p://mydomain.com. Do I need to have internal IP addresses like 192.168.1.x? Now I create a container with an external IP, not an internal one: vzctl create 101 (I use a config file) vzctl set 101 --ipadd 85.43.xx.xx (the IP of mydomain.com) For the moment, let's forget iptables. If I create my containers using an external IP, do I have access to the internet? (for the moment it doesn't happen, maybe for the crash of iptables. I think I must reinstall centOS!).
creator: plotinus
date: 2011-06-14T15:43:18-00:00

Re: Can't resolve host address within container [SOLVED]
type: item
description: Finally I did it! Your post was the solution, thank you!! It was the information I needed. Yes, the containers (in my case) must have a private IP, not a public one (I was wrong) and then your link applies. The problem is iptables, but if I stop iptables, I get access to/from the internet. But this is another story.... Thank you again
creator: plotinus
date: 2011-06-16T21:42:11-00:00

Re: Can't resolve host address within container [SOLVED]
type: item
description: Hi, I got the same problem like you. and when I show ifconfig on my container, it shows: (the container does not have eth0) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 b) TX bytes:560 (560.0 b) venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: fe80::1/128 Scope:Link UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:39 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:6913 (6.7 KiB) please help me to find out the problem.thanks so much!
creator: sarh877
date: 2013-10-28T05:02:02-00:00